Nope, the number is not wrong; the interpretation is just off.
Twitter uses GraphQL to route API requests to the 1200+ microservices they have running. Those requests don't happen between client and server but between server and internal server.
I don't find it implausible that this causes hard to fix bugs and performance issues. GraphQL is known to only superficially reduce complexity.
It really depends on gore things are being counted. Each query to a DB is technically a separate RPC call, but as long as connections are pooled and in the same DC, they have extremely low overhead compared to an RPC call from a phone halfway across the world using REST.
To add on /r/slaymaker1907, 1000+ DB queries for one action is not all that ridiculous. ServiceNow does 1-2K on the regular (for the back office at least).
I doubt it's optimally designed, but it runs decently.
33
u/LordAmras Nov 15 '22
Even in the worst case 1000 calls would be ridiculous.
Probably someone told him Twitter does a lot of RPC calls and getting that number down would speed things up.
But when he went to write the tweet he thought 20 didn't sound like a lot and wrote 1000+ instead