How we almost delivered 100 tons of Stracciatella Mousse
summary
An online shop order flow suddenly generates 100 tons of Stracciatella Mousse — roughly 1000 packages for one customer — exposing gaps across more than a hundred interacting services. Teams reconstruct the chain using logging messages, unique order IDs, timestamps, the data warehouse and real-time dashboards, build anomaly detectors and alert rules, and tighten who can replay or mutate orders. The monitoring changes catch the surge before mass shipment and remove noisy debug logs that hid the root cause.
AI-written summary · about
chapters (10)
- 0:00Stracciatella Mousse disaster intro
- 8:30Customer solutions and dependencies
- 11:07Service interactions complexity
- 16:52Dashboard setup challenges
- 22:41Database security issues
- 27:09November trend analysis
- 32:57Performance dashboard entry
- 36:30Data access safety
- 41:08Developer definitions
- 45:03Data ethics and sensitivity
related talks
34mMetrics driven development
14mHere, There and Everywhere: Spotting Data Opportunities 101
24mArchitecting a Seamless E-commerce Platform Transition
07mAccelerating Composable Commerce with Strapi
21mData-driven approaches in a technology startup
23m30 Minutes To Zero: Slashing Debug Time With WhatIsWrongWithThis?
52mScaling Data Teams: Three Pitfalls and How To Avoid Them
20mSystems @Scale Summer Live Q&A Session #2