Durable, But At What Cost?
summary
Lovable starts using Temporal six months ago and finds opaque billing: only ~60% of cost shows in basic metrics, while activity heartbeats consume ~30% of the bill from one long-running activity. About 200–300 workflows produce skewed usage where the top 10 account for ~93% of cost. Using Go SDK metrics + OpenTelemetry, Prometheus, and workflow coalescing reduces bills ~20–30%, and targeted tweaks (heartbeat timeouts, local activities) cut another ~25%.
AI-written summary · about
related talks
31mMy Logs Cost More Than My Services
10mLightning Talk: Show Me the Money: Metrics Edition
14mMetrics Without Limits
32mTaming the Cost of Telemetry: How Riot Games Reined In...
16mShrinking the Observability Bill
56mUnwiring High Cardinality
33mMonitoring Systems as a Service – Walking the Line between...
40mOptimizing AI/ML Workloads