CQRS—Event Sourcing

Par Pyxis

CQRS is a system architecture or design pattern that separates the act of reading data (query) from taking action (command) in order to produce a system which easily scales and provides some useful benefits (such as “playable” event logs) that make the maintenance of the system less burdensome.

Learn more about these topics

Articles

Clarified CQRS

CQRS : An alternative Architecture for DDD

How is CQRS implemented using an ORM

CQRS : Designing Domain Events

Blog posts and Twitter

CQRS

Forums and mailing lists

DomainDrivenDesign (Yahoo Groups)

Code examples

Fohjin

Videos

Erik Rozendaal of Holland talking about CQRS and Event Sourcing

Debates and threads

The value of the Event Store’s events (part 2)

In the previous post, we saw how to create events based on commands. Why not update the database directly? Why do we need to go through an Event Store? Let’s talk a bit about the current situation… Currently, the majority of systems keep their data in a relational database common to several information systems. The...

Software Development Expertise | Done Technologies

Understanding Spikes in Agile Software Development

There is a technique, initially introduced by the Extreme Programming movement, which consists in adding an element to the product backlog that we call a “spike.” The team agrees on a limit of time to be invested in this item. The goal is to acquire the knowledge necessary to reduce the risk, understand a requirement,...

Off-the-Shelf ERP vs Custom ERP for Manufacturers: How to Choose the Right Fit for Your Operations

Off-the-Shelf vs Custom ERP: What’s the Real Difference? Choosing between an off-the-shelf ERP and a custom-built solution isn’t just about features, it’s about how well the system adapts to your factory’s actual operations. While off-the-shelf ERPs offer speed and lower upfront costs, they often come with trade-offs in flexibility and long-term value.On the other hand,...

Back to Blog