The overview is really great, but I think you only scratched the the surface. With ambitious task to cover such a broad topic, it&#x27;s hard to go into all details in one post w&#x2F;o making it unreasonably long. So great work on bringing attention to this topic.<p>I feel some need for code examples as well [as other commenters], but I&#x27;m afraid the post would be bloated with them. Maybe, it&#x27;s worth expanding that into a series of posts - one per architecture&#x2F;approach.<p>Another idea to improve expressiveness of the post would be to draw e.g. ol&#x27;good MVC pattern for comparison. But since your article is targeted for people familiar with the subject, that piece of advice might be not very useful.<p>As for conclusion, I think I cannot completely agree. It seems for me a little like a &quot;silver bullet&quot; solution. On top of that, looking at charts, I can think about a potential problem. Proposed solution requires a lot of internal wiring, which can result in a bunch of glue code.<p>I think that different solutions suit different application patterns. E.g. ones go well with -bacon and cheese- unconnected models&#x2F;stores, the others benefit from centralized data hub.<p>You&#x27;ve started a really interesting topic, but we need to go further. We can benefit more from a deeper analysis.