Mini training - EventStore

Transcript

1. EventStore Play with events
2. Event Sourcing Persist our domain model by persisting just the events instead of the current state
3. Append Only Model When you update or delete data you lose information Events are the result of decisions, they should be immutable
4. Advantages No loss of information One source of true Go back in time Free audit logs Immutable data « Easy »migration Replay feature
5. But How to Store Events?
6. Event Store The open-source, functional database with Complex Event Processing in JavaScript.
7. No Table but Event Streams No giant stream Partitions by aggregate Million of streams is normal 5000 - 10000 events before any snapshot
8. Event Store Operations Append to a stream Read all or part of a stream Subscribe to a stream
9. What About Queries? You don’t query on events but on appropriate read model There is no best storage AKA all database sucks One model can’t be good for all scenarios
10. Read Models Events Graph Dd Document Db SQL Db
11. Clients HTTP Based on Atom feed HTTP content type negotiation HTTP persistent connection HTTP pipeline HTTP cache TCP .NET, Ruby, Java Really fast communication protocol
12. KEEP CALM IT’S DEMO TIME!!!
13. Thank you Any question?