In this episode of TFiR Insights, Kapil Thangavelu, Co-founder / CTO of Stacklet joined me to talk about his new company that is solving some of the biggest problems facing users who are embarking on their cloud native and digital transformation journey.
Kapil is a technical luminary in the area of cloud computing having most recently worked at Amazon Corp on the AWSOpen team. He created Cloud Custodian at Capital One so developers can have the freedom to use cloud native tools and resources with the right guardrails in place to ensure they use infrastructure inline with best practices, and he’s the lead maintainer. At Canonical/Ubuntu, he was a core developer on Juju, an open source, cross-cloud orchestration and provisioning product. He is passionate about open source and building infrastructure and developer tooling that’s a pleasure to operate.
Here are some of the topics we covered in this video discussion:
- Kapil has a very long career in open source. He talks about some of the open source projects that he created, including Cloud Custodian, which are being used by major companies like Capital One.
- Kapil founded a new company called Staclet which came out of the stealth mode last year. We learnt about what the company is all about and what problem it’s trying to solve.
- Open source solves day one problem where you can download and get it running. The real challenge is on day 2 with manageability, updates and scalability. That’s where commercial support for open source becomes important. We talked about what factors play a role in the survival and sustainability of open source.
- Cloud Native computing is a busy and crowded space, where a lot of overlapping is happening at the same time there are many gaps. Kapil talks about where Stacklet fits into the massive Cloud Native computing landscape.
- While open source has become a preferred model for software development, public cloud has created new challenges for traditional open source models and some companies are responding to this new challenge by creating their own ‘open source’ licenses that are not approved by OSI. We explored how Kapil sees these changes and if he is worried about the future of open source.