How One Tech Team Built a Multi-Region Routing System in Under 2 Months

A technology team expanding their Australia-based platform to the United States faced a tight two-month deadline to build a multi-region routing system on Cloudflare Workers. The core challenge was that simply routing users by geography was insufficient, as logged-in users could be travelling or using VPNs, and admins needed seamless access to both regional clusters from a single account. Teaching materials shared across regions added further complexity, since a link created in one region needed to be accessible to users in the other. The team chose not to shard their Firebase authentication service to avoid redirect loops between regions, while opting to shard other databases like Neo4j for simplicity. The result was a purpose-built routing layer designed to balance latency, data consistency, and cross-region usability across two distinct Kubernetes clusters.