Key Factors to Consider During Containerization with Travis Jeppson

Key Factors to Consider During Containerization with Travis Jeppson

Some of the highlights of the show include

  • How containerization enabled Nav to spread roughly 250 virtual machines across multiple environments, while drastically reducing infrastructure spend
  • Travis’s thoughts on buying cloud native software tools versus building them, and what engineers should consider during this process
  • The difficulty of finding security solutions that work inside of a cloud-native ecosystem
  • Why companies should expect to encounter unique challenges when migrating to Kubernetes
  • Why companies need to understand their end goal, and determine an overall objective before beginning a migration
  • Travis’s must-have engineering tool, and why he can’t live without it


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’m here with Travis Jeppson. Travis is currently at Kasten, but he’s also going to talk about his time as a director of engineering at Nav.



Travis: At Nav, my role shifted quite a bit while I was there. I started as a software developer, writing Ruby back end applications for them, and then shifted into—actually within a month of being there, they shifted me over to the operational side because I had previous experience working with containerization, and also in infrastructure. So, they quickly moved me over into that realm and from there, I worked there for about a year until they told me, go spin up a team and get things moving. Help us move to containerization. Help us move to a more modern infrastructure and stuff. And so, about a year after that I became a director of engineering to where I had our ops team that had spun up, and then I also acquired both our QA team and our IT team that was there. And then, about a year after that, I ended up acquiring a little bit more than that. So, I ended up with a fair amount of our front end and some of our backend teams as well, and where they moved me into the senior director position. So, a day in the life, towards the end of when I was at Nav was a lot of working with the teams, helping them to do a lot of architectural perspective, and changes, and outlook to where we were trying to get as far as the company is concerned. We were building a product that we could address both first-party customers where they would log in to the Nav website directly, as well as working with partners so that we could issue out Nav functionality to those partners that they could incorporate to their pages as well. And so, we worked very hard to try to segment those two pieces together so that what we were building could be dispersed between both first-party customers and our third-party customers. And so, towards the end of my time there, it ended up being a lot of working within all of engineering to help facilitate those purposes. Then, just about six months ago, I ended up shifting my role over to a company called Kasten. And, Kasten is strictly working within the Kubernetes ecosystem. So, we do data management for Kubernetes based applications, and I am the site lead in Utah for Kasten, and so my day in and day out, a lot is, it's, kind of, all over the place. Sometimes it's working with engineering to help figure out some things going on there, sometimes it's working with brokers to help find office space for it. And sometimes it's dealing with insurance. It ended up being quite dynamic. But overall, I'd say most of my time is really spent more on the engineering side, just from the perspective of having worked at Nav and having been a consumer of a lot of these technologies, I think that they really appreciate my insights that I'm able to give there. So, I end up working, a lot, with the engineers to help facilitate what we're doing.



Emily: Sounds like you end up serving as a bridge from having been an end-user. But do you think that there is common miscommunications that happen, or what do those conversations sound like? Why is that experience valuable?



Travis: Yeah, so I don't know if it's as much as a miscommunication as much as what are customers looking for? And what are they trying to achieve? And why are they purchasing different software solutions? And what makes sense for them, more than anything. And I think that, having been a consumer of those products, I was more or less on the front lines there. When I was building our operational team at Nav, that was basically what I was doing is trying to figure out what things are we going to spend time on? And what things are we going to build ourselves, or what things do we need to just go find a solution for and bring them in-house? And the funny thing is when I was doing that for Nav is actually when I was introduced to Kasten and to the CEO here. And so, that ended up changing the way my career went. But overall, I think what Kasten—what those conversations really end up becoming is what are customers trying to do, and where are they trying to go?



Emily: Yeah, and in fact, that is exactly what I want to talk about more on this podcast. So, tell me a little bit about what your experience at Nav was. What were you looking for? What did you want to prioritize? What was the company hoping to get out of moving to containers?



Travis: So, I would say maybe the piece that really facilitated a lot of the progress in that sense was starting to understand our infrastructure spend. And then, to couple with that was also trying to become more agile. More agile in the sense of being able to push on demand, where previous to that we were pushing—you know, when we push our code, we did it on a bi-weekly basis—well, every other week, and it was always very cumbersome. If we have pictures of us in the early days of Nav, where there would be 10 engineers around someone’s desk, and they were the one person that was pushing the code into production, just waiting for the other shoe to fall, or waiting for something to happen. And so, when I started doing operational things for Nav, it started addressing those two things. What can we do to help control our infrastructure, and to understand it a little bit better? And how can we also create more of a dynamic infrastructure? Like, Nav is very much a US-based company. And so, the traffic that we're getting onto our website was regional very, very much. And so, there would be periods where it would be very busy, and then there'd be periods where it wasn’t. And the way that our infrastructure was designed, and a lot of times the way that they are designed, especially with virtual machines, is that you're building for capacity. You're building to be able to handle that load, and that has to stay there all the time, regardless of whether that capacity is being used or not. And so, that was one of the biggest questions, and that bill was—we were completely in the clouds. We were completely in AWS, but that bill continued to get more and more expensive every month. To the point of where it warranted the executive team to come down and say, “This needs to be fixed. This is going at an outrageous pace, and we need to be able to figure out how to control this.” And so, that's when they came to me and said, “Okay, get a team spun up, and let's figure out how to control this.” And so, I would say that those wer...

Jaksot(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 Maalis 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 Helmi 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 Helmi 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 Helmi 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 Tammi 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 Tammi 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 Tammi 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 Tammi 20min

Suosittua kategoriassa Liike-elämä ja talous

sijotuskasti
mimmit-sijoittaa
psykopodiaa-podcast
puheenaihe
rss-rahapodi
ostan-asuntoja-podcast
rss-lahtijat
pomojen-suusta
rss-rahamania
rss-startup-ministerio
rss-turvacast
taloudellinen-mielenrauha
rss-neuvottelija-sami-miettinen
rahapuhetta
rss-h-asselmoilanen
oppimisen-psykologia
kasvun-kipuja
sijoituspodi
hyva-paha-johtaminen
rss-40-ajatusta-aanesta