Command Query Responsibility Segregation: Intro to CQRS
Have you heard about CQRS, but don't know how it could be used? Or, do you have an application that seems to make doing data access hard? The origin of CQRS is from Bertrand Meyer: "every method should either be a command that performs an action, or a query that returns data to the caller, but not both." CQRS takes this a step further by splitting the system into two parts: one that processes the commands (actions) and the other than handles queries (data access). Essentially, separating the Reads from the Writes. In this talk, I'll introduce how I used CQRS in a small Java application using the Axon Framework (axonframework.org). Note that I'm no CQRS expert, so while I'll present what I've learned, I expect that questions will be asked that I won't have a ready answer for, but we can find the answers together.
- Not Interested