ProblemsSSA0068

Materialized View Is Behind

Hard

Problem

Paradox Shop's order-history dashboard reads from a materialized view: a read-optimized projection kept current by a projector worker consuming a change-event queue. A write spike can leave the projector needing to catch up a 90,000-event backlog while new change events keep arriving at 750/sec, or else the dashboard starts showing numbers that are minutes stale. Design a projector worker pool from scratch that keeps up with new change events and catches the read model up to a fresh state within 30 minutes. A materialized view needs somewhere to actually live, so wire the projector to a read-model store as part of a complete design; note that only projector throughput, drain time, and cost are graded, not the read-model wiring itself.

Required components

Click to add a component to the canvas.

Additional components

Browse by category. Click or drag a component onto the canvas.

Drag components from the library onto the canvas, then drag from a component's right handle to connect it to another.

100%

Design canvas

Sign up to start designing

Sign up free

Premium is free for 58 more days.

$0 / $330