| date | author | paging | theme |
|---|---|---|---|
2026-02-27 |
Peter Hellberg 🌿 |
[page %d / %d] |
../../../.slides/theme.json |
________________________________________________
▛▀▖ ▌ ▜ ▛▀▘ ▐ ▗
▌ ▌▌ ▌▙▀▖▝▀▖▛▀▖▐ ▞▀▖ ▙▄ ▚▗▘▞▀▖▞▀▖▌ ▌▜▀ ▄ ▞▀▖▛▀▖
▌ ▌▌ ▌▌ ▞▀▌▌ ▌▐ ▛▀ ▌ ▗▚ ▛▀ ▌ ▖▌ ▌▐ ▖▐ ▌ ▌▌ ▌
▀▀ ▝▀▘▘ ▝▀▘▀▀ ▘▝▀▘ ▀▀▘▘ ▘▝▀▘▝▀ ▝▀▘ ▀ ▀▘▝▀ ▘ ▘
▗▐ ▌ ▀▛▘ ▜
▌ ▌▄▜▀ ▛▀▖ ▌▞▀▖▛▚▀▖▛▀▖▞▀▖▙▀▖▝▀▖▐
▐▐▐ ▐▐ ▖▌ ▌ ▌▛▀ ▌▐ ▌▙▄▘▌ ▌▌ ▞▀▌▐
▘▘ ▀▘▀ ▘ ▘ ▘▝▀▘▘▝ ▘▌ ▝▀ ▘ ▝▀▘ ▘
------------------------------------------------
Temporal is a durable execution engine that lets you write reliable, long-running applications as normal code.
It abstracts away retries, state persistence, and timeouts — so your business logic stays simple and fault-tolerant.
- Originally built at Uber, now an open-source CNCF project.
Go handles concurrency very well, but durable, long-running workflow reliability requires extra effort.
Go’s concurrency model (goroutines, channels) is great for parallelism but not for reliability.
It fits naturally with Go’s programming style and error handling.
https://docs.temporal.io/develop/go/
Temporal is polyglot — you’re not limited to Go.
You can build reliable workflows in multiple languages, keeping the same durable execution guarantees.
Workflows, Activities, Workers, Task Queues, and durable execution.
This allows you to pick the language that fits your domain while still benefiting from Temporal’s reliability.
https://docs.temporal.io/develop/
The durable function that represents business logic.
The actual work being done
(e.g. calling an API, processing data)
Runs your workflows and activities.
In day-to-day conversations, the term Worker is used to denote either a Worker Program, a Worker Process, or a Worker Entity.
Connects clients and workers.
A Task Queue is a lightweight, dynamically allocated queue that one or more Worker Entities poll for Tasks.
Durable Execution in the context of Temporal refers to the ability of a Workflow Execution to maintain its state and progress even in the face of failures, crashes, or server outages.
The orchestration engine that ensures durability and state persistence.
The Temporal Server consists of four independently scalable services:
Frontend gateway: for rate limiting, routing, authorizing. History subsystem: maintains data (mutable state, queues, and timers). Matching subsystem: hosts Task Queues for dispatching. Worker Service: for internal background Workflows.
Acts as the bridge for communication between your applications and the Temporal Service.
The most common operations;
Get the result of Workflow Execution. List Workflow Executions. Query a Workflow Execution. Signal a Workflow Execution. Start a Workflow Execution.
▄▖ ▜ ▜ ▗ ▘▗
▐ █▌▛▛▌▛▌▛▌▛▘▀▌▐ ▐ █▌▜▘▛▘ ▌▌▛▌▌▌ ▌▌▌▛▘▌▜▘█▌
▐ ▙▖▌▌▌▙▌▙▌▌ █▌▐▖ ▐▖▙▖▐▖▄▌ ▙▌▙▌▙▌ ▚▚▘▌ ▌▐▖▙▖
▌ ▄▌
▜ ▘ ▌ ▜ ▌▘ ▗ ▘▌ ▗ ▌
▛▘█▌▐ ▌▀▌▛▌▐ █▌ ▛▌▌▛▘▜▘▛▘▌▛▌▌▌▜▘█▌▛▌
▌ ▙▖▐▖▌█▌▙▌▐▖▙▖▗ ▙▌▌▄▌▐▖▌ ▌▙▌▙▌▐▖▙▖▙▌
▘
▗ ▘ ▜ ▌
▛▘▌▌▛▘▜▘█▌▛▛▌▛▘ ▀▌▛▘ ▛▘▌▛▛▌▛▌▐ █▌ ▛▘▛▌▛▌█▌
▄▌▙▌▄▌▐▖▙▖▌▌▌▄▌ █▌▄▌ ▄▌▌▌▌▌▙▌▐▖▙▖ ▙▖▙▌▙▌▙▖▗
▄▌ ▌