.png)
![‘Companion’ Ending Breakdown: Director Drew Hancock Tells All About the Film’s Showdown and Potential Sequel: ‘That’s the Future I Want for [Spoiler]’](https://variety.com/wp-content/uploads/2025/02/MCDCOMP_WB028.jpg?#)
Is CQRS CQRS without separate read and write data stores?
Is having a separate read only and write only data store a core part of CQRS, or does it still make sense in some scenarios to do CQRS with a single data store? Asking because a coworker is using CQRS terminology in a project. Whether or not he's actually using the pattern I can't say because I'm not familiar enough with it to know, but my first impression is that it's just a regular REST service where he is using separate objects for saving data with POST operations than the ones used to retrieve data with GET operations. My first impression on CQRS is that the shape of the data at rest is different for reading and writing, whereas here the same database is used for both. Am I perhaps missing something about the purpose of CQRS and its usefulness in a scenario like this?
Is having a separate read only and write only data store a core part of CQRS, or does it still make sense in some scenarios to do CQRS with a single data store?
Asking because a coworker is using CQRS terminology in a project. Whether or not he's actually using the pattern I can't say because I'm not familiar enough with it to know, but my first impression is that it's just a regular REST service where he is using separate objects for saving data with POST operations than the ones used to retrieve data with GET operations.
My first impression on CQRS is that the shape of the data at rest is different for reading and writing, whereas here the same database is used for both.
Am I perhaps missing something about the purpose of CQRS and its usefulness in a scenario like this?
