ES is a wonderful concept, but comes with many pitfalls and design contraints that are very different from the classic CRUD workflow, which is what most devs a

ES is a wonderful concept, but comes with many pitfalls and design contraints that are very different from the classic CRUD workflow, which is what most devs are familiar with. The biggest problem is the lack of available tooling. The only custom built ES database is Eventstore [1], and it has many issues. Many are abusing solutions that were not built for the use case (like Kafka), and end up hand-building a lot of related functionality that often ends up brittle. Ad new purpose-built DB could do wonders for the space if it had these features: * Horizontally scalable * schema validation for events * schema migrations and event upcasting * Built-in projections + state rebuilding * index projections * something to help out with cross-aggregate sagas and coordination, and maybe even cross-aggregate transactions * Spinning up mirror replay databases up to a certain time/event [1] https://eventstore.org/ https://eventstore.org/