How a Default Dropdown Choice Became a Four-Year Architecture Regret

A proof-of-concept deployment made in an afternoon locked a company's production infrastructure into a cloud region that was never deliberately chosen — simply because it was the default. Over 18 months, the decision hardened around a production database, object storage, and years of regulated data, with no one ever having made a conscious choice. The consequences compounded quietly: latency for most users, legal uncertainty over data residency, reliance on outdated self-managed services, and ongoing cross-region data transfer costs. Author Serguey Shinder argues that cloud region selection is one of the few genuinely irreversible choices in an otherwise elastic environment, making it far stickier than it appears at the prototype stage. He now advocates treating a handful of foundational choices — including region, identity provider, and primary datastore — as one-way doors that warrant at least a brief, documented rationale even during early experimentation.