Problem
Paradox Shop users update their profile, then immediately reload the page; and sometimes see their old data, because that read landed on a replica that hasn't caught up yet. The application and database tier below are already live and already split reads to a replica; fix the routing so a user's own reads stay 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.