For much of the history of enterprise technology, companies tended to buy from a single vendor because it made managing the entire affair much easier while giving them a “single throat to choke” when something went wrong. On the flip side, it also put customers at the mercy of said vendor — and it wasn’t always pretty.
As we move deeper into the cloud model, many IT pros are looking for more flexibility than they had in the past, avoiding the vendor lock-in from the previous generation of enterprise tech, and what being beholden to a single vendor could mean for the bottom line and their own flexibility.
This is something that comes up frequently in discussions about moving workloads from one cloud to another, and is sometimes referred to as a multi-cloud approach. Customers are loath to leave their workloads in the hands of one vendor again and repeat the mistakes of the past. They are looking to have the same flexibility on the infrastructure side that they are getting in the SaaS world, where companies tend to purchase best-of-breed from multiple vendors.
That means, they want the freedom to move workloads between clouds, but that’s not always as easy a prospect as it might seem, and it’s an area where startups could help lead the way.
What’s the problem?
What’s stopping customers from just moving data and applications between clouds? It turns out that there is a complex interlinking of public cloud APIs that help the applications and data work in tandem. If you want to pull out of one public cloud, it’s not a simple matter of just migrating to the next one.
Selected by softengoxford