- Really good talk covering mistakes people make when trying to apply event sourcing to a domain
- One mistake: treating event sourcing (or CQRS) as a top-level architecture that applies to everything (apply it separately to some parts of your business model instead)
- Another: pairing it with OO when it’s really more naturally expressed in a functional paradigm (like happening because event sourcing is closely aligned with DDD, which is most often thought of alongside OO)
Original video by Domain-Driven Design Europe:
Domain-Driven Design Europe 2016 - Brussels, January 26-29, 2016 - Organised by Aardling (https://aardling.eu/)
https://dddeurope.com
https://newsletter.dddeurope.com/
https://be.linkedin.com/company/domain-driven-design-europe
https://bsky.app/profile/dddeu.bsky.social
https://mastodon.social/@dddeu@m.aardling.social
Gregory Young coined the term “CQRS” (Command Query Responsibility Segregation) and it was instantly picked up by the community who have elaborated upon it ever since. Greg is an independent consultant and serial entrepreneur. He has 15+ years of varied experience in computer science from embedded operating systems to business systems and he brings a pragmatic and often times unusual viewpoint to discussions. He’s a frequent contributor to InfoQ, speaker/trainer at Skills Matter and also a well-known speaker at international conferences. Greg also writes about CQRS, DDD and other hot topics on codebetter.com.