I think when architechture fails, its a failure to understand the problem you're trying to solve and the value an architecture gives you. Some problems are suc

I think when architechture fails, its a failure to understand the problem you're trying to solve and the value an architecture gives you. Some problems are such you don't need audit, you don't need to roll-back time and you don't need multi-database coordination. Then you don't need event sourcing. CQRS is a more generic concept, but you also often don't need it. That's because RDBMS do CQRS for you. You can design tables in a normalized way, to maximise writes, updates and deletes guarantees and consistencies. And then you can do whatever query projection you need. All view aggregation is magically handled by the RDBMS for you. You need to manually implement CQRS when that RDBMS limits your scale or performance.