Vodafone’s Cloud Native Journey with Tom Kivlin

Vodafone’s Cloud Native Journey with Tom Kivlin

Some of the highlights include:


  • Why Vodafone moved to a cloud native architecture. As Tom explains, the company was struggling to manage operations across more than 20 markets. They also needed to improve the customer experience, and foster customer loyalty.
  • Why their business and engineering teams were both in favor of cloud native.
  • The benefits of deploying daily operational activities around a single cloud native platform.
  • An overview of where Vodavone currently is in their overall cloud native journey. Tom also explains how cloud native conversations have changed inside of the company throughout their journey, as various business units have caught on to the benefits of the cloud.
  • Vodafaone’s transition from outsourcing roughly 97 percent of their operations, to bringing 95 percent in house. Tom explains how this has improved efficiency and expedited time to market.
  • The challenge that Vodafone faced in trying to apply legacy network security solutions to distributed and dynamic systems.
  • Tom’s thoughts on why Vodafone’s cloud native transition and modernization efforts have been crucial to their success over the last five years.

Links:


Transcript


Announcer: Welcome to The Business of Cloud Native podcast, where we explore how end users talk and think about the transition to Kubernetes and cloud-native architectures.



Emily: Welcome to The Business of Cloud Native. I'm Emily Omier, your host, and today I am chatting with Tom Kivlin. Tom, thank you so much for joining us.



Tom: You're welcome. No problem.



Emily: Let's just start out with having you introduce yourself. What do you do? Where do you work, and what do you actually do during your workday?



Tom: Sure. So, I'm a principal cloud orchestration architect at Vodafone Group. I work in the UK. And my day job consists of providing guidance and strategy and architectural blueprints for cloud-native platforms within Vodafone. So, that's around providing guidance to the software domains that are looking to adopt cloud-native architectures and methodologies and also to the more traditional infrastructure domains to try and help them provide their services in a more cloud-native manner to those modern teams.



Emily: And what does that mean when you go into the office—or your home office, go into your dining room where your laptop is, I don't know—what do you actually do? What does an average day look like?



Tom: It can vary. So, depending on the activity at the time, it could be anything from preparing a global policy that needs to go through the senior technology leadership team, to preparing some extremely detailed requirements for selection process or creating some infrastructures code, or the code artifacts for the deployment of cloud-native services, whether that's in our lab, or to help our services teams within Vodafone.



Emily: Tell me a little bit more about what pain made Vodafone think about moving to cloud-native and Kubernetes.



Tom: Primarily, it was the challenge of having 25 different markets, or 23 now. We launched a digital strategy to—so back in 2015, we launched a five-year strategy, which we wanted to massively increase the rollout of 4G, of converged network offerings, of improved customer experience. And we found that the traditional way of managing software was not supportive enough in our ambition. And so, having to choose cloud-native technologies, things like Kubernetes, but also the modern operating models, that was the driver: it was to improve our customer experience, and our customer-affecting KPIs, really.



Emily: And when you say it wasn't supportive enough, what do you mean specifically?



Tom: So, things like time to market, for example. So, if we wanted to offer a new service—so one of the things that 4G started the drive towards was a more granulated service offering to consumers, and so lots of different things could be offered. And if it took you six months to think of an idea and then have to go through—or even longer than six months to get to the point where that could be offered to customers, even if it was just a very minor feature within an existing product, then that's not going to engender customer loyalty. And so, things like the cloud-native mindset, where there's a much closer link between the engineering teams and the customer, there are much shorter periods of time between ideas coming in from the customers and then being delivered back to the customers as product features, that sort of time to market was really enabled by cloud-native technologies and mindsets.



Emily: And how does having two dozen, more or less, different markets, how does that play into the decision A) to move to cloud-native in general, and managing the IT infrastructure?



Tom: So, one of the things that's really driven it is trying to simplify and reuse artifacts. So, if you've got 23 markets all doing a different thing, then there's obviously a lot of duplication happening across the group, whereas if everyone's using the same technology in the same platforms—take Kubernetes as the example—everyone can write their software for that platform. Everyone can write their operational ecosystem around that platform. So, the deployment artifacts, the pipelines, the day two operational activities, they can all be based around that single cloud-native platform. And so, that enables a huge amount of efficiency from the operational side. And that in turn allows those engineering teams to focus on things that are adding value to the business and the customer instead of having to focus on fairly low-level tasks that are just keeping the lights on, if you like.



Emily: What's different for each one of those markets?



