I think there is a general misunderstanding of CQRS. What you're explaining here is CQS (Command and Query separation) where commands and queries can still life in the same system. CQRS (Command and Query Responsibility Segregation) takes this one step further and completely isolates commands from queries. Usually putting them in separate systems.
CQS = software design pattern
CQRS = software architecture pattern

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

Written by René Reifenrath

I am a software developer from germany. Blogging about programming and tech related topics. I ❤️ open source and privacy.

Responses (1)

Write a response

That is not strictly true. What CQRS mandates is the separation of read and write models, often achieved by having separate data models or databases optimized for reads and writes. While it is common to take this further by separating the processes…

1