Key takeaways

• What is CQRS?
• Why we would want CQRS?
• What we in and what we lose get when switching mindset?
• How you can start today with this approach?

Code reflects the way we think, but not necessarily the way it is used. Our programming patterns reflect the simplistic nature of acquiring and changing resources, but in certain cases it doesn't map properly to how the software is used. In this session we will introduce CQRS and explain how our code will now reflect a slightly different paradigm - one more powerful and a better match for how we interact with the software. We will explore how testing is simplified, what is its relation to DDD and how it will affect our overall architecture.