Language Selection

English French German Italian Portuguese Spanish

Why open source won't prevent cloud lock-in

One of open source's promises is to minimize vendor lock-in. However, it's not so apparent that this value proposition holds when using software as a service (SaaS) or cloud-based platform services. The implication is clear: So-called open source cloud platforms, like the recently announced VMforce, are no more open than proprietary clouds -- and believing otherwise will trap you into unintended lock-in.

Open source helps, but isn't sufficient to provide future freedom of action

The VMforce offering reveals specific issues about open source's relationship to cloud lock-in. But before I get to those, I need to remind you that even in on-premise deployments, open source doesn't necessarily prevent vendor lock-in.

It's true that access to a product's source code can increase the freedom of customer choice and minimize the risk of vendor lock-in.

rest here




More in Tux Machines

Linux 4.9-rc8

So if anybody has been following the git tree, it should come as no surprise that I ended up doing an rc8 after all: things haven't been bad, but it also hasn't been the complete quiet that would have made me go "no point in doing another week". Extra kudos to Arnd, who actually root-caused the incredibly annoying "modversions do not work with new versions of binutils", bisecting it to a particular change to symbol handling in binutils, and then adding a small one-liner patch to the kernel to work around the issue. We already had other workarounds in place, but it's always good to know exactly what in the tool chain changed to cause things like this. Read more Also: Linux Kernel 4.9 Slated for December 11 Release as Linus Torvalds Outs RC8 Linux 4.9-rc8 Kernel Released