Software Architecture: Going International
The Business Goal
Byte Burger enters new countries. Customers expect responsive ordering; regulators and partners impose data-location and recovery requirements.
The Story
Customers in the new country wait several seconds for checkout because the order path still crosses an ocean. Then a local regulator asks where loyalty records live and how quickly they can be recovered after a regional outage. The old single-country kitchen is no longer a neutral choice. Copies of data, regional deployments, and failover plans all create cost and consistency consequences. The company names which data must remain local, which can travel, and how much disruption the business can tolerate.
The Decision
Choose regional placement, replication, routing, and disaster recovery from latency, residency, RTO, and RPO requirements. Distinguish a backup from a tested recovery path and a global diagram from an operational capability.
Decision Record
| Field | Decision |
|---|---|
| Valid while | Regional complexity earns measurable customer, regulatory, or resilience value |
| Operational tax | Data governance, failover testing, cost, observability, and operational ownership |
| Invalidation trigger | The business retreats, requirements simplify, or the regional estate cannot be operated safely |
| Reversal path | Consolidate regional machinery when demand, regulation, or recovery needs no longer justify operating it separately |
The Last Bite
Geography is an architectural constraint only when a real customer, legal, or recovery requirement makes it one.
Next chapter: Software Architecture: We Built Too Much
Regional machinery solved real constraints, but success has also made complexity feel automatically virtuous. Byte Burger must measure which boundaries still earn their cost.