Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Cloud lockin is here to stay, so learn to love it

Matt Asay | Oct. 26, 2017
To get the benefits of the cloud means tapping into proprietary ecosystems. But there is one way to lessen the impact: change agility.

Cloud lockin is here to stay, so learn to love it
Credit: Wesley Fryer (CC BY-SA 2.0)

With all the gleeful finger-pointing over which cloud provider is the least (or most) generous with open source code, it’s worth remembering that all cloud providers essentially fail when it comes to open source. Why? Because the very nature of their platforms means that their best code remains closed even when openly licensed.

All of which makes your favorite cloud “probably the most proprietary software in the history of software,” as Dremio CMO (and former MongoDB exec) Kelly Stirman says. What to do?

 

You can’t check out of the cloud any time you like

No one likes lockin, but if you take a quick glance around the industry you’ll find that most every category is dominated by a vendor or two that exercises outsized lockin. What started out at Microsoft with its Windows and Office hegemonies moved to Apple’s iPhone, and at the enterprise infrastructure level we’re currently cozying up to Amazon Web Services, Microsoft Azure, and Google Cloud.

“Not to worry!” you say. After all, these companies L-O-V-E open source! Well, they do, but what does that actually mean in the cloud context?

For example, in response to Google’s Miles Ward extolling the openness of Google Cloud Platform, Cloud Guru co-ounder Ant Stanley asked an uncomfortable question: “Can we talk about Big Query and Spanner customers then? Great tech platforms but huge lockin.” Ward, nonplussed, responded, “Apache Drill and ANSI SQL. Next?”

In so doing, Ward sidestepped the gaping void between platforms like GCP and the raw technologies that comprise them. Apache Drill isn’t a real substitute for Google’s Spanner. Sure, at some level, it might replicate some of the features or functions, but to derive value from Spanner you need, well, Spanner—and all the infrastructure behind it.

Again, Ward tried to give the open source response: “:| split writes to newdb. SELECT * at olddb. INSERT * at newdb. Repeat, move reads to new database. I get there are quirks, but there’s no lock.” Yet, again, it doesn’t work, because, as he ultimately admits, the only real way to get the equivalent to Spanner is to “just lay a few thousand miles of fiber, snag a few atomic clocks, get GPS sorted, and, yeah, you’re cool.”

In other words, on-premises, server-based lockin forced you to buy new cloud software to get out of lockin. In the cloud world, you have to buy a new datacenter and all the network infrastructure to go with it. The cloud, in short, has perfected lockin, and open source doesn’t really help.

 

1  2  Next Page 

Sign up for Computerworld eNewsletters.