All 18 Dependencies

Every package temporal depends on, ranked by repo health score.

Temporal is an open-source durable execution platform that ensures workflows keep running through crashes, network outages, and infrastructure failures without losing state. Originating as a fork of Uber's Cadence project, it is now developed by Temporal Technologies and powers some of the most demanding distributed systems at companies like Stripe, Coinbase, and Netflix.

At its core, Temporal implements event-sourced workflow orchestration: every workflow execution maintains an append-only event history that can be replayed at any time to reconstruct exact state. This means workers can crash and restart without any data loss, and developers write ordinary sequential code rather than managing complex state machines or retry loops.

The platform is structured as a cluster of internal services—Frontend, History, Matching, and Internal Workers—each handling a distinct concern. The History Service owns per-workflow state and shards it across the cluster for horizontal scalability. The Matching Service manages task queues that SDK workers poll for work. Client SDKs in Go, Java, Python, TypeScript, PHP, Ruby, and .NET communicate with the cluster over gRPC.

Self-hosting Temporal requires running the server alongside a persistence backend (PostgreSQL, MySQL, Cassandra, or SQLite for development) and optionally Elasticsearch for advanced workflow visibility. Temporal Cloud is the fully managed alternative, eliminating operational overhead while offering the same programming model.

Join founders buildingwith open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on Substack
Join 750+ subscribers

Search