![]() ![]() Something that wasn't mentioned was that this is why traders will pay millions to set up servers in DCs/IXs all the way between them and the market so they have more control over the route their traffic takes. After your request leaves your ISPs hardware often you have no choice where it goes next. It's a mix of traffic, peering agreements between providers* and QoS rules on the routers you hop through along the way. ![]() >Sometimes I get weird routing through Asia if a service determines I'm better suited for that. But they couldn't do anything about the sharks :(. Luckily this was a well known risk/issue for our parent company who had a team dedicated to negotiating peering and routing between office locations and their nearest regional DCs (these were not azure, aws, etc. If the primary sub-sea cable was cut, we'd have to route through another which would add at least 400ms round trip extra. The answer was usually "illegal fishing", or "sharks". We had ridiculous bandwidth for the time, which users knew, and they would often come and ask "why can I stream youtube in HD but accessing my document/file takes ages" (ages being anything more than 2-3 seconds). No data at rest (besides riverbed cache) due to security. locally we had firewall, router, riverbed, UPS that's it for max 40 people. ![]() I never really appreciated the relationship and importance of bandwidth, latency and packet loss until I had to move a small office from all on-prem infrastructure to completely cloud based at a regional data centre, about 10 years ago. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |