3 ms·
If you serve data from a DC in California to the west coast of Australia it will take 10 seconds of just network transfer time. Sometimes data has a high degre
by coolhand2120 3y ago
If you serve data from a DC in California to the west coast of Australia it will take 10 seconds of just network transfer time. Sometimes data has a high degree of cardinality and cannot be cached. Some companies cannot afford to, or for other reasons cannot, have regional instances of their compute surfaces. This is just one common scenario, there are many others.
> A middling back end system with median complexity is doing 10-100K requests per second per server and is near-perfectly horizontally scalable.
You know perfectly your SLAs without knowing anything about the business, data, or the user access pattern? You don't even need a budget? Impressive!
- hipadev23 3y ago> If you serve data from a DC in California to the west coast of Australia it will take 10 seconds of just network transfer time. What? Is this a typo or do you think that’s true?
- willsmith72 3y ago> If you serve data from a DC in California to the west coast of Australia it will take 10 seconds of just network transfer time Where did you get that calculation? Looks way way off
- felixgallo 3y agoYou have no idea what you're talking about. Perth is about a third of a second away from Los Angeles. There is no data that cannot be cached owing to 'high cardinality'. There does not exist a company that is trying to serve Perth traffic from a US CA DC that cannot afford a server that can do 100k RPS.
- firecall 3y agoAs a fellow Australian here in South Australia, I can say with certainty that I've never had it that bad! I can measure the difference between US, Singapore and Sydney based DCs, but it's milliseconds. 10 seconds is abnormal and would indicate to me that something isn't functioning as expected!