Complexity

CQRS makes your system more complex design.

Strategically choose where we use and how we can separate read and write database.

▪ Eventual Consistency

The read data may be stay old and not-updated for a particular time. So the client could see old data even write database updated, it will take some time to update read data due to publish/subscribe mechanism.

▪ We should embrace the Eventual Consistency when using CQRS, if your application required strong consistency than CQRS is not good to apply

https://www.redhat.com/architect/pros-and-cons-cqrs