[BrentOzar]

I’m not excusing the wild number, but just tossing out some additional load: * Drivers checking in for work, especially if the apps poll automatically * Drivers phoning home with live location updates * Restaurants sending automated updates on order status * Push notifications to users with status changes on their orders * Users with multiple devices (like I have at least 5 devices with the UberEats app)

[jakjak123]

Yes, our server had 120k queries/sec, but 80% of that traffic was driver heartbeats or connection verification. We halved it by disabling the connection verification query.

[javawizard]

Hold up, what do you mean by "our server"? Do you work for DoorDash?

[cdchn]

Even just searching and browsing restaurants and menus is probably dozens of queries for every interaction.

[gizmo]

Serializing json is pretty expensive at scale. I would be shocked if restaurant and menu json doesn't get cached aggressively.

[cdchn]

Bit hard to cache search results.

[fragmede]

depends on how many different queries your think there are. there's a long tail of unique ones, but searching for eg pizza seems eminently cacheable, given magic algorithmic ranking.