151–160 of 275 posts
Earlier quoted context omitted.
100k(s) orders per minute is several orders of magnitude more than realistic. Amazon does 20k orders per minute. Instacart doesn't need "100,000s of grocery delivery orders per minute". There must be some 0s added for the sake of the story.
Amazon does 20k peak, or 20k average? Website visitor peaks could easily be two orders of magnitude higher traffic than average for a few minutes.
i'm sure you'll get 100x comments about "why not just have one fast SSD? it can do 2000 trillion writes/s"
Don't pay a startup for your DB proxy, you should own that layer yourself inside of your infrastructure.
"Why Us" => "I ran Postgres at Instacart, where we scaled the company 5x in April of 2020. The biggest problem we had was making Postgres serve 100,000s of grocery delivery orders per minute" Couldn't be a better why us :)
Is 100k order per minute a lot? Even a single Postgres instance should serve that fine?
I really wish they'd acknowledge the prior art and name that they've taken inspiration from - https://github.com/postgresml/pgcat Don't pay a startup for your DB proxy, you should own that layer yourself inside of your infrastructure.
I really wish they'd acknowledge the prior art and name that they've taken inspiration from - https://github.com/postgresml/pgcat Don't pay a startup for your DB proxy, you should own that layer yourself inside of your infrastructure.
Earlier quoted context omitted.
Good thing we support HA as well: https://docs.pgdog.dev/features/load-balancer/ Load balancer with health checks and failover, works out of the box. :) Battle-tested at this point too, so could be worth a look.
I've extensively used Dynamo (internally at Amazon and externally) and even founded a DB startup with it at it's core. Boiling down scalability of Postgres vs Dynamo as it's written in blog is a bit terse. Dynamo scales writes horizontally with the keyspace, forever. Postgres simply can't, and no number of layers between the machines and the developer changes that. Sharding, pooling, Citus are all layered on top of a…
I don’t think the backend matters. It’s the frontend wrapper that makes or breaks HA.
We sharded over 20 TB that we know about. This is probably a typo, right? 20TB isn't that big. I would imagine they've sharded a lot more than that
congrats, lev! brings back fond memories of database fires. i'm sure you'll get 100x comments about "why not just have one fast SSD? it can do 2000 trillion writes/s"