Using Serverless & ARM64 for Real-Time Observability
summary
Built a query engine (Retriever) that pulls recent NVMe segments and months of archive from S3, shards the work into tens of thousands of AWS Lambda workers, and merges results in a three‑tier map‑reduce so arbitrary queries return in seconds rather than minutes. Observed P99 local SSD queries drop ~2s to ~1s, scaled storage 20× without proportional cost increase, managed 100k+ concurrent vCPUs via negotiated limits, cut instance count ~20% and achieved ~30% better price‑performance after a Graviton/ARM migration while exploiting sub-second latency and the ability to buy compute in 1ms units.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:27Agenda
- 1:07What is lambda for?
- 1:37What is retriever for?
- 2:31What is Honeycomb for?
- 3:09Demo
- 4:08Interactive investigation of production behavior
- 4:44Emphasis: interactive
- 7:48Dynamic aggregation of any fields across any time range
- 10:31Buy compute in 1ms units
- 11:08Considerations
- 18:55It's not all about the money
- 19:59Software contributes significantly
- 21:02Wasting less power
- 37:23Yes*, do this at home
- 41:06Outro
related talks
49mUsing serverless functions for real-time observability
32mUsing Serverless Functions for Real-time Observability
39mServerless in production, an experience report
36mHow we used serverless to speed up our servers
47mAdvanced Serverless Architectural Patterns on AWS
54mServerless beyond Functions
01h 02mServerless in production, an experience report
47mServerless in production, an experience report
