Question

A retail company runs an order-processing system on Azure. The write workload (placing and updating orders) is moderate, but the read workload (order status dashboards, reporting queries, and customer lookups) is extremely heavy and involves complex joins that slow down the transactional database. The architecture team wants to scale reads independently, keep the transactional write model simple, and serve pre-computed query results with low latency. Which application architecture pattern should the architect recommend?

Accepted Answer

Implement the Command and Query Responsibility Segregation (CQRS) pattern with materialized views maintained in a separate read store

Answer

Add an Azure Cache for Redis instance in front of the transactional database to cache all query results

Answer

Enable read replicas on the transactional database and route all reads to the replicas

Answer

Implement the Retry pattern with exponential backoff for all read queries against the database