Easy-to-understand monoliths are giving way to distributed systems: microservices, serverless, meshes, and proxies in every possible combination. These systems offer developers the freedom to build new features and technology faster, as they are no longer beholden to the elaborate release processes associated with monolithic architecture.
But, like all good things, there is a price: distributed systems are inherently difficult to operate and maintain. When something breaks—which it invariably will—how can you quickly comb through the myriad dependencies? How can you separate good hypotheses from bad ones?
Learn how observability helps developers understand multi-layered architectures: what’s slow, what’s broken, and what needs to be done to improve performance.
Yoann Lechevallier, Solution Engineer at Lightstep
Prior to Lightstep, Yoann worked as a Professional Service consultant at Splunk, IBM. While at ATOS, he was a benchmark engineer working on the development of a NUMA server. Yoann worked also for several startups such as BlueData and Seanodes as Solution Engineer and consultant.
Andy Steed, Content Director, Big Data LDN
Recorded: 23 May 2020