Problem
Paradox Shop users need their own reads to stay correct: update a profile, reload the page, and the new data must be there, not stale data from a replica that hasn't caught up yet. Design a load-balanced application and database tier from scratch that keeps a user's own reads current right after their own writes, without giving up replica read scaling for everyone else.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.