Wednesday, October 9, 2019

Building a Cloud Practice in Azure

SHOW: 418

DESCRIPTION: Brian talks with Joseph Landes, (@josephlandes, Chief Revenue Officer @GetNerdio) about the unique characteristics of the Azure Cloud, how MSPs are able to differentiate or partner in the market with public clouds, and how Nerdio helps bring together popular services in simple ways.  


SHOW SPONSOR LINKS:




CLOUD NEWS OF THE WEEK:


SHOW INTERVIEW LINKS:


SHOW NOTES:

Topic 1 - Welcome to the show. Before we talk about Nerdio, tell us about your background prior to joining the company, and about your focus today. 

Topic 2 - We spend quite a bit of time on this show talking about the technology offerings of Azure (and other clouds). Give us a sense of what the partner ecosystem of companies building enabling services on Azure looks like today. 

Topic 3 - Lets talk about how Nerdio interacts between Azure services and Managed Service Providers (MSPs). Help us understand the interaction between that ecosystem.  

Topic 4 - Traditionally, MSPs had the advantage of being regionally close to customers, and having some ability to differentiate based on vertical markets. How has their world evolved over time, what are their biggest struggles today, and how does Nerdio help them be more successful?

Topic 5 - We often look at Azure holistically, through the broad lens of 100s of services. Is it better to look at them in groups of services, targeting a specific market segment or market vertical? 

FEEDBACK?

Posted by
Labels: , , , , , ,

Wednesday, October 2, 2019

Developer Tools for Kubernetes

SHOW: 417

DESCRIPTION: Brian talks with Ellen Korbes (@ellenkorbes, Developer Relations at @garden_io) about the emerging sets of tools and frameworks to make it easier for application developers to interact with Kubernetes. 

SHOW SPONSOR LINKS:



CLOUD NEWS OF THE WEEK:


SHOW INTERVIEW LINKS:


SHOW NOTES:

Topic 1 - Welcome to the show. Tell a little bit about your background, and some of the things that you do in your day-to-day of Developer Relations with Garden.

Topic 2 - Kubernetes is a weird system because it involves containers and schedulers, neither of which developers really want to deal with. So why has Kubernetes become so popular, if it’s potentially not that friendly for developers?

Topic 3 - There has been a lot of activity in open source communities to create ways to make it easier for developers to work with Kubernetes. Some of those have been “PaaS” offerings (s2i, buildpacks, etc.), and some have been new tooling (e.g. Helm, Draft, Skaffold, Forge, Telepresence, Garden, and Tilt). Can you tell us about some of the new tooling - how do they map to developer needs? 

  • Debugging - Squash, KubeFwd, Stern
  • “Connect” - KubeFwd, Telepresence, Ksync
  • Development Orchestrators - Garden, Skaffold, Tilt

Topic 4 - In going through the different tools, what have you found are the ones that make the most immediate impact for developers? 

Topic 5  - As Kubernetes get more popular and widely used, do you think it’s important for developers to have to learn about Kubernetes? Or do you think that the external tooling will abstract it enough for them to be productive without that knowledge?

FEEDBACK?

Posted by
Labels: , , , , , , , ,

Wednesday, September 25, 2019

Dashboards, Metrics and Observability

SHOW: 416

DESCRIPTION: Brian talks with Björn Rabenstein (Engineer at @Grafana) about the intersection of Dashboards, Metrics, Monitoring and Observability.

SHOW SPONSOR LINKS:


CLOUD NEWS OF THE WEEK:

SHOW INTERVIEW LINKS:

SHOW NOTES:

Topic 1 - Welcome to the show. Tell about your background prior to joining Grafana Labs. (worked with Julius Volz at Soundcloud, guest on The Cloudcast on Eps.263 and Eps.319). 

Topic 2 - I saw a tweet the other day that said, “CIO directive to cut contracts because they have 37 monitoring tools and still the reliability is poor...". Your talk at VelocityConf is about the hype around observability and monitoring. What is the state of Ops visibility? 

Topic 3 - Let’s start by talking about good hygiene and good practices. What types of things should Ops teams, SREs and even Developers always been doing to have good visibility of their environments?

Topic 4 - What are the big mistakes that companies make, or what anti-patterns are becoming more pervasive? 

Topic 5 - As a builder of tools, and an operator of tools, what are some of the things you wish more Dev knew, but maybe don’t know what to ask?

FEEDBACK?

Posted by
Labels: , , , , , , , ,

Wednesday, September 18, 2019

Chaos Engineering and Team Health

SHOW: 415

DESCRIPTION: Brian talks with Paul Osman (@paulosman, SRE Engineering Manager @UnderArmour) about aligning business value to Chaos Engineering, measuring its impact, and changing team culture to embrace the chaos.

SHOW SPONSOR LINKS:


CLOUD NEWS OF THE WEEK:

SHOW INTERVIEW LINKS:

SHOW NOTES:

Topic 1 - Welcome to the show. Before we get into Chaos Engineering, let’s talk a little bit about your background and some of the things you did prior to joining Under Armour. 

Topic 2 - We’ve talked about Chaos Engineering a few times on the show before. At a company level, what are some of the things (Connected Health) where it makes sense for Under Armour to be investing in Chaos Engineering and developing expertise around this discipline?

