3 ms·

> It would technically be faster because of lower latency between services in the same data center and sending the final results to the user in one go Which is

> It would technically be faster because of lower latency between services in the same data center and sending the final results to the user in one go Which is a pretty big deal when you have practically the whole planet as users, many of whom are found where low latency is a luxury. > but at the same time if your DB is hit 50 times to service that request, you still have a problem. Maybe. Or when you are Facebook maybe you don't care. Just throw another datacenter at the problem. > without actually improving anything else They found it improved discoverability for designers and non-technical folk. > That tradeoff seems like a tough sell to me If your organization doesn't look like Facebook, I imagine it wouldn't sell. It's very much designed for a purpose.

KronisLV 4y ago
> Which is a pretty big deal when you have practically the whole planet as users, many of whom are found where low latency is a luxury. This is an excellent point! Different scales will need vastly different approaches and the concerns will also differ. Like the anecdotes about a "Google scale problem", where serving a few GB of data won't phase anyone, whereas some companies out there don't even have their prod DBs be that size.
- randomdata 4y ago
  Another thing to consider is that while a query may be dynamic during the discovery/development phase, once it is solidified in the application for deployment it becomes static and is able to be optimized as such. If you are a small team of developers that is no doubt a lot of unnecessary indirection. When you are small you can talk to each other and figure out how to create a service that returns the optimized results right away. At Facebook scale, if everyone tried to talk to each other there would be no time left in the day for anything else. Conway's Law strikes again.

KronisLV 4y ago

> Which is a pretty big deal when you have practically the whole planet as users, many of whom are found where low latency is a luxury. This is an excellent point! Different scales will need vastly different approaches and the concerns will also differ. Like the anecdotes about a "Google scale problem", where serving a few GB of data won't phase anyone, whereas some companies out there don't even have their prod DBs be that size.

randomdata 4y ago
Another thing to consider is that while a query may be dynamic during the discovery/development phase, once it is solidified in the application for deployment it becomes static and is able to be optimized as such. If you are a small team of developers that is no doubt a lot of unnecessary indirection. When you are small you can talk to each other and figure out how to create a service that returns the optimized results right away. At Facebook scale, if everyone tried to talk to each other there would be no time left in the day for anything else. Conway's Law strikes again.