Tom: So, it might be something like language, it might be something as simple as that. It may be that the offerings are slightly tweaked. So, rather than, I don't know, as an example, rather than Spotify being included as a kind of add on, it might be some other service that's more relevant to that market. It may be that there are particular regulatory requirements that are specific to a market that needs to be considered within the product design and the engineering of it. And so, having a cloud-native response allows sharing and reuse of artifacts where we can, but still allows for that customization where it's required.



Emily: Where would you say Vodafone is in the cloud-native journey? Do you feel like you've, mission accomplished?

<...

Episoder(267)

How Technology Decisions Impact Growth with Misha Bragin

How Technology Decisions Impact Growth with Misha Bragin

This week on The Business of Open Source, I spoke with Misha Bragin, co-founder and CEO of NetBird. This was also the first episode I recorded in 2025, which gives you an idea of how far in advance I’m recording episodes. NetBird has an interesting origin story — it came out of an original idea to make a hardware product, but as Misha and his co-founder were starting to work out the realities of manufacturing, they realized that they would be better off building a software company. Here were some of the take aways from the conversation: Sometimes your users want to pay you! Misha explained that before there was a commercial offering, some open source users proactively reached out asking for one — because they understood that in order for the company to be viable, it needed to have revenue. Just because you get crickets at first doesn’t mean your project sucks. When NetBird’s open source project was first released, it made zero splash.The reality of working in a proprietary piece of software, you can do things quick and dirty. *Obviously you shouldn’t, but let’s face it a lot of people do. But when your code is open, it is also a part of your communication strategy! If you push out code that’s not tested or that’s not well done, you risk reputation damage even if the software works exactly as it should. Misha talked about how choosing Auth0 as an authentication service was a mistake — not because it is a bad service, but because it was not appropriate for their target audience, who are self-hosting. This is a very good reminder of how sometimes choosing the best technology for the job can backfire; you also have to take into account who the target user is and if they are going to be repelled by the choice you’re making. Struggling to figure out how to balance your project development with your product development? Need to supercharge your funnel? You might want to work with me. Want to share your knowledge and learn from your peers who are open source entrepreneurs? You should join us at Open Source Founders Summit May 19th and 20th in Paris.

5 Mar 35min

Open Source and AI Coding Assistants with Ty Dunn

Open Source and AI Coding Assistants with Ty Dunn

This week on The Business of Open Source, I spoke with Ty Dunn, founder of Continue.dev, which is an open source AI code assistant. We had a fabulous conversation that touched on both the AI hype wave and why open source. The first thing I’d like to touch on is why Continue.dev is open source, in other words, what business rationale Ty has for taking that route. Because he makes some great points about building an ecosystem. If building an ecosystem, and encouraging people in your community to build on top of your software, is something that is important to your for either strategic or philosophical reasons, the absolute best way to accomplish this goal is with an open source project. In the case of Continue, being open source, and allowing companies to retain control over their data, is also a differentiation in the market. There was also a phrase in the conversation that I wanted to pull out — Ty talked about monetizing “next to” the open source project. This is precisely how many of the most successful open source companies work. They have a successful open source project but monetize it in a way that is adjacent, rather than directly competing with the project. Check out the full episode for a discussion about the AI hype wave and how it intersects with open source business models. If you want more discussions about open source companies, you shouldn’t miss Open Source Founders Summit this May 19th and 20th — it’s the only event specifically designed for leadership in open source companies. And if you’re struggling with your open source strategy, you should consider working with me.

26 Feb 40min

The CFO's View of Open Source Companies with Eileen Doody and Karen Walker

The CFO's View of Open Source Companies with Eileen Doody and Karen Walker

This week on The Business of Open Source I had a slightly different conversation: I spoke with the CFOs of two open source companies, Sysdig and Percona, to better understand what is different (and what is not) about financial management in open source companies. Karen Walker is the CFO at Sysdig, and Eileen Doody is the CFO at Percona. They both joined me to talk about the CFO role in general and the CFO role in particular at an open source company. Why did I do this episode? Many founders I’ve spoken with are a bit unclear on the role of a CFO — whereas I’ve never spoken with a founder who had trouble understanding what their CTO does. Here’s some takeaways from our conversation: Part of the CFO’s role is about thinking about open source strategically, in terms of how the open source project is going to fit into the company’s overall strategy.Because open source is so ingrained in the company, it doesn’t fit into a single budget line item; it’s impossible to break out and say ‘we spend $X on open source’ because it’s so integrated into everything the company doesHow do you measure your ROI on investment in open source? At Sysdig, two out of three prospects come to the company because of Falco, their open source project. We also talked about the ecosystem effects of having a huge footprint with your open source project; it’s hard to measure the positive influence of having massive brand awareness, but both CFOs are convinced that it is very important to the company. Eileen says that many CIOs now have mandates to look for open source solutions when possible, which was not the case a decade ago. That’s changed the dynamic for a company like Percona that’s based around open source. Another reason I did this episode is because while I usually have founders on the podcast, there are some really important perspectives from other leadership team members. Part of the the role of a CEO is to understand all the other C-level leadership position’s roles and responsibilities, and in my experience the CFO is one of the less well understood roles. In fact, we wrapped up the conversation by talking about how a CFO can be a real strategic partner that’s forward-thinking rather than just the bean-counter that some people expect a CFO to be. A couple things to mention. First of all, if you want to learn more about my consulting work with open source companies, you can do so here. Second, if you want to chance to connect with other founders of open source companies, consider joining Open Source Founders Summit this May 19th and 20th in Paris.

