No more monoliths! Let’s use microservices and asynchronous invocations everywhere! But how to track logs when multiple calls are in place, clocks are skewed, network is faulty and something goes wrong? How to figure out what happened first? And how to debug this single request which caused so many troubles?
In this talk I explain problems with synchronizing clocks and why relying on timestamps doesn’t work in the world of microservices. We will see happened-before relation, vector clocks, correlation ids and other patterns used to introduce some meaningful order. We will understand why common understanding of “time” is misleading in distributed systems and what to use to mitigate that.
Examples will be in .NET. Level 200, moderately intense session.
Learning Objectives:
- Learning problems with wall lock in computer science
- Understanding Lamport timestamps and vector clocks
- Examining real life implementation an application in microservices
Materials
Recordings