Cloud Portability: Avoiding Lock-In Without Fighting It

Cloud Portability: Avoiding Lock-In Without Fighting It

The advice to avoid lock-in is often repeated in a tone that suggests any use of a managed service is a mistake. In reality portability is a spectrum, and the useful skill is knowing which dependencies are worth taking and which would be painful to leave.

The costs of leaving

Ask of any service: how long would migration take, who would have to do it, and what would break? For a database with a standard interface, the answer may be weeks. For a service with proprietary semantics woven through the application, it may be a rewrite. The second kind deserves caution; the first rarely does.

Managed services worth taking

Queues, object storage, email delivery, managed databases and monitoring are areas where a provider's reliability and operations are usually better than a small team's. The dependency is real, but the alternative is running it yourself, which is also a dependency, just one you own.

Where portability pays

Keep your own hands off nothing so thoroughly that the system cannot be understood without the console: infrastructure described as code, configuration outside the repository, standard protocols for the parts that connect to everything else, and data stored in formats you can read with ordinary tools. The cheapest insurance is a system a new engineer can still follow.

The middle path

Containers and orchestration buy portability at the cost of operational complexity. For teams without that capability, a simpler deployment on a single provider is the better engineering decision, provided the description in code makes moving possible later.

Decide deliberately

Write down the services chosen, what they would cost to leave, and what would trigger a move. Lock-in is only a problem when it happens by accident, one convenience at a time.

How we approach it

Architecture decisions at Black Origin IT are made during planning, with the maintenance burden and the exit cost both written next to the choice.

Evaluating infrastructure options? Tell us about your project and we will weigh the dependencies with you.