In the enterprise world, open source has long been a bit tentative. Starting in the early 2000s, various vendors started contributing bits and pieces of code, careful not to give away anything too valuable, all while hoping for positive marketing effect. It was, as in 2007, a matter of gifting complementary technology to secure potential customers’ interest in the core of your business.
It mostly didn’t work.
Today, open source has become a primary driver of innovation, but we’re still too tentative in our contributions. Much of the most impressive innovation is being hatched at the public cloud vendors, specifically Amazon Web Services, Microsoft Azure, and Google Cloud (“AMG,” as ), with , , and more being contributed to the wider open source community.
But in a world where operations—not code—matter most, the AMG trio could contribute all their code without hurting their business, and with potentially much positive effect.
, buoyed by its aggressive push into the cloud.
The cloud is, of course, where all the growth is happening. Combined, the AMG trio has about 60 percent annual growth rate for the public cloud, or 600 percent growth over five years. That’s huge.
But the real story isn’t about growth. You might think that all that growth provides a great foundation for open source innovation, including contributions from the likes of AMG to the community that can be built on for the greater good. After all, as Golden highlights, the AMG triumvirate has “capabilities that no other user or tech vendor on the planet has, and those capabilities can be leveraged to deliver innovation unobtainable anywhere else.”
, which are the bailiwick of AMG.
In short: All this innovation is available to buy; none of it is available to build. Not for mere mortals, anyway.
Google is deliberating whether to open-source its Spanner technology. , spawned by a former Googler, is already working on its own open source Spanner. As good as it is, however, it’s not Spanner. Spanner depends on TrueTime, a powerful way of coordinating resources in disparate places. No one but Google has this technology, although AWS and Microsoft could conceivably build it. Pretty much no one else on Earth could.
Now, multiply Spanner across a range of possible projects, from Google’s TensorFlow to to Microsoft’s . These companies could give you the code (and, in the case of TensorFlow, Google already has), but having the code won’t make you operate like the AMG.
As Golden colorfully describes: “Maintaining the position that making the code available realistically enables someone else to implement Spanner functionality would be like someone handing me a pair of running shoes like the ones Usain Bolt wears and telling me that I can now run a 9.58-second 100 meters. Bolt has the genetics, the training regimen, the ecosystem, and the single-minded drive of a great athlete. Me? I’ve got a pair of sneakers.”
More than a decade ago, Jeremy Zawodny (then at Yahoo) for suggesting his company (and Google) should open-source more code. He rightly pointed out that it’s not that simple and, as he (and Google’s Chris DiBona) had said at OSCON earlier, what would be the point? Giving away a bunch of code that is tightly bound to Yahoo’s infrastructure wouldn’t really give you much insight into how to operate that code like Yahoo. Instead, it might just render you frustrated.
Where the action is: Open-sourcing more on-ramps
Since then, Google in particular has figured out how to both open-source code in a useful way and make it pay. As Server Density CEO , Google hopes to “standardize machine learning on a single framework and API,” namely TensorFlow, then supplement it “with a service that can [manage] it all for you more efficiently and with less operational overhead,” namely Google Cloud.
By open-sourcing TensorFlow and backing it with machine-learning-heavy Google Cloud, Google has open-sourced a great on-ramp to future revenue.
My question: why not do this with the rest of its code?
The simple answer is “Because it’s a lot of work.” That is, Google could open-source everything tomorrow without any damage to its revenue, but the code itself would provide other providers and enterprises only limited ability to increase their revenue unless Google did all the necessary prep work to make it useful to mere mortals not running superhuman Google infrastructure.
This is the trick that AWS, Microsoft, and Google are all racing to figure out today. Not open source, per se, because that’s the easy table stakes. No, the AMG trio are figuring out how to turn their innovations into open source on-ramps to their proprietary services.
Companies used to lock up their code to sell it. Today, it’s the opposite: They need to open it up to make their ability to operate the code at scale more valuable. For them.