3 ms·
> About 1.2 million queries per second at daily peak hours. > About 2,300 total nodes spread across 300+ clusters. > About 1.9 petabytes of data on disk. > C
by xyst 3y ago
> About 1.2 million queries per second at daily peak hours.
> About 2,300 total nodes spread across 300+ clusters.
> About 1.9 petabytes of data on disk.
> Close to 900 changefeeds.
> Largest cluster is currently 280 TB in size (but has peaked above 600 TB), with a single table that is 122 TB.
all of this yet my food still arrives cold af
kidding aside, I wonder if DD has the same problems as Uber or Lyft except with food delivery. Each new "change feed" is a specific region, county/municipality, or city. Federal, state, and local laws all handled delicately.
- orangechairs 3y agoDoorDash's engineering blog has a much more indepth look at their architecture: https://doordash.engineering/2023/02/07/how-we-scaled-new-verticals-fulfillment-backend-with-cockroachdb/ https://doordash.engineering/2023/02/07/how-we-scaled-new-ve...
- beembeem 3y ago> my food still arrives cold af Ha. The first thing I noticed and you almost got to it in your summary: at 1.2MM/2300 = 520 qps per node, this isn't a wild setup. I'm wrapping my head around how they're generating that amount of load. Seems like an easy task for any database to handle.