Topic 3 - Walk us through how a team at Under Armour thinks about Chaos Engineering, from the business need to think about scheduling it (or not scheduling it), measuring it, and then communicating the results back within your team and to management.

Topic 4 - I think people think that Chaos is a periodic event, like a DR test, but in reality, it needs to be somewhat of an on-going activity. How do you connect the dots between this on-going Chaos and actual problems in your systems - and how/when to measure problems (or what to measure)?

Topic 5 - What is the most difficult part about getting the team culture to understand that Chaos is an important part of day-to-day activities and dealing with “failure” being part of the system?

FEEDBACK?

Posted by
Labels: , , , , ,

Wednesday, September 11, 2019

Knative Serverless

SHOW: 414

DESCRIPTION: Brian talks with Sebastien Goasguen (@sebgoa, CTO/Co-Founder at @TriggerMesh) about the evolution of the Knative project.

SHOW SPONSOR LINKS:


CLOUD NEWS OF THE WEEK:

SHOW INTERVIEW LINKS:

SHOW NOTES:

Topic 1 - Welcome back to the show. Almost a year ago, you launched TriggerMesh with Mark Hinkle. How is the business doing? 

Topic 2 - A couple of years ago, you helped create a technology called Kubeless, to do Serverless/FaaS on Kubernetes. And then Knative came along. For people that aren’t familiar with Knative, can you give us a Tl;DR on what it is and how it has evolved as a standard for Kubernetes?

Topic 3 - Let’s talk about the different elements of Knative and how each one of them is evolving - Build, Serving and Eventing. 

Topic 4 - Can we talk about the differences between “Serverless” and “Functions-as-a-Service”, especially in the context of different frameworks, and event sources?

Topic 5 - Triggermesh has been very early in delivering Serverless or Functions-as-a-Service via Knative. What are some of the lessons you’ve learned (use-cases, customer preferences, area of education) over the last year?

Topic 6 - Do you have any insight into some of the things that might be coming next in Knative? 

FEEDBACK?

Posted by
Labels: , , , , , , ,

Wednesday, September 4, 2019

Everything is a Little Bit Broken

SHOW: 413

DESCRIPTION: Brian talks with Heidi Waterhouse, (@wiredferret, Developer Advocate @LaunchDarkly) about the challenges of balancing stability and agility, from a technology perspective and a cultural perspective. 

SHOW SPONSOR LINKS:


CLOUD NEWS OF THE WEEK:

SHOW INTERVIEW LINKS:

SHOW NOTES:

Topic 1 - Welcome to the show. We’re going to talk about broken systems today, but before we get into that, let’s talk about your background, and what types of things you work on at LaunchDarkly.

Topic 2 - As we start seeing companies adopt a lot of these new technologies and methods (Agile, DevOps, Microservices, Distributed Systems, Cloud-Native Apps, Continuous Integration, etc.) we’re seeing them go through this interesting transformation of having to think differently about how things should work and how they might break. This is an area that you talk about quite a bit. 

Topic 3 - There is a 5 9s mentality and there is a release daily intro production mentality that sort of seem at odds with each other. How do we start figuring out how to manage that big space in between those two world views? Or can they be the same? 

Topic 4 - By adding in error budgets, layered access, and other accommodations for failure and for designing our systems for function over form or purity - we learn how to add resiliency to their system by learning to trust but mitigate their reliance on the perfect performance of their underlying tools.

Topic 5 - You get to talk to a lot of developers and architects. What are some of the best ways that you’ve seen them not only grasp these concepts but communicate them up to their management chains so they educate them about the terminology and concepts?


FEEDBACK?

Posted by
Labels: , , , , , ,

Wednesday, August 28, 2019

2019 Mid-Year Update

SHOW: 412

DESCRIPTION: Brian talks with Brandon Whichard (@bwhichard, Co-Host of Software Defined Talk podcast) about the tech/cloud trends that have shaped the first half of 2019.

SHOW SPONSOR LINKS:

CLOUD NEWS OF THE WEEK:

SHOW INTERVIEW LINKS:

SHOW NOTES:

Topic 1 - Welcome to the show. I’ve been listening to your show, Software Defined Talk, for quite a while. Tell us about your show, your co-hosts and the types of things you discuss on the show?

Topic 2 - What are some of the biggest trends you’ve seen (or been discussing) so far in 2019? Anything really surprise you?

Topic 3 - AWS has continued to be the leading public cloud for a decade now. Do you see anything slowing AWS down?

Topic 4 - There were lots of articles earlier in the year about big public cloud contracts between web companies and the public cloud (hundreds of millions in cloud spending). Many of those companies are now struggling as they have gone IPO. If they struggle to make revenue (and subsequently their cloud payments), do you see this having any effect on sentiment about public cloud? 

Topic 5 - There is starting to be some noise in the news and the markets about a potential economic slowdown. How much do you think about what that might mean to the tech industry, and subsequently buyers and users of tech? Sometimes in slower times, we see the creativity of new tech emerge (2001 - mass websites; 2007/8 - AWS and iPhone, 2019/2020 - ??)

FEEDBACK?

Posted by
Labels: , , , , , , ,
Subscribe to: Posts (Atom)