Downloaded 41 times
Uploaded byChristopher Bennage
Exploring CQRS and Event Sourcing
This document provides an overview of Command Query Responsibility Segregation (CQRS) and Event Sourcing patterns. It defines CQRS as separating reads from writes by having separate models for data access. Event Sourcing represents data as a sequence of events, rather than as a current state. The document then discusses examples of using CQRS with separate read and write data stores. It covers benefits like scalability and integration, as well as lessons learned around testing performance early and avoiding assumptions.
More Related Content
Similar to Exploring CQRS and Event Sourcing
Exploring CQRS and Event Sourcing
- 1.
- 2. Exploring CQRS andEvent Sourcing A journey into high scalability, availability, and maintainability with Windows Azure
- 3.
- 4. What is CQRS? SeparatingReads from Writes Command Query Responsibility Segregation An architectural pattern that separates Commands, that change state, from Queries that only read state.
- 5. Simple Example ofCQRS Segregating Queries Presentation Validation Queries (generate DTOs) Commands Domain Logic Data persistence Based on Rob Ashton’s codeofrob.com/entries/cqrs-is-too-complicated.html
- 6. Taking it further… SeparateData Stores Presentation Validation Queries (generate DTOs) Commands Domain Logic Data persistence
- 7. What is EventSourcing? An Alternate Way to Represent the Data Relational Model Event Stream Shipping Item 1 Cart Created Item 1 Added Item 2 Added Information Removed Added
- 8. CQRS / ES Presentation Validation Read thin-layer Commands Domain Logic Data persistence Based on Rob Ashton’s codeofrob.com/entries/cqrs-is-too-complicated.html
- 9. Eventual Consistency TheTrade-Off • Asynchronous is faster, but may yield stale data • Write Model can be consistent • Write Model is the source of truth
- 10.
- 11. “For the thingswe have to learn before we can do them, we learn by doing them.” ~Aristotle
- 13. Project Objectives • BuildConsensus • Focus on Learning • Leverage Windows Azure
- 14. Decomposing the Domain Conference Discounts Orders & Management Registrations Payments
- 15. demo >> conferencemanagement system
- 16. When to UseCQRS? • Do multiple users compete for access to the same resources? • Are the business rules ever changing? • Is scalability one of the challenges? • Is the business logic complex? • Are benefits that CQRS brings clear?
- 17. Benefits CQRS & EventSourcing • Integration with other systems / screens • Versioning / Evolution • Team development • Testing • Performance can be fine-tuned separately
- 18. Some Lessons Learned • Throw away your assumptions • CQRS space is a little confusing - inconsistency, dissonance • Not a top-level architecture • Not everything needs to be asynchronous, nor message-based • In messaging, tracing matters big time • Test for performance early • Find or build a robust infrastructure that fits your needs • “Sagas” != sagas; Avoid them at first
- 19.
- 20. Resources microsoft.com/practices Project Personal • cqrsjourney.github.com • @bennage • aka.ms/cqrs • dev.bennage.com • aka.ms/cqrspdf
Editor's Notes
- #2 A very popular topic in the developer community.But also an area where there was lots of confusion.This was a different kind of project for p&p.Not about Prescriptive Guidance,More of a Journal of Our Experiences, a Case Study
- #3 Similar to CQS, but applied to a BC/Subsystem as opposed to Objects.
- #4 If you are using an ORM, such as Entity Framework or Nhibernate, then you would have two different models: write and read.There would be no need for lazy loading.
- #5 Now that you have different models, you can go to the next step and have separate data stores.Not required for CQRS.This could be replication, transformation, projection, etc.This is good for scalability. Because READS tend to outnumber WRITES.Queries can be expensive, we want to make them cheaper.
- #8 ES contains a lot more information.Tries to preserve events that make sense in the business (with its intent)To get the current status, you can get the event stream and replay.Not very easy to query other than by ID.
- #9 From Nicomachean Ethics
- #10 We were exploring the landscape.Report our findings.Not a Framework, not a LibraryThe idea is to go through building a non-trivial system that uses CQRS and event sourcing and report back on the lessons learnt.
- #11 Conference Management – setting up a conferenceOrders & Registration – for reserving and purchasing ticketsPayments – for interacting with external payment providerDiscounts – not implemented (et al)
- #19 Infrastructure: needs to scale out? Messaging. code evolution No downtime migrationsIf messaging: follow best practices for scalability.