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 Fowle...
Source: [Dev.to](https://dev.to/rosgluk/implementing-cqrs-in-go-a-practical-guide-to-scalable-architecture-3iik)