This talk covers hard lessons learned by a small team at Redhat over the past few years as they struggled to refactor a monolithic service to a more scalable and resilient architecture. In this talk, I'll cover the lessons we've learned about observability, production support effectiveness, and the cost of bad or inadequate solutions. We made more than a few mistakes like repeatedly under-appreciating the value of operational features and support infrastructure, and falling prey to the rush of shipping features while neglecting our service's operational health.
These lessons have matured my team's approach to observing our code in action, shown us how to let data guide priorities, and taught us that context is everything when trying to find answers to new problems. The insights we’ve gained into our system complexity, illuminated by our view into our running code, have changed how we think about the ways service architecture influences team health and agility. By attending this talk, you'll cringe at our mistakes, nod knowingly at our wrong turns, and chuckle fondly over my naivete regarding the future.
Please register for o11ycon+hnycon first, then register for this workshop. Conference registration is required.
Michael is a Platform Engineer at Honeycomb.io. Has worked with various public and private cloud providers over for the past 8 years. Originally was deeply rooted in system administration but has since gained fondness for infrastructure as code and developer tooling. He has been using Kubernetes + Terraform software pairing since 2017. In his spare time he is an avid PC gamer, enjoys cooking and tinkers with mixed reality.