Event Logging
summary
Truecaller rebuilds event logging around two concrete choices: a single, immutable schema repo using Apache Avro to generate cross-language libraries so events don’t desync, and modeling inbound telemetry as reactive streams with Akka Streams so backpressure and buffering propagate failures upstream. The stack serves ~200 million users, blocks about 400 million spam calls per month, and fewer than 90 engineers, and these changes have prevented production data loss multiple times while eliminating version-mismatch bugs.
AI-written summary · about
chapters (4)
related talks
38mPostmortem: Evolution of an Event recording solution
01h 03mSurviving Long Event History
41mAkka in Production: Our Story
55mThe Incredible Efficiency of Log Unification!
38mHow to handle 100k events per second
44mThe Art and Benefits of Computing Eventfully
30mUnhappy Path & Dealing with Bad Events
55mExperience report on using Akka in production: pitfalls and rewards
