Home / Companies / Temporal / Blog / Post Details
Content Deep Dive

How groundcover built a durable alert dispatch system with Temporal

Blog post from Temporal

Post Details
Company
Date Published
Author
Omar Karjevsky, Yosi Zelensky
Word Count
2,458
Company Posts That Month
20
Language
English
Hacker News Points
-
Post removed?
No
Summary

Groundcover, a company providing a comprehensive observability stack for metrics, logs, and more within Kubernetes clusters, transitioned its alert dispatch system to Temporal to improve scalability and reliability. The previous Python/FastAPI platform presented operational, durability, and observability challenges, especially as groundcover expanded. Temporal offered a more cohesive integration with their Go-based backend, providing advantages such as durable execution and efficient workflow management. By implementing a two-level workflow architecture, groundcover effectively managed alerts, maintaining proper order and handling high-throughput demands without reordering events. This setup allowed for streamlined notification processes using Temporal's capabilities, enhancing the system's resilience and scalability. The transition facilitated better debugging and testing processes, leveraging groundcover's observability tools and Temporal's features to ensure robust alert management. The adoption of Temporal marked an important shift in groundcover's infrastructure, paving the way for future use cases and optimizations as the team becomes more familiar with Temporal’s offerings.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Kubernetes 4 1,965 371 106 -15%
Observability 4 3,421 707 180 -24%
OpenTelemetry 1 945 122 49 -21%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.