19 Feb 37min

Thinking Hard about your License Choice with Ivan Burazin

Thinking Hard about your License Choice with Ivan Burazin

This week on The Business of Open Source, I spoke with Ivan Burazin, the CEO and co-founder of Daytona. First of all, Daytona was one of the sponsors of the first edition of Open Source Founders Summit, and I had a chance to meet Ivan in person at the event. So a big thank you to him for taking a risk on the first year of the event! But let’s get down to business. We talked about: Why Daytona took an open source approach, even though they originally started out with a pure commercial licensed software. The thought that went into choosing the license — this was a great discussion, because it is a question a lot of people have. Ivan walked through his thought process in choosing a license and how he thinks about difference licenses. The theory about how open source will help Daytona build their business, and the dynamics of how open source adoption leads to commercial success. The importance of technical decisions in an open source project’s growth strategy.The different stakeholders in the community, as well as in the customer community. I really liked the piece when Ivan talked about the individual motivations that people might have for getting involved in a community — instead of thinking about how you get something from the community, think about how others can get something out of the community. For example, you can have someone who wants to get into technical writing who gets that experience by writing documentation for your project. Making it easier for that to happen is in everyone’s best interest. Like this episode? Struggling with your messaging or with your conversions from open source project to commercial customers? You might want to work with me. And if you want to join us at Open Source Founders Summit, apply to join us here.

6 Feb 39min

Bootstrapping an Open Source Company with Ludovic Dubost

Bootstrapping an Open Source Company with Ludovic Dubost

This week on The Business of Open Source, I talked with Ludovic Dubost, founder and CEO of XWiki about the long history of XWiki, which he started in 2003. This was a wide-ranging conversation… here’s some of the things we covered: Why XWiki is an open source company. Ludovic started out with the explicit goal of creating a company, so why start it as an open source company? The reality that starting a software company in Europe means putting yourself at a disadvantage — which doesn’t mean that you shouldn’t do it, but rather that you need to be aware of that fact, and that open source is one tool that European companies can use to  succeed even when they are at a disadvantage. How Ludovic bootstrapped the company, including moving from support contracts to recurring revenue from the SaaS and how the transition has happened over the yearsThe difficulties that come from being small and bootstrappedManaging the balance between distribution and monetizationWhy a community version / enterprise version model did not work for XWikiWhy it’s so important to pay attention to your competitive landscape, because the only way to get customers is by offering something that is better in some way than your competitors — it’s your comparative strengths that matter. Did you enjoy this conversation? Find Ludovic and XWiki at Fosdem on Saturday! And/or join us at Open Source Founders Summit. Are you also interested in the challenges around product management for open source companies? You might want to work with me.

29 Jan 46min

Building an Open Source Company for Long-Term Sustainability with John O'Nolan

Building an Open Source Company for Long-Term Sustainability with John O'Nolan

This week on The Business of Open Source, I spoke with John O’Nolan, the co-founder of ghost.org. Before further ado, John is going to be one of speakers at Open Source Founders Summit 2025, so if you’d like a chance to dive deeper into any of the subjects we talked about on the podcast with him, in person, you should join us in May. There’s a lot of interesting tidbits to pull out from this conversation. First of all, I think it’s interesting that Ghost came about because Wordpress was moving away from its roots as a pure publishing tool and becoming a website builder. John, who was very involved in the Wordpress community at the time, wondered what it would look like if Wordpress went back to its roots and focused on publishing and only publishing. It’s a lesson for founders that sometimes focusing on the small niches left behind as incumbents expand can be huge opportunity. —> It’s worth noting that we recorded this podcast last fall when the drama between Wordpress and WPEngine was exceptionally hot. Ghost is organized as a non-profit, and John also talked about why he made that decision from the beginning. It came down to wanting to make a good salary at a company he had started, but without the goal of becoming fabulously wealthy as a result. We also talked about whether or not a venture-backed company can be ‘responsible’ with respect to their community; and what types of companies tend to be able to manage the tensions between the community needs and the fiduciary duty that you have if you take outside funding. We also talked about the difference in the market between the product and the project, how Ghost manages to expand in spite of not having a dedicated marketing team. We also talked about the difference between building a sustainable business and building a business that gets hockey stick very quickly as well as some of the tension between technology decisions and business decisions. If you want to talk more about these issues — and want to talk directly with John — you should come to Open Source Founders Summit May 19th and 20th, 2025. Get your tickets here.

