3 ms·
Event sourcing could be a great architecture for general purpose applications - if we had good frameworks and specialized event stores built for this purpose.
by the_duke 5y ago
Event sourcing could be a great architecture for general purpose applications - if we had good frameworks and specialized event stores built for this purpose.
Some features that would be needed:
* Automatic , schema based event and aggregate versioning
* A combined event and aggregate data store with ACID guarantees, schema validation and indexes
* event migrations (so you don't have to carry around old event versions forever)
* Event stream migrations that allow re-writing streams for purging data, gdpr cleanup, etc
* Copy on write based stream clones that can be used for testing with production data
As it stands, such a solution is nowhere to be seen. So you have to cobble together a working system with lots of custom work , which often ends in a complete mess.
- jordanbeiber 5y agoLook at Zeebe[1] for example. If you declare the business process you want to support - either in code or in BPMN, you're automatically mapping out the events that are relevant to the business. Having a system that takes care of executing this, and tying the pieces of this workflow together is one example where ES can shine IMHO. [1]https://docs.camunda.io/docs/product-manuals/zeebe/technical-concepts/internal-processing https://docs.camunda.io/docs/product-manuals/zeebe/technical...