Sponsored by LightStep
October 18, 2018
11 AM ET
Google deserves a lot of credit for imagining (and popularizing) what we now call "microservice architectures." With the benefit of hindsight, we now recognize that Google made mistakes during those early days of microservices. And unfortunately, the rest of the industry is repeating many of these mistakes today. What did Google get wrong about microservices, and how can we apply those lessons today?
Join us for our upcoming technical talk where Ben Sigelman – LightStep CEO, OpenTracing co-creator, and former Googler who built Dapper, Google’s distributed tracing infrastructure – will discuss:
- The problems Google wanted to solve with microservices
- What Google got wrong with microservices (and a few things they got right)
- Common microservice pitfalls today and how they compare with Google’s issues many years ago
- Practical steps engineering teams can take to avoid the preventable microservices failure modes
Ben Sigelman ,CEO and
Ben Sigelman (LinkedIn, Twitter): CEO and co-founder of LightStep, co-creator of Dapper (Google’s distributed tracing tool that helps developers make sense of their large-scale distributed systems), and co-creator of the open-source OpenTracing API standard (a project within the CNCF).