Table of Contents
Go To References #
- Command Query Separation & Events | Code Walks 038 - Christopher Okhravi – CQS: Keep functions either as questions or mutations not both. For cases like pop, or “answering a question changes the answer” cases, or saving a user and returning success or error, use event chains.
Saveperforms the save and if there is an error, instead of returning it, have it publish a
user_save_errorevent, which other consumers are listening to, in order to handle that information.
- Building microservices with event sourcing and CQRS | SpringDeveloper
- Connell Watkins - Onion Architecture with DDD and CQRS | DDD East Midlands Conference - Great comparison of various architectures and how they are similar based on Dependency Inversion, followed by a deep dive into DDD and CQRS