Building Sub-Millisecond Ingestion Middleware for ServiceTitan and Jobber: Part Four - Bare-Metal V8 Edge Runtimes and In-RAM Idempotency
When you scale multi-branch home-service fleets past millions of dollars in monthly ad spend, the bottleneck isn't your ad spend or your dispatchers—it's the stateful weight of your infrastructure. Traditional backend runtimes rely on heavy container clusters, database connection pools, and ORM mapping layers just to process a standard Meta or Google Local Services Ad webhook. Under…
The article discusses the challenges faced by ServiceTitan and Jobber when scaling multi-branch home-service fleets, particularly in handling high-concurrency webhook traffic. Traditional backend runtimes rely on heavy container clusters, database connection pools, and ORM mapping layers, which can add significant latency and cause database locks during peak traffic.
To address this, the team moved to a stateless, bare-metal V8 edge architecture, which enables sub-millisecond execution times (~0.42ms) and eliminates dropped packets. This redesign involved eliminating disk I/O and ORM latency through the use of V8 isolates and implementing atomic dual-hash deduplication in volatile memory. The solution also includes strict E.164 telephony sanitization and compliance gating to ensure clean data processing.
Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.
