Launching today
PgDog
Scale PostgreSQL without changing your app
134 followers
Scale PostgreSQL without changing your app
134 followers
PgDog is an open source connection pooler, load balancer, and sharding proxy for PostgreSQL. It's Postgres-compliant, fast, secure and built in the open by a community of database engineers.
PgDog
2M qps in production is a real number, not a launch-day claim. the part I'd actually worry about with transparent sharding is cross-shard joins and multi-shard transactions, since that's usually where these proxies either quietly fall back to something expensive or just reject the query outright. does pgdog handle that at the protocol level too, or is there a class of queries you tell people to just not run against a sharded setup
PgDog's connection pooling and transparent query routing is technically elegant. It removes the need to re-architect your data layer, which saves weeks of migration work. We've hit connection saturation issues under bursty SaaS workloads and this seems like a real fix. How does PgDog handle long-running transactions during a shard rebalance or failover?
I appreciate the honesty in positioning this as scaling without forcing app changes. Usually, "seamless scaling" secretly means rewriting half your queries to fit a proprietary router, so tackling this transparently at the protocol level makes a ton of sense.
Wondering what the tradeoff on latency looks like under the hood, when it's intercepting traffic on the fly, is there a noticeable overhead for high frequency, simple reads compared to just hitting standard postgres?
Congrats on the launch! Running a SaaS on Neon's serverless Postgres — connection pooling is one of those things you don't think about until it bites you in production. Couple of questions: how does PgDog handle the connection limit quirks of serverless Postgres vs traditional dedicated instances? And is there a recommended setup for a Next.js + Prisma stack?
finally a pgpooler alternative that actually feels modern, set it up behind our staging cluster last week and the latency under load was noticeably more stable than pgbouncer. love that it speaks the postgres protocol too
Congrats on the launch. One thing that would help teams adopt this faster is a built-in dashboard or web UI for live monitoring of pool stats, query latency, and shard distribution. Most teams using pgBouncer end up bolting on tools like pgwatch2 or custom Grafana setups, so having something more turnkey would be a real differentiator.