CQRS is one of those patterns that gets oversold, overcomplicated, and occasionally misdiagnosed as a cure for plain old CRUD boredom. The useful version is much simpler: separate the code that changes state from the code that reads state, then let each side evolve for its own job. Martin Fowler describes CQRS as using a different model to update information than the one used to read it, while also warning that for most systems it adds risky complexity. Microsoft makes the same core point in ...