22 Jan 43min

The Complicated Calculus around Donating a Project to a Foundation with Omri Gazette

The Complicated Calculus around Donating a Project to a Foundation with Omri Gazette

In the last episode of The Business of Open Source recorded at KubeCon Salt Lake City, I spoke with Omri Gazitt, co-founder and CEO of Aserto. Aserto has two open source project that it maintains, one of which it donated to the CNCF. In this episode, we talked about the decision to donate a project to the CNCF — both what the process entailed and what is in for Aserto in having a project at the CNCF. But of course Aserto also has another project, Topaz, which it has not donated to the CNCF. We also talked about why Topaz wasn’t donated to the CNCF. A couple things to pull out of this conversation: The complicated calculus of deciding whether to donate a project to a foundation, and how the dynamics of the market change over the years and you have to think very critically about the specifics of your situation before making the decision to donate to a foundationHow every company has slightly different market pressures — sometimes the market pushed you to donate to a foundation, sometimes the market doesn’t care. The importance of thinking not just about market share when you’re open source, but also how you are going to monetize! It’s possible to have vastly smaller market share but make vastly more money. Why being an open source company does not have to mean that your paid solution has to be cheaper than your competitors. Why you don’t have to start selling into startups — sometimes your best customers will always be either mid-market or enterprise from the very beginning. We talked about the panel I moderated at CloudNative StartupFest at KubeCon. If you missed it, here’s the link to see the replay. We also talked about Adam Jacob’s talk at the same event, which you can see here. If you’re building a company around an open source project and aren’t sure how to manage the relationship between the project and product, you might want to work with me or come to Open Source Founders Summit this May.

15 Jan 24min

A Massive Head Start on Product Development with Open Source with Martin Mao

A Massive Head Start on Product Development with Open Source with Martin Mao

This special episode recorded live at KubeCon Salt Lake City last November is with Martin Mao, CEO and co-founder at Chronosphere.We talked about how M3 was foundational to the early history of Chronosphere, and how the ability to leverage M3, which Martin and his co-founder had written while they were still working at Uber. One of the most important aspects of this story is that since M3 is the foundation Chronosphere is built on, the fact that it was developed over four years at Uber while they were still on Uber’s payroll meant that when they decided to build a company it allowed them to get to market dramatically faster than would have been possible otherwise. Chronosphere’s core platform is a proprietary SaaS product, but still has a significant relationship with two other projects: Perses, which was developed at Chronosphere and donated to the CNCF in 2024; and FluentBit, a CNCF graduated project that was originally developed by Calyptia and became part of Chronosphere when it acquired Calyptia. We talked about: The pros and cons of donating projects to the CNCF, from both the perspectives of the company creating the project and the interests of the community and project itselfWhy Chronosphere’s core platform isn’t open source itselfHow a company can end up getting financial advantages from being the stewards of large open source community, even if the connection doesn’t always seem obviousHow product roadmaps are managed for the two projects versus how it’s managed for Chronosphere’s proprietary products. If you’re building a company around an open source project and aren’t sure how to manage the relationship between the project and product, you might want to work with me or come to Open Source Founders Summit this May.

10 Jan 20min

Populært innen Business og økonomi

stopp-verden
dine-penger-pengeradet
e24-podden
rss-penger-polser-og-politikk
rss-borsmorgen-okonominyhetene
finansredaksjonen
pengepodden-2
tid-er-penger-en-podcast-med-peter-warren
utbytte
livet-pa-veien-med-jan-erik-larssen
pengesnakk
morgenkaffen-med-finansavisen
rss-sunn-okonomi
okonomiamatorene
aksjepodden
rss-rettssikkerhet-bak-fasaden-pa-rettsstaten-norge
lederpodden
rss-fa-makro
rss-andelige-tanker-med-camillo
rss-markedspuls-2