A SaaS platform allows analysts to run aggregation reports directly on the production Postgres database. During peak hours, these analytical queries hold long-running locks and degrade response times for end users. Redesign the data architecture to isolate analytical workloads.
Splitting analytical load (OLAP) from the transactional database (OLTP) ensures heavy reports and long-running aggregations do not degrade app operations — the two workloads have opposing access patterns and compete for the same resources when running on the same database. Data is replicated to an analytical warehouse (BigQuery, Redshift, ClickHouse) and analysis queries run there with zero impact on OLTP. Use it when reports or aggregations on production data are slowing down app queries; accept that warehouse data carries a replication lag, typically measured in minutes.
Evaluation criteria and weights will be revealed after you submit your solution. This ensures a fair assessment of your design skills.
Draw your architecture diagram, explain your design decisions, and get AI-powered feedback.
For the best experience, design challenges on a desktop or tablet — drawing the architecture on a phone is hard.