CQRS design pattern in order to avoid complex queries to get rid of inefficient joins.

▪ Separates read and write operations with separating databases.

▪ Commands: changing the state of data into application.

▪ Queries: handling complex join operations and returning a result and don't change the state of data into application.

▪ Large-scaled microservices architectures needs to manage high-volume data requirements.

▪ Single database for services can cause bottlenecks.

▪ Uses both CQRS and Event Sourcing patterns to improve application performance.

▪ CQRS offers to separates read and write data that provide to maximize query performance and scalability

https://martinfowler.com/bliki/CQRS.html