CQRS—Event Sourcing

By 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

Autres articles qui pourraient vous intéresser

The rubber duck debugging method or the art of solving a problem when you’re a programmer

When you write code for software, if there’s one thing a programmer knows for sure, it’s that at some point it will get stuck. No matter how much experience you have, you will find yourself at a dead end with a programming problem that you can’t solve right away. The question to ask yourself in...

Creation of Custom Software | Done Technologies

Do you care about testing?

I recently “talked” to my past self of several years ago, and we came to talk about unit testing. Back then, I did not care about unit testing. Today, I still do not care, but in a different way. Despite years passed, many of the issues raised in this conversation are still relevant. Do you...

Software Development Expertise | Done Technologies

Spike and Emergent Design

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,...

Back to Blog