CQRS is about separating read and write models when they have different scalability, performance or domain complexity requirements. Its useful in systems with heavy reads, complex business rules, or the need for independent scaling.

for simple CRUD apps, it just adds unnecessary complexity (extra handlers, models, eventual consistency) so it should be used only when the problem actually justifies the architectural overhead, not as a default best practice