2 ms·
> A bit surprised to see Meta here I worked at WhatsApp until 2019. Without details, Meta has a large global userbase, serves lots of video, and stores a large
by toast0 4y ago
> A bit surprised to see Meta here
I worked at WhatsApp until 2019. Without details, Meta has a large global userbase, serves lots of video, and stores a large amount of user data in several datacenters (sometimes with replication across oceans). Being a partner in undersea cables is a good way to get committed international bandwidth at relatively low prices. Meta has lots of cash, and there's a clear ROI, so it's an easy decision.
Take a look at peering DB, Meta is at many (most?) major peering points, because it improves their product, and having dedicated backhaul from peering points to the datacenters makes the service from the peering points better too.
- kccqzy 4y agoAn (possibly) apocryphal story at Google is that when Gmail first launched, they figured that email delivery isn't latency-sensitive, so they purposefully set up compute-intensive jobs (like spam analysis) to be cross continent. When it's night time in the U.S. people aren't doing a lot of web searches, so U.S. servers are relatively idle and the entire world's email delivery processing happens in the U.S.; when the U.S. wakes up all those email processing gets done in Europe. My takeaway is that for large companies cost of international bandwidth isn't such a big factor, at least relative to compute.
- deleted 4y ago[deleted]
- eep_social 4y agoOne of the things I wish I had exfiltrated from a FAANG was the datasheet of ram/cpu/bandwidth/eng hours equivalences for the engineers to make informed decisions on exactly this question.
- kleton 4y agoI'd be surprised if some version of go/rulesofthumb is not in the wild somewhere