What is the “CQRS” design pattern? CQRS stands for Command and Query Responsibility Segregation, a pattern that separates read and update operations for a datastore. CQRS separates reads and writes into different models, using commands to update data, and queries to read data. Commands should be business method oriented, such as “reserve funds”, “buy book”, “register user” Queries should never modify database Queries can use “materialized views” specifically optimized for reads; queries can be routed to “replica” as a performance optimmization “Command” can update First Name, Last Name, and DOB, and Query can return concatenated string “full name” and pre-calculated “age” What are the benefits and drawbacks of the “CQRS” microservices design pattern?