How to Build Your Open Source Strategy
A solid open source strategy is important to the success of anyone leveraging open source. In this blog, we discuss open source strategy, why it's important, and best practices for building your own OSS strategy.
What Is Open Source Strategy?
Open source strategy brings together plans for creating, managing, or using open source software.
Do you have an open source strategy? According to Gartner, more than 95% of IT organizations use some form of open source software (OSS) in mission-critical IT workloads. And organizations’ open source footprints are growing annually by 30%. However, more than 50% of open source investments have not resulted in considerable TCO advantages.
To take advantage of the cost savings, increased agility, and innovative technical capabilities that OSS offers, companies need to create an effective open source strategy.
Back to topWhy You Need an Open Source Strategy
You need an open source strategy to mitigate open source risks.
It is well established that open source software is similar to proprietary software and open core software when it comes to potential risks related to security and software quality. However, the low cost of acquiring and adopting open source software drives rapid adoption of numerous open source technologies as well as an often-overlooked side effect, which is a lack of vendor relationships. Companies in this situation can quickly encounter code-management and code-maintenance issues that slow IT staff efficiency and increase risk.
Back to topWhy Open Source Strategy Is Key to Success
In the webinar below, Justin Reock, Ex-OSS Evangelist at Perforce Software is joined by guest speaker and Forrester Principal Analyst Chris Condo, to discuss why open source strategy is no longer optional.
How to Build Your Open Source Strategy
To create a sound open source strategy, first decide whether your organization will:
- Take a self-support approach to open source software.
- Establish a partner network of vendors for open source services including support.
Option 1: Self-Support
According to Gartner, at least 75% of OSS policies do not provide any effective results. Why is this? For years, many companies have supported their own open source software, with the help of open source communities and strictly mandated governance process. However as more open source makes its way into IT stacks, successful OSS governance and support requires increased diversity in expertise. Without the right resources and skill sets, OSS governance can quickly drive up overall costs and create a bureaucratic nightmare — blocking the key benefits that the OSS packages were put in place to achieve.
Option 2: Partner Network
The alternative and more effective long-term OSS approach is to work with trusted vendors for:
- Enterprise-level, commercial SLAs for open source packages.
- Open-core solutions, where the open source technology is commercially packaged with value-added capabilities.
Both types of solutions help ensure that your open source security and quality challenges are addressed. However, before you move forward with a commercial open source solution or open-core package (like Cloudera's Hadoop-based data platform), evaluate the benefits of the package’s proprietary extensions and any risk from vendor lock-in.
Related:Weighing the Value of Apache Hadoop vs. Cloudera
Managing Your Open Source Vendors
As you choose your open source partners, consider the following challenges that often arise when working with more than one organization or group:
- Inconsistent SLAs: Application stacks are developed by combining many building blocks to work together. Having different SLA’s between interconnecting components such as databases, data-streaming technologies, message queues, and underlying operating systems can delay issue resolution. Any lack of clarity in the responsibilities of the organizations supporting each of your components will exacerbate this challenge — and the associated risks.
- Multi-Vendor Finger Pointing: Production problems may involve multiple packages or be difficult to clearly isolate. Lack of communication between vendors forces IT teams to serve as a mediator, distracting them from addressing the core issues. In addition, vendors, especially smaller niche players, often lack direct communication or escalation channels, which can also slow initial response times.
- Disparate Contract Management: As the number of vendors increase, so does the complexity of procurement workflows. Large volumes of contracts — that include widely disparate models for pricing, licensing, legal obligations, and other terms — require significant time to sift through and manage, resulting in backlogs. Working with fewer vendors typically translates into faster procurement and efficiency.
Best Practices For a Successful Open Source Strategy
If your organization plans to scale its open source strategy and footprint, it is essential to keep these best practices in mind when selecting your OSS vendors:
Use the Fewest Number of Vendors to Achieve Your Goals
Minimizing the number of organizations or groups that you work with to achieve your IT goals will always benefit the efficiency of developers, IT administrators, and procurement teams — and lower overall TCO. So, it is critical to choose a single vendor or a small set of vendors that can provide full coverage for your IT stacks as well as the technologies you will need to meet your goals. Another important consideration is checking whether your OSS packages include commercial support, and what the cost is compared with full-OSS-stack enterprise-support offerings.
Go With the Highest Possible SLA
To avoid delays in resolution, you should confirm whether the vendors you are considering can meet your SLA requirements. Do the vendors have the skills needed to provide guidance, quick diagnostics, and resolutions for your mix of OSS technologies?
Avoid Lock-In and Don't Sacrifice Flexibility
IT environments are dynamic. Strict vendor lock-in limits development and innovation agility, which slows your ability to meet changing business requirements. Evaluate vendors to see which packages, application stacks, and infrastructure stacks they support, and confirm what level of freedom you have to use interchangeable components. If your business demands a migration from MySQL to Postgres, CentOS to Ubuntu, or Tomcat to WildFly — you want to ensure that you are empowered to make changes, while still getting the support you need.
Choose Adaptive Services
Innovative vendors that keep evolving their supported open source stacks and services offer an advantage over companies who can’t. For example, let’s say that you implemented a big data stack last year and now you are deploying an infrastructure based on containers that support a data-streaming layer. Can your vendors provide the guidance and support you need to effectively modify your IT using proven best practices?
Back to topMake Your Open Source Strategy Successful
Open source software is driving global innovation. There are thousands of free open source projects today and the number continues to grow each month. To make your use of open source successful, you need the right strategy.
You can build it with the help of OpenLogic experts. OpenLogic provides end-to-end open source services, so you can quickly adopt and effectively manage open source in your development and production environments.
Talk to an expert today to learn how we can help you shape your open source strategy.
Related Content
- Resource Collection - Open Source in the Enterprise
- Blog - Guide to Open Source Licensing
- Blog - How to Build an Open Source Stack
- Recorded Webinar - Best Practices for Building an Open Source Stack
- Forrester Consulting Study - Seize The Open Source Opportunity Through Comprehensive, Optimized Strategies
- Video - Risks of Ignoring EOL
- Video - Open Source Security
