![]() ![]() Traffic destined for datacenters on AWS and Alibaba Cloud enter their respective backbone closest to the target region. The backbones differ significantly in where they ingress incoming traffic, a difference that significantly impacts your end-to-end performance. But, as the report demonstrates, one of the biggest differences between cloud backbones happens before traffic enters those networks. Normally, backbone analysis starts by comparing latency between the PoPs of the backbone. The report, Cloud Performance Benchmark from ThousandEyes, took a close look at the differences between cloud backbones. Backbone Performance Starts Before the Backbone Even backbones with less latency may not provide optimum end-to-end performance. ![]() Latencies between backbones varied as much as 22 percent but that was only part of the story. It provides a picture that’s relevant to any company looking to reduce the cost of their global MPLS network without exposing their SD-WAN to the unpredictability of the Internet. However, even within well-developed Internet regions, Internet performance can be too erratic for some applications depending on the route.Ī recent report evaluated the performance of the major independent backbones gathering latency and loss metrics from several locations across each backbone. Between Internet regions, such from the US or Europe to the Asia Pacific, latency is often too high and unpredictable for enterprise-grade connectivity. We’ve already spoken about the problems of the open Internet and the benefits of private backbones. Alibaba, Azure, AWS, and the Google Cloud Platform (GCP) - all can connect your SD-WAN appliances, offering lower, more predictable latency than the open Internet. One of the most exciting developments to happen in enterprise networking has been the rise of private backbones. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |