Guest: Alex Chircop (LinkedIn)
Company: Akamai (Twitter)
Show: Open Source and Opinionated

Lock-in can exist in both proprietary and open-source solutions, where it can be beneficial or harmful depending on how it’s managed. In this show, Alex Chircop, Chief Product Architect at Akamai, discusses the dual nature of lock-in, highlighting the importance of companies contributing to open-source projects, the complexities involved in using Kubernetes, and the challenge of balancing the convenience of managed services with the need for long-term flexibility and innovation.

Understanding lock-in: balancing standardization and diversification

• Chircop defines lock-in as neither inherently good nor bad, emphasizing that its impact largely depends on context and the specific needs of the organization. He elaborates that different business models and strategies may yield varying perspectives on lock-in.
• Chircop explains that standardizing on a specific SaaS product or cloud provider can drive innovation and streamline operational complexity, creating a more simplified environment for businesses. It can enhance collaboration and integration across teams.
• Lock-in is commonly viewed negatively because it often forces companies to diversify their tech stack. This can be particularly problematic for larger organizations with complex infrastructures that are resistant to change due to established processes.
• Triggers that lead to diversification include changes in the market ecosystem, mergers and acquisitions, or alterations in licensing agreements, which can compel companies to reconsider their technology choices.

Evaluating the risks and benefits of open source and lock-in

• Chircop talks about whether open source can completely eliminate lock-in saying that lock-in can still occur, especially with less mature or more niche projects. He explains that the lack of community support and documentation can exacerbate these risks.
• Chircop provides examples like Kubernetes and Linux, where there are alternatives but switching can be resource-intensive and complicated. While alternatives exist, the migration process often requires significant time and expertise.
• Despite the challenges, open source generally offers more flexibility compared to proprietary solutions, as alternatives are more accessible. This flexibility allows companies to tailor solutions more closely to their specific needs, fostering innovation.
• Unexpected events, such as license changes or the failure of a startup offering a SaaS product, can cause shifts within the open source landscape, necessitating changes in strategy.

Overcoming challenges of maintaining open source software

• Chircop explains how open source software can become complex to maintain noting that while open source software may be free to obtain, it often incurs costs when it comes to usage, such as maintenance, ongoing support, and keeping up with updates. These hidden costs can catch organizations off guard.
• The specific challenges companies face with open source software include the need to manage security vulnerabilities and new releases. Chircop highlights the urgency of staying updated with patches and security advisories to protect against potential threats.
• Chircop highlights the significant knowledge and skills gap in managing open source projects, particularly in less mature spaces where external support might not be readily available.
• Many cloud providers offer managed services to simplify the process, but this convenience can create lock-in, as businesses become reliant on specific tools within a provider’s ecosystem.
• Chircop stresses the need for companies to carefully evaluate these dependencies to ensure they maintain control over their technology stack.

Encouraging greater contributions to open source communities

• Chircop notes that open source plays an essential role in the majority of modern projects, with many products built on open source foundations, making its use inevitable in today’s tech stacks. It is not just beneficial but necessary for staying competitive.
• Despite this, Chircop admits that while some companies contribute to open source, the level of involvement often falls short of expectations, leaving key projects maintained by just a few individuals, leading to potential sustainability issues.
• Chircop encourages companies to explore different ways of contributing to open source, whether through organizing meetups, working on documentation, or participating in online discussions.
• Chircop stresses that even small contributions can make a meaningful impact and urges companies to shift from merely consuming open source to actively participating in its growth and sustainability.

Steps for small and large companies to support open source

• Chircop offers advice on how companies, regardless of size, can become good open source citizens and contribute meaningfully. He seeks practical suggestions that organizations can implement.
• Chircop discusses the obstacles that both small and large companies encounter when trying to contribute, such as navigating legal agreements and overcoming internal bureaucracy. He emphasizes that these challenges can stifle motivation and hinder proactive engagement.
• Chircop suggests that organizations integrate open source participation into their company culture and workflows, especially if they are heavily reliant on open source stacks. Chircop recommends creating dedicated teams or roles focused on community engagement and contribution.
• Chircop explains that contributions don’t have to be large; companies can support open source efforts in specific areas like security, networking, or through improving particular aspects of distribution. He highlights that even minor contributions can lead to significant improvements in project sustainability.
• Chircop concludes by advising companies not to be intimidated by the scale of open source projects and that even small, targeted contributions can have a substantial impact. Chircop encourages organizations to see their participation as part of a larger ecosystem where every contribution matters.

Selecting Kubernetes providers: balancing managed services and flexibility

• Chircop discusses how companies should approach selecting Kubernetes providers to avoid lock-in while benefiting from the platform. He explains that Kubernetes enjoys a broad community and ecosystem, ensuring it remains open and non-proprietary despite heavy investment from multiple stakeholders.
• Chircop acknowledges the complexity of the Kubernetes ecosystem, which spans multiple domains such as networking, service mesh, ingress, observability, security, and storage. Understanding this complexity is crucial for making informed decisions.
• While managed Kubernetes services can provide a quick and efficient solution, they can also introduce lock-in as companies rely more on specific provider features. Organizations need to carefully assess the trade-offs of managed services against their long-term flexibility needs.
• Chircop advises businesses to strike a balance between utilizing the benefits of managed services and ensuring they maintain diversity in their tech stack as their needs evolve over time.

The importance of KubeCon for open source collaboration and innovation

• Chircop shares that Akamai is a key sponsor at KubeCon, with a large booth and multiple speakers contributing to the event, showcasing their active involvement. He expresses excitement about the opportunity to engage directly with the community.
• Chircop describes KubeCon as a central gathering for open source contributors, where thousands of people come together to share insights, collaborate, and push the community forward.
• Chircop highlights the value of the event in aligning on key initiatives and planning the future direction of open source projects over the next six months. He notes that these discussions can help shape the roadmap for future developments and innovations.
• KubeCon offers a valuable opportunity for learning, collaboration, and sharing best practices within the community. Chircop underscores that the connections made at KubeCon can lead to fruitful collaborations beyond the event itself.

Expectations from KubeCon: engaging with the community and sharing insights

• KubeCon has evolved significantly, now focusing on mature use cases, scaling challenges, and securing existing cloud-native environments. This shift reflects the maturing needs of the community as they tackle complex real-world problems.
• Chircop points out that a significant portion of attendees are first-time participants, offering an opportunity to educate them on good practices and help them bring new knowledge back to their teams.
• Chircop emphasizes the blend of seasoned users and newcomers, making KubeCon a key event for both advanced learning and onboarding the next generation of contributors.
• Chircop looks forward to engaging with the diverse audience and sharing Akamai’s experiences and ongoing work within the Cloud Native Computing Foundation (CNCF). Chircop views this as a chance to not only showcase Akamai’s contributions but also to learn from the broader community.

This summary was written by Emily Nicholls.