This week, we talk with Charity Majors, chief technology officer of Honeycomb.io and a pioneer in observability about the three-year anniversary of that movement which has significantly changed how applications are monitored and maintained in the cloud native era. Majors contributed a post that appeared on The New Stack this week in which she takes a closer look at why the observability movement formed and why other approaches and methods fall short. She explained why engineering teams must continue to focus on this approach in order to better understand, debug, and maintain large-scale distributed systems. "When we blew up the monolith into many services, we lost the ability to step through our code with a debugger: it now hops the network. Our tools are still coming to grips with this seismic shift," Majors writes.
This week, we talk with Charity Majors, chief technology officer of Honeycomb.io and a pioneer in observability about the three-year anniversary of that movement which has significantly changed how applications are monitored and maintained in the cloud native era.
Majors contributed a post that appeared on The New Stack this week in which she takes a closer look at why the observability movement formed and why other approaches and methods fall short. She explained why engineering teams must continue to focus on this approach in order to better understand, debug, and maintain large-scale distributed systems.
"When we blew up the monolith into many services, we lost the ability to step through our code with a debugger: it now hops the network. Our tools are still coming to grips with this seismic shift," Majors writes.