Code RoomPostgres CDC to warehouse
HardPrep Room Coding #3305

Postgres CDC to warehouse

System designDistributed systemsSenior–Staff~50 min

Design change-data-capture replicating a 4 TB Postgres OLTP database (3k writes/sec, frequent schema changes from a fast-moving product team) into a warehouse and a search index, with end-to-end lag under ~30s. Constraints: the search index must reflect deletes promptly, the warehouse needs full history (every version of a row), and you cannot put meaningful extra load on the OLTP primary. Design the capture mechanism, how you do the initial load without blocking, and how you keep it correct across schema changes.

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:30 left
Estimate5:30 planned
Design16:30 planned
Deep dive13:30 planned
Failure9:00 planned
0:00
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.