Your app == derived data ...using the history of every action that ever happened
17
Process every action for every query request.
18
Can we make it fast enough?
19
An example: photos
20
Lots of advantages Manage the trade-atts of your data store granularly
21
Choose the best data store for your question.
22
Closing the loop
23
Things that don't work
24
Communication between stores waitfor() doesn't work
25
Option 2: Enrich data Consume action, emit new action with additional data.
26
Strong consistency Only individual answers to questions may be consistent
27
Strong consistency Lack of strong consistency is a more accurate worldview
28
Read about stream processing frameworks.
29
Turning the Database Inside Out
Description:
Explore full-stack Flux architecture in this conference talk from React.js Conf 2015. Dive into the challenges of current backend systems and discover how Flux can address these issues. Learn about Facebook chat implementation, the concept of shared mutable state, and scaling actions and queries. Examine the backend perspective, understanding applications as derived data from action history. Investigate techniques for efficient action processing, data store management, and choosing optimal data stores for specific queries. Analyze communication between stores, data enrichment strategies, and the implications of consistency models. Gain insights into stream processing frameworks and the concept of turning databases inside out for improved application architecture.
Full-Stack Flux Architecture in React.js - React.js Conf 2015