Problem
Paradox Shop needs to replicate user-profile data for fast reads everywhere, but a naive replicated design risks a visible bug: right after a user updates their bio or avatar, reloading the page could still show the old version if that read lands on a replica that hasn't caught up yet. Design a data tier from scratch where a user's own read immediately after their own write always reflects it, while everyone else's general profile reads keep scaling through a cache instead of hitting the store directly.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.