Imagine a website that allows you to buy tickets for concerts. The typical flow of the application begins with you selecting and reserving the tickets, paying and finally receiving an email with the purchase confirmation. Now imagine this application running at scale for hundred thousands of users at the same time. How do you know when something goes wrong? How do you trace a single failing transaction? It’s like finding a needle in a haystack! If you are building an event-driven application you might end up having Kafka messages floating all over the place. How do you make sense of it?
Run Time: Approx. 60 minutes
Mauricio “Salaboy” Salatino is an open source software engineer at @Diagrid, contributing to and driving initiatives for the Dapr OSS project. He also is a Steering Committee member for the Knative Project and co-leads the Knative Functions initiative.