Multi-National eCommerce WebSite Infrastructure
Geographically distant web servers add latency and degrade the shopping experience. Such mistakes can prove costly, resulting in lost customers, missed revenue, and reputational damage.
Route your traffic to your regional Magento Servers based on the user’s location.
When you use geolocation routing, you can localize your web store and present some or all of your websites in the language of your users. You can also use geolocation routing to restrict access to the websites to only the locations you have distribution rights. Another use case is balancing load across endpoints.
You can specify your store geographic locations by continent, by country, or by the state in the United States.
Such Global brands like:
- Helly Hansen
- Ripcurl
- Adobe
- Champion Europe Group
are losing millions of customers worldwide because they are hosted on a slow Magento Commerce Cloud and using legacy multi-store feature when the data center is located in a single geographic AWS region and customers worldwide. Can you imagine your USA-based customers’ frustration when your servers are located in Norway 🇳🇴 or Australia 🇦🇺?
This Open Source Magneto Infrastructure as a cod has multi-regional support for single Magento installation out of the box:
Amazon has determined that each 100ms of latency took them 1% in sales. Google discovered an extra half of a second in TTFB time decreased transactions by 20%.
A 2017 Akamai study determines that every 100-millisecond network lag in website load time can hurt conversion rates by 7% — that is a meaningful reduction in sales. An eCommerce competition is getting harder for online retailers as user experience is becoming critical to e-commerce success.
When accessing a website that is hosted in us-central1A user in Germany uses the following methods to test latency:
- Ping: While ICMP ping is a common way to measure server reachability, ICMP ping doesn’t measure end-user latency.
- Curl: Curl measures Time To First Byte (TTFB). Issue a
curlrepeatedly command to the server.
When comparing results, be aware that latency on fiber links is constrained by the distance and the speed of light in fiber, which is roughly 200,000 km per second (or 124,724 miles per second).
The distance between Frankfurt, Germany, and Council Bluffs, Iowa (the us-central1 region), is roughly 7,500 km. With straight fiber between the locations, round-trip latency is the following:
7,500 km * 2 / 200,000 km/s * 1000 ms/s = 75 milliseconds (ms)Fiber optic cable doesn’t follow a straight path between the user and the data center. Light on the fiber cable passes through active and passive equipment along its path. An observed latency of approximately 1.5 times the ideal, or 112.5 ms, indicates a near-ideal configuration. To download the content and instantiate a connection browser requires 2–3 round trips * N times.
