Sucesses

• Rethinking the app as a set of:

  • Components

  • Component-level Stores

  • Series of state changes
     

• Create an abstraction around client/server traffic
   

• Make our components idempotent (or "pure")

✔

How React Helped

Mistakes

Dispatcher Abuse

• It's reserved for application state

• It's not a generic EventEmitter

• Be wary of any Dispatcher use outside of an action

https://facebook.github.io/flux/docs/overview.html#structure-and-data-flow

Stores

• Multiple stores aren't inherently bad

• But if you let them know about each other you're gonna have a bad time

What React doesn't solve for you

Be mindful

• DOM updates aren't free

• Processing on stores happens regardless of render

• A/B Testing
   

• Rehacked  was created to solve this problem

If we were doing it now

• NEVER shortcut unidirectional data flow

• Data management is huge

  • Consider redux and/or immutable
     

• Awesome view layer !== application architecture

• React has changed lots over the last year+

• React Best Practices for 2016

Tips