Skip to content
Examples of implementation CQRS with Event Sourcing - evolutionary approach
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
CqrsWithEs.Tests tests added for all rest api methods Feb 27, 2019
CqrsWithEs
NoCqrs.Tests termination outside cover period test added Jan 30, 2019
NoCqrs commands exposed via rest controller Feb 19, 2019
SeparateModels get version and get versions query handlers added Feb 4, 2019
readme-images Add architecture images Feb 15, 2019
.gitignore gitignore added Jan 12, 2019
DotNetCqrsIntro.sln initial cqrs with es version added Feb 8, 2019
README.md Update README.md May 17, 2019

README.md

CQRS and Event Sourcing Intro for Developers

We live in a world of dynamically changing technologies. New ways of architecturing our solutions, new frameworks and libraries seem to appear on almost daily basis.

But good software engineering is not about fancy frameworks and solutions aggressively promoted by their vendors. It is not about doing something because Netflix or Google did it. It is about taking well-thought-out decisions based on facts and knowledge. That’s why it is important to be familiar basic architectural concepts like CQRS. It is one of the tools we use in our software house every day. We mentioned CQRS in the article which is part of the series about Microservices on .NET Core, but it was presented from technical perspective and here we want to focus on basics concepts explanation with visualisation and examples.

Check our article!

No CQRS

No CQRS

Separate Commands and Queries

Separate Commands and Queries

Separate Models Commands and Queries

Separate Models Commands and Queries

Separate Storage Engines

Separate Storage Engines

Event Sourcing

Event Sourcing

You can’t perform that action at this time.