Temporal
title: Temporal radar_quadrant: Platforms radar_ring: Assess radar_position: inner created: 2026-05-22 last_updated: 2026-05-22 related: ["TwelveFactorApp", "AWSSaaSLens"]
Temporal is an open-source durable workflow execution engine that persists every step's execution state to a database, enabling workflow code to survive process crashes and resume exactly where it left off. It is the open-source successor to Cadence (Uber) and eliminates the manual combination of message queues, retry tables, and state machines that teams typically build for long-running processes.
- Workflow: Ordinary code (Python, Go, TypeScript, Java) that Temporal checkpoints automatically; can run for seconds or years
- Activity: An individual step (API call, database write) with configurable retry policies, timeouts, and heartbeating
- Signal: An external event that can alter a running workflow's course at any point in its execution
- Query: Inspect the current state of a running workflow without interrupting it
- Child workflows: Compose workflows hierarchically for complex multi-step processes
Temporal replaces the ad-hoc combination of SQS + Lambda + DynamoDB state tables (or equivalent) that teams assemble manually for multi-step processes with retry requirements. The workflow code is the state machine — no separate state table, no manual idempotency logic.
Self-hostable via Docker Compose with a Postgres or MySQL backend. Temporal Cloud is the managed option. SDKs available for Python, Go, TypeScript, Java, .NET, and PHP.
Temporal sits at Platforms → Assess inner. The durable workflow model solves a real and recurring problem — long-running, multi-step business processes (order fulfilment, user onboarding, payment flows, data pipeline orchestration) — with a significantly simpler operational model than hand-rolled alternatives. Self-hosting requires a Docker Compose deployment and a database; the learning curve is the new workflow-as-code mental model. Inner position reflects direct applicability to any project with multi-step processes and retry requirements, active open-source development, and multi-language SDK support. The remaining gate is a completed workflow handling a real multi-step process with at least one retry scenario validated end-to-end.
