The Challenges of Open Source in the Enterprise
There is an old Chinese curse, “may you live in interesting times.” Of course, we all want to live in interesting times, but sometimes the interesting part can be a bit much. The enterprise is an interesting place. On the one hand, real enterprises have technology budgets that are quite large, sometimes even running into billions of dollars. Much of that budget is for labour, meaning that a successful enterprise technology person can make very good money, while learning a lot on the way. Although your typical tech shop may have a few servers and program in, say, Ruby, with an HTML front end backed by MySQL, in an enterprise, you are likely to encounter, and learn, every technology out there. If you like Ruby, it is there; Java, most certainly; .NET, that too. If your preferences run to infrastructure, you are likely to find everything from Windows servers to Linux to UNIX variants to mainframes to the unexpected. As recently as 2001, I worked as head of enterprise management at a place that had a massive farm of DOS 3.1 PCs; those were “interesting times”.
On the other hand, enterprises don't start or end with cool technology, and they are there to serve a business purpose. The most famous illustration of this is the Nine-Layer OSI Model by the legendary Evi Nemeth.
Sure, you may have the best solution to a problem, but in an enterprise, you need to get the budget approved—on a multiyear cycle, of course—and then you likely need to go before some sort of capital expenditure (CapEx) or major expenditure review (MER) committee. Everyone there views your request as competing with their priorities for 1) budget allocation, because even a $1-billion IT budget is still finite, and 2) recognition and promotion, because after all, they want you to succeed, but they want their own projects to succeed even more. Finally, enterprises have legitimate business support needs that may or may not be resolved by your open-source solution.
At base, everyone interested in open source is interested in technology, so let's address the technical challenges first. As you may have noticed, enterprises spend a lot of money. Unsurprisingly, to quote Willie Sutton who used to rob banks because “that's where the money is”, many commercial technology businesses build products to focus primarily on the enterprise and solve its unique problems, and they have very large sales and marketing budgets to sell them. On the other hand, open-source products often are built, at least initially, to solve very specific problems.
Thus, before advocating for open source, we need to understand if the open-source solution solves the problem as well as the commercial solution, given the entire requirements set. This includes not just the immediate technical problem, such as “serve up a Web page”, but also the management challenges that can be unique to an enterprise, such as “replicate in real-time across 15 databases in ten countries around the world, while instantly alerting to any degradation and providing service-level agreement (SLA) reporting”. In many cases, open source has indeed developed to the point where it truly can compete on a technical requirements level with commercial products. In other cases, it is not yet sufficiently evolved, but it may be some day. And in some cases, it is literally impossible to solve the problem with open source. Let's examine two extreme examples.
Web servers: the dominant Web server for many years, of course, has been Apache. Although various competitors nip at its feet, such as IIS for Windows or nginx for sheer performance, Apache remains dominant for both intranet and Internet Web serving. In 2010, it is not hard to make the argument to adopt Apache for a Web server solution in the enterprise. It is mature, established, lots of well-known companies bet the business on it, and it has the various controls, hooks, logging and security that an enterprise demands. It is important to remember, however, that only a few years ago, Apache was not sufficient, and other commercial variants arose to fill in the gap, such as Apache Stronghold. The combination of a mature product, a complete enterprise-ready feature set and broad enterprise adoption make open-source Apache a selection as valid as any commercial solution.
Network infrastructure: in the old days, when we had to decide whether to route mail via UUCP or SMTP, we built our own firewalls. Routers simply were dedicated servers with multiple network interface cards (NICs) on which we ran software to route the traffic. Over time, however, the proliferation of networks and the demand for traffic-routing capacity and intelligent control exceeded the capabilities of these homegrown solutions. Special companies were formed to create specialized networking hardware. The most famous, of course, is Cisco. Although a small organization can make do with a simple router, or even a dedicated box with a few NIC cards running m0n0wall, such a solution is highly unlikely to work in a large enterprise. There, the complexity, traffic demands and management requirements, as well as a three-tier architecture (core, distribution and access layers) can be done far more cost effectively, and in some cases, only with a hardware solution. Clearly, open source is not about to run enterprise networks. Having said that, it is not impossible that a split could occur. Currently, enterprise network equipment manufacturers provide both the hardware and software to manage routing, some of which may be based on open source, such as Cisco ASA 8.x. It is possible that in the near future, a pure-hardware networking equipment manufacturer could be formed that would sell the hardware only, while software is provided via an open-source solution, in a manner similar to current servers.
The important takeaway from evaluating any technology is that it has to solve the immediate problem, such as serving Web pages, but also have the features required for an enterprise, such as management, logging and security. Rarely does it matter that the open-source product may be better or that you want to support the community that brought us Linux/Apache/whatever. For adoption in the enterprise, the rule remains, as it should anywhere, first solve the actual problem and everything related it.
|PasswordPing Ltd.'s Exposed Password and Credentials API Service||Apr 28, 2017|
|Graph Any Data with Cacti!||Apr 27, 2017|
|Be Kind, Buffer!||Apr 26, 2017|
|Preparing Data for Machine Learning||Apr 25, 2017|
|openHAB||Apr 24, 2017|
|Omesh Tickoo and Ravi Iyer's Making Sense of Sensors (Apress)||Apr 21, 2017|
- Graph Any Data with Cacti!
- Teradici's Cloud Access Platform: "Plug & Play" Cloud for the Enterprise
- The Weather Outside Is Frightful (Or Is It?)
- Simple Server Hardening
- PasswordPing Ltd.'s Exposed Password and Credentials API Service
- Understanding Firewalld in Multi-Zone Configurations
- Gordon H. Williams' Making Things Smart (Maker Media, Inc.)
- IGEL Universal Desktop Converter
- Server Technology's HDOT Alt-Phase Switched POPS PDU
Pick up any e-commerce web or mobile app today, and you’ll be holding a mashup of interconnected applications and services from a variety of different providers. For instance, when you connect to Amazon’s e-commerce app, cookies, tags and pixels that are monitored by solutions like Exact Target, BazaarVoice, Bing, Shopzilla, Liveramp and Google Tag Manager track every action you take. You’re presented with special offers and coupons based on your viewing and buying patterns. If you find something you want for your birthday, a third party manages your wish list, which you can share through multiple social- media outlets or email to a friend. When you select something to buy, you find yourself presented with similar items as kind suggestions. And when you finally check out, you’re offered the ability to pay with promo codes, gifts cards, PayPal or a variety of credit cards.Get the Guide