Going global
Use Hong Kong and Singapore as international entry points, deliver static content over the CDN and pool cross-region transfer with shared packages, with cross-border SD-WAN linking your offices.
The challenge
- 01Overseas users see high latency to mainland data centres.
- 02Cross-border transfer costs are hard to predict.
- 03New markets need quick validation without heavy upfront investment.
Reference architecture
How it rolls out
- 01
Pick the right regions
Choose Hong Kong, Singapore, London, Texas or Munich by where users are, and hand static content to the CDN.
- 02
Domains and certificates
Smart DNS sends users to the nearest node; certificates are managed in one place and renew automatically.
- 03
Back to origin over private links
Traffic from overseas nodes back to head office or mainland systems rides the cross-border network instead of the public internet.
- 04
Watch metrics by region
Split monitoring by region so you see at a glance where things are slow or failing.
How a customer uses it
A team selling SaaS into Europe
- Before
- Everything ran in Hong Kong; European customers waited three or four seconds for the dashboard, and syncs back to head office often timed out.
- After
- An app node in Munich, static content on the CDN and back-to-origin over the cross-border network brought European dashboard loads under a second and ended the sync timeouts.
−70%
Load time for European users
0
Sync timeouts
1 week
To open a new region
Design notes
Validate with lightweight servers
Fixed packages with transfer included suit the first release in a new market.
Pool transfer by region
Several elastic IPs in a region share one package so no single IP overruns.
Domains and certificates together
Register domains and manage certificates in one account with renewals in one place.