Recently I spotted a study by Digital Ocean on the adoption of open source that found more than half of developers are contributing to open source projects. Looking at the media coverage, though, I was particularly struck by one headline that suggested employers were lukewarm to open source. The article picked up on one finding that only 25 per cent of employers would contribute more than $1,000 to open source projects. This completely misses the point. It fails to understand why enterprises engage with open source.
To see why this conclusion is in error, we first have to understand how enterprise IT adoption has evolved.
Over 40 years IT departments have grown up on a diet of very expensive, but highly reliable database and enterprise applications. Even now CIOs still have the fabled words "No-one ever got fired for buying IBM" ringing in their ears. IT decision makers were, and still are, understandably cautious about purchase decisions as their businesses have become more reliant on these applications. With IT so mission-critical, CIOs have come to expect first class support to ensure the stability of these critical systems with reliable service providers standing behind them.
But open source turned the situation on its head. With its arrival enterprises were told to dump their long-standing vendor relationships and highly customised on-premise databases for untried open source alternatives, because it would drive cost efficiencies and speed up innovation cycles. At first, CIOs in mainstream organisations refused, worried by the lack of support and SLAs that the traditional commercial vendors offer. However, disruptive competitors in traditional industries like financial services found that unburdened by legacy IT systems, they were able use open source to move more quickly than the incumbents. The pressure to adopt open source accelerated following the financial crash when money was short, even in mainstream, risk-averse organisations, as they sought to keep up, innovate and reduce their existing IT expenditures.
They did not throw caution completely to the wind, however. In highly regulated industries such as financial services, companies cannot tolerate IT system failures - they cost CEOs their jobs. They still demand the reassurances of traditional enterprise IT arrangements, namely enterprise SLAs, 24/7 support and the ability to get bug fixes fast. So they looked for the equivalent in the open source world.
The fact that few enterprises participate in open source foundations could be interpreted as a lack of organisational commitment to open source, but this is just one factor. Indeed, Digital Ocean's research shows employers do want their organisations to participate in open source. Seventy-one per cent of companies surveyed said they expect their employees to routinely use open source projects as part of their day-to-day development work. Over a third of these companies even give their employees time to work on open source projects not related to work!
This suggests a far greater level of comfort with the software than in years gone by. They are certainly far from lukewarm about the technology.
We've come a long way since the days when my colleague Bruce Momjian said it was rare for someone to earn a living from open source software. It is positive that employers are encouraging their staff to engage with open source, because it overcomes the tricky question of how to get paid for contributing to free software. Indeed, this is all part of a significant maturing of attitudes in large corporates when it comes to open source. They may not contribute directly, but funding their employees, who make contributions, is equally important to maintaining the vibrancy of such communities.
In addition to all this employee participation, there is another important way that enterprises contribute to open source projects. That is by working with the software vendors that are the primary contributors to these projects. Of course this isn't done for altruistic reasons. Aside from providing enterprise customers with the support they need, these vendors drive the open source projects forward in a way that helps both the companies paying them and all other users of the software.
At EDB we are contributors to PostgreSQL and provide support to the community version of PostgreSQL, as well as proprietary tools and services and an enterprise-ready version of Postgres. In this way we can be assured of the quality of the core database while customers and users can choose between community and commercial versions according to their needs.
I am confident open source adoption in the enterprise will continue to grow and mature. Employers will embrace open source software as it becomes strategic to their businesses and IT strategies, because it will underpin their agility and responsiveness in the digital era.
However, if employers do not want to increase their corporate contributions to open source projects that is also OK. Many businesses are too busy running their operations to have time to commit code to individual open source projects, but they want to work with partners who do. This gives them access to the benefits of open source, but also gives them the reassurances of support that are vital for mission-critical enterprise applications.
This article first appeared in Computing on January 9, 2019.
Ken Rugg is EDB's Chief Product and Strategy Officer and is charged with leading the company's product and strategic vision. Prior to joining EDB, Ken was the founder and CEO of Tesora. The Tesora DBaaS Platform, based on OpenStack Trove, let enterprises provide self-service database provisioning and full lifecycle management to their developers across 16 different databases, including Postgres, MySQL, Oracle, MongoDB, Cassandra and others.
Before founding Tesora, Ken served as Senior Vice President and General Manager for Enterprise Business Solutions (EBS) of Progress Software which was comprised of a number of enterprise infrastructure product lines. The EBS business unit included the Actional, Apama, FUSE, Savvion, and Sonic products. Ken joined Progress Software when it acquired Object Design/eXcelon Inc. where he served as Vice President, Product Development and Chief Technology Officer.