2 ms·

This article doesn’t really explain event sourcing and some of the trade offs with event driven architecture in general (additional complexity). I’ve heard Git

• nivertech 5y ago
  I started my carrier before the industry consolidated around CRUD, and even before RDBMS/SQL became the go to tool. I only had SQL on large machines (VAX-11), not on PCs. The industry is moving chaotically and sometimes getting stuck in a local minima for a decade. The innovation follows diffusion model, and it slowly builds momentum until the tipping point is reached. So I do agree, that CQRS/ES might be the next informal industry standard, but we do need tooling, best practices, use cases and success stories. Maybe we need a special programming language, a DSL, or a framework for it, or a special DBMS. Another point: it's not that easy to build a correct, scalable and maintainable moderate-complexity CRUD app. Anything beyond a simple blog engine or TODO list tutorial can quickly become a mess. The tutorials are omitting error handling, and that where the juniors are learning from. Last anecdotal datapoint: when building a moderate-complexity CRUD app, and trying to handle all edge cases/error handling/correctness, I realized that I'm building a poor man's CQRS, so I might do the real thing as well.