I wanted to share on this post the content from my Google partner booth lightning talk where I talked about checking the pulse of your cloud native architecture. While that sounds like a dry architecture type of talk, I promise you, I took it in a unique direction with the focus not on the technology as much as on the side-effects it has on your teams.
Getting the control and overview back into the hands of your developers and engineers with regard to the massive challenges around cloud native observability data is the number one challenge we are all facing. I hope my insights provided a few hand holds for you to start gaining ground on your own organization's challenges.
See below for the slides from my talk.
These are the slides I used on Wednesday evening, at the Google booth #E2 for my lightning talk that was at 18:30 - 18:45.
For completeness, below the abstract for this talk.
Checking the pulse of your cloud native architecture
The daily choices you make as an engineer when shipping code contributes to the feedback loop. In cloud native environments a surprising amount of data is generated from the application layer down to infrastructure and along the delivery path. Regulatory and compliance pressures force us to store audit and observability data. Understanding the pressures on our engineering teams around the collection, storage, and maintenance of your cloud data can mean the difference between successful teams and burnout. Let us take you on a journey, looking closely at the current state of observability based on a recent research conducted with 500 cloud native engineers and find out what it’s like to be in the trenches.
Thanks to all who stopped by the Google partner booth to share their stories with me and listen to my insights, was great fun!