Read replica visualization pattern
Skill kjuhwa/skills-hub/skills/design/read-replica-visualization-pattern
Self-correcting knowledge corpus for Claude Code — 9 stable shape clusters, bias-correction pipeline baked into contribution flow. 47 papers, 45 techniques, 1.1k skills.
npx -y skills add kjuhwa/skills-hub --skill read-replica-visualization-patternAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Canvas-based topology visualization for primary-replica clusters with lag indicators and routing flows
SKILL.md
2.1 KB, 377 tokens by cl100k_base, as published. Nobody here has run it
read-replica-visualization-pattern
Read-replica systems need a visualization that makes three things legible at a glance: the primary node, the set of replicas, and the replication lag between them. The recommended pattern places the primary at the center (or left) with replicas radiating outward, connected by directed edges whose thickness or color encodes current lag (green <100ms, amber 100-1000ms, red >1s). Each replica node should display its role (sync/async), lag in milliseconds, and current query load as a small inline badge, so operators can correlate routing decisions with replica health without hovering.
Query routing should be animated as discrete particles traveling along edges: writes always flow to the primary (solid line, distinct color like blue), reads flow to the selected replica (dashed or lighter line, green). When a read hits a stale replica, flash the particle red at the destination to make consistency violations visible. For the lag-monitor variant, add a stacked time-series panel below the topology showing lag-per-replica over the last 60 seconds, with threshold lines for the app's consistency SLO. For the router-playground variant, overlay the current routing strategy (round-robin, least-lag, weighted, primary-fallback) as a label on the primary, and let users swap strategies to see the particle distribution shift in real time.
Keep the rendering stack lightweight: SVG for the topology (easy to label, animate via CSS/requestAnimationFrame), Canvas only if replica count exceeds ~50 nodes. Expose a speed-control slider (0.25x–4x) because replication phenomena at real-world timescales are either too slow to observe or too fast to trace — users need to scrub through scenarios. Always pause on hover over a node to freeze the lag readout; otherwise ticking numbers are unreadable.