HN Showcase
Back to browse
Scry – Test migrations against production scale copy of your DB

Scry – Test migrations against production scale copy of your DB

by gmcquillan·Feb 24, 2026·5 points·1 comment
Visit ProjectView on HN

AI Analysis

●●●BangerSolve My ProblemBig BrainDark Horse

Replay production queries against shadow DB to catch 92x regressions before they ship.

Strengths
  • •Solves a real, specific blind spot: staging has wrong scale and wrong traffic patterns; Scry bridges that gap with CDC-replicated shadow + query replay
  • •Transparent proxy captures workload without app changes; minimal integration friction
  • •Concrete proof in blog post (92x slowdown detected) makes the value credible, not abstract
Weaknesses
  • •Requires production query capture and CDC setup—significant infrastructure lift for smaller teams
  • •Pricing model unclear (Early Access on landing page); unclear if cost justifies value for non-scale operations
Target Audience

Backend engineers, database teams at scale, SaaS companies running production migrations

Similar To

PgBounce · Datadog APM · New Relic Infrastructure

Similar Projects

Developer Tools●Mid

Spawn – Postgres migration/test build system with minijinja (not vibed)

Edit-in-place components + per-migration snapshotting is a neat practical solution to the classic migration-versus-repeatability tradeoff: you keep readable Git diffs for functions but spawn pins exact component versions into lock.toml and compiles them into atomic SQL transactions. Minijinja macros and JSON-driven data generation make writing repeatable tests and fixtures much less painful. The only obvious limit today is Postgres-via-psql only, but the compilation/snapshot model feels like a real workflow improvement for teams that live in the database.

Niche GemWizardry
Winsaucerer
103mo ago