PgDog founder. Rust and Postgres nerd.

San Francisco
Our most important tools are open source. Postgres, Linux, Firefox, and git, all the programming languages we use, just to name a few. There is no reason why sharded Postgres shouldn't be as well. pgdog.dev/blog/why-open-sour…
3
3
30
1,978
Looking for an amazing Rust engineer to join our team at pgdog.dev! We are building sharded Postgres that works everywhere, incl. your cloud, CI, or local dev.
11
4
49
3,777
PgDog just reached 2M downloads! It took us a year to get to the first million, and only 3 months to get to 2.
1
13
530
Lev Kokotov retweeted
ParadeDB is now natively available in Postgres.app for all macOS users out there! postgresapp.com/extensions/
5
30
2,434
I ran PgBouncer for years. It's an awesome piece of technology, solid as a rock. But I think it's time to try something more Postgres-compliant. Read more about why we wrote "yet another" connection pooler for Postgres here: pgdog.dev/blog/why-yet-anoth…
6
20
128
10,461
Proudly announcing PgDog's $5.5M seed round from @BasisSet, @ycombinator, @pioneer_fund, and others. Running Postgres in prod is hard. PgDog is a modern connection pooler, load balancer and database sharder. It can be deployed anywhere and works with all Postgres hosts, incl. RDS Postgres, Aurora, Cloud SQL, Supabase, Neon, etc. Some cool numbers: 2M+ queries per second in prod, 20TB+ sharded, 50+ open source contributors. 1 year down; here's to 10 more.
20
13
175
26,858
Also, check out our newest landing: pgdog.dev/
1
6
694
1M PgDog downloads! 🚀🚀🚀
1
2
15
26,769
Lev Kokotov retweeted
Are your Postgres servers melting down right now? Congratulations AND you need PG Dog - the founder Lev is one of the world's experts at scaling and sharding databases - he did it for Instacart and his software can do it for you. If your replicas are falling behind and your IOPS are pegged, it's time. pgdog.dev/
40
30
575
135,157
hot take: databases should be single-threaded someone a long time ago decided that database shards should be multi-threaded. ever since then, we've had to worry about transactions, serializability, race conditions, and locking. instead, we should have single-threaded shards, and shard aggressively and early. we switched from servers to serverless by building apps with statelessness in mind. it's time to switch from multi-threaded DBs to sharded single-threaded DBs by building apps with sharding in mind. many will say that you can't JOIN across shards if you do this. but if you're JOINing across shards on your *writer* node you're already doing something wrong in the current world. your read replicas will still be able to JOIN just fine. that way, scale comes naturally with no extra effort. sharding sounds hard but is it really harder than worrying about transaction guarantees with every query you do? (yes, i'm serious. at the very least i think this type of database is extremely underexplored.)
40
8
293
98,319
Super cool new feature just landed: two-phase commit! Atomic, cross-shard writes make us a real, distributed database! docs.pgdog.dev/features/shar…
3
350
Made a video about load balancing in PgDog. You can get 99.99% availability with just plain old Postgres and horizontal scaling for your read queries...without changing a line of code in your app. piped.video/ZaCy_FPjfFI?si=Dy7_…
1
2
4
1,377