tl;dr: >[An] architecture is analogous to the redux dataflow model on a react app, but applied to the fullstack. The page has no concrete recommendations as f

tl;dr: >[An] architecture is analogous to the redux dataflow model on a react app, but applied to the fullstack. The page has no concrete recommendations as for what tools could work to implement this pattern except GraphQL. Without a pretty strong knowledge of the tools out there, you won't know how to implement this architecture pattern well. There's a lot of hand-waving past non-trivial problems and there's not much help on what tools/patterns/best practices will help that. For example, the architecture requires a fully async backend, yet that all state changes be atomic. Similarly, the architecture requires `Your event system should deliver the events reliably to other microservices.`. Not a trivial thing to achieve. Also, this architecture promises to `Scale your backend infinitely` because of using serverless services, but because everything is being funneled through a centralized state, That server/database has the potential to be a bottleneck that keeps you from scaling, and the architecture has no advice as to how to build your state to be scalable.