for big team. One big file with data scheme. • Performance issues with big data scheme • Full consistency can cause performance issues • There is no observing of nested entities from the box • Can cause performance issues during app startup because of DB creation
are mutable • Leaking abstraction. You have to think about SQL if you are building something complex • It can only store actual domain models • No place for intermediate state • Migrations • Do we really need database inside mobile app?
to simplify state management inside Facebook messenger on the web • Not a framework, just a pattern • Not new idea, but a combination of existing pattern with some additional components
data flow • State is split into stores • Each store contains state modification logic based on events • All state mutations are isolated in separate layer
service layer • Updates the state • Notifies View about state changes • Store is the only place in your whole app that has privilege to mutate the state
using KVO or any other type of notifications • When state is changed View should sync it’s UI components tree with state • Todo app sample https://github.com/techery/flux- todo-app