PODCAST
In this episode of the Ambassador Livin’ on the Edge podcast, Charity Majors, CTO at Honeycomb and author of many great blog posts on observability and leadership, discusses the new approach needed when instrumenting microservices and distributed systems, the benefits of “observability-driven development (ODD)”, and how Honeycomb can help engineers with asking ad hoc questions about their production systems.
Be sure to check out the additional episodes of the “Livin' on the Edge” podcast.
Key takeaways from the podcast included
PODCAST
The conversation yielded several related themes that underpin success for cloud-native adoption in the real world:
Centralizing real-world, cloud-native development to meet business goals should be the key driver of any digital transformation.
In a previous role, Katie worked with the Condé Nast organization to build a centralized, cloud-native solution that unified upwards of 32 different media platforms into a single hosting platform, single CMS, and single visual identity in order to create and deliver content consistently on a global level. "With business critical applications, 'centralizing the decentralized' ensured stability and ownership when we needed to take other nuances into consideration, for example, operating in China and other complex business problems."
PODCAST
In a cloud native world, software developers are no longer only responsible for writing code. Today’s developers must write and package code, deploy these services into production, and make sure that the corresponding applications continue to run correctly when released into production.
As part of an ongoing interview series about cloud-native development and easing the developer journey, we've spoken to a number of people about cloud-native challenges. These include different perspectives, including the SRE and platform architect.
In this interview, Ambassador Labs' own Daniel Bryant, Director of DevRel, spoke with our own Bjorn Freeman-Benson, SVP of Engineering, to get both the engineering leadership and architect's point of view. They explored the challenges inherent in the question: "How do you make sure your development teams have the tools they need to manage all of these tasks?". Ultimately the conclusion drawn is that a developer control plane enables developers to control and configure the entire cloud development loop in order to ship software faster.
PODCAST
Several themes and insights emerged from the conversation:
Platforms are evolving: While Kubernetes has emerged as a kind of standard, providing more granular control and enhancing the ability to curate different platform experiences for different types of teams, it isn't entirely accurate to say that the platform question is settled. Kubernetes may be the platform around which focus has converged because of its fluidity and flexibility, letting you do just about anything. But more broadly, platforms continue to evolve, in large part because there are so many different ways to accomplish the many tasks that make up cloud-native development. On one hand, more mature companies may be happy with the Kubernetes setup. Many others, though, want a more curated, structured and opinionated path, with tools sitting on top of Kubernetes.
PODCAST
Be sure to check out the additional episodes of the "Livin' on the Edge" podcast.
Key takeaways from the podcast included:
Creating a fast development loop is essential for engineering productivity. Sometimes engineers have to “bend the rules” in order to make this work for them.
PODCAST
Be sure to check out the additional episodes of the "Livin' on the Edge" podcast.
Key takeaways from the podcast included:
Creating an effective continuous delivery pipeline is essential for enabling fast feedback for developers.
