Lev Kokotov

PgDog |

[Lev Kokotov @levpgdog]

@gregpr07 Love Zed, my daily driver. I used sublime for years (because its fast, even with 1M+ files), but Zed just rocks for Rust development.

[Lev Kokotov @levpgdog]

@Ferbin08 @garrytan Oh definitely. And we do a lot more than sharding as well. If you need a modern connection pooler, or a load balancer for your database, we got you.

[Lev Kokotov @levpgdog]

@yash1_ @garrytan 1.3M as of today, and it's only been a month!

[Lev Kokotov @levpgdog]

@samokhvalov Love the growth of Postgres-backed queues. When done right, they scale well and provide the much needed durability, transaction guarantees and visibility other queues (e.g. Redis-backed, SQS-backed) do not.

[Lev Kokotov @levpgdog]

Also, check out our newest landing: https://t.co/b2aFDEdvlL

[Lev Kokotov @levpgdog]

1M PgDog downloads! 🚀🚀🚀

[Lev Kokotov @levpgdog]

@ClaranceLiberi @garrytan That's right! PgDog runs everywhere, completely cloud/hardware agnostic. All you need is Postgres.

[Garry Tan @garrytan]

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.

https://t.co/q0Acmi4riq

[Konsti Wohlwend @konstiwohlwend]

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.)

[Lev Kokotov @levpgdog]

Hot take on a hot database: https://t.co/KiHvLslWhZ

[Lev Kokotov @levpgdog]

Super cool new feature just landed: two-phase commit! Atomic, cross-shard writes make us a real, distributed database! https://t.co/ZPGcu8SZID

[Lev Kokotov @levpgdog]

Had fun last week building plugins for PgDog in Rust! FFI isn't so scary once you read all the fine print.

https://t.co/B2K0ocqQu7

[Lev Kokotov @levpgdog]

Databases aren't greenfield projects. I've been working on this feature for a while: we can re-shard Postgres online, terabytes at a time.

https://t.co/gU9u3g1Ya9

[Lev Kokotov @levpgdog]

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.

https://t.co/qJhiKFF0cP

[Lev Kokotov @levpgdog]

I forgot I signed up for twitter (or X, whatever). If you're building multi-tenant apps, check out my latest post: https://t.co/vekg8Uav0X