OLTP-to-OLAP replication pipeline
Design an OLTP-to-OLAP replication pipeline so analysts can run heavy aggregate queries (revenue by region by day, cohort retention) over a 10 TB transactional Postgres database doing 60k writes/sec, without those analytical queries degrading production OLTP latency. Freshness target is under 1 minute. How do you move data, what target store do you pick, and how do you reconcile updates and deletes?
What a strong answer looks like
Clarify scale and constraints first. Propose a clean component breakdown, then go deep on the hard parts (data model, bottlenecks, consistency, failure modes) and name the trade-offs you are making.
Clarify5:00 left
Estimate5:00 planned
Design15:00 planned
Deep dive12:00 planned
Failure8:00 planned
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.