OSS TanbouSign in with GitHub

A durable execution platform that runs and records workflows across failures and restarts

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
23,476
Primary language
Go
License
MIT
Repository last updated
Oct 5, 2026
On this page

Overview

Temporal is a durable execution platform that records application logic as Workflows and manages retries and resumption across failures or restarts. It lets teams express order processing and long-running business procedures in code without building their own state machine.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

What it provides

Temporal Server manages Workflow history and tasks while Workers execute Workflow and Activity code. The official SDK test environment can advance workflow time and check results or failures without a server.

Sources: [1][2][3][7]

Best fit

Where it fits

It fits processes lasting minutes to months that must track transient service failures, retries, and compensation. The pinned example runs a Workflow that waits and returns a greeting in the Go SDK test environment.

Sources: [1][2]

Before adoption

What to verify before adoption

This repository contains Temporal Server; Workflow implementations require a supported SDK. Production operation also requires deliberate persistence, availability, encryption, and monitoring design. GitHub and the v1.32.0 LICENSE report MIT. The pinned Go SDK 1.49.0 used by this guide requires Go 1.26 or later.

Sources: [3][4][5][6]

Official sources

  1. [1]temporalio/temporal README at v1.32.0(2026-10-05)
  2. [2]Temporal official documentation(2026-10-05)
  3. [3]Temporal fixed version source(2026-10-05)
  4. [4]temporalio/temporal LICENSE at v1.32.0(2026-10-05)
  5. [5]temporalio/temporal GitHub metadata(2026-10-05)
  6. [6]Temporal Go SDK v1.49.0 go.mod(2026-10-05)
  7. [7]Temporal Go SDK testsuite v1.49.0 API(2026-10-05)
Supplemental curator note

It fits long-running business operations that need observable history and retries. Verify deterministic Workflow behavior in the SDK test environment before moving to a local development server.

Try it in 3 steps

  1. 1

    Create a pinned SDK test project

    Requires Go 1.26 or later and Git. Create a temporary module pinned to Temporal Go SDK 1.49.0 and testify 1.10.0.

    demo=$(mktemp -d "${TMPDIR:-/tmp}/temporal-workflow.XXXXXX") && cd "$demo" && go mod init example.com/temporal-demo && go get go.temporal.io/sdk@v1.49.0 && go get github.com/stretchr/testify@v1.10.0
  2. 2

    Write a Workflow with a timer

    Write a Workflow that waits one hour in Workflow time and returns a named greeting, plus its test.

    printf '%s\n' 'package demo' 'import (' ' "fmt"' ' "testing"' ' "time"' ' "github.com/stretchr/testify/require"' ' "go.temporal.io/sdk/testsuite"' ' "go.temporal.io/sdk/workflow"' ')' 'func Greeting(ctx workflow.Context, name string) (string,error) {' ' _ = workflow.Sleep(ctx, time.Hour)' ' return fmt.Sprintf("Hello %s", name), nil' '}' 'func TestGreeting(t *testing.T) {' ' var suite testsuite.WorkflowTestSuite' ' env := suite.NewTestWorkflowEnvironment()' ' env.ExecuteWorkflow(Greeting, "Ada")' ' require.True(t, env.IsWorkflowCompleted())' ' require.NoError(t, env.GetWorkflowError())' ' var result string' ' require.NoError(t, env.GetWorkflowResult(&result))' ' require.Equal(t, "Hello Ada", result)' '}' > workflow_test.go
  3. 3

    Verify the result without a server

    Run the SDK test environment, which advances virtual time and requires completion with Hello Ada. No Temporal Server or external service is started.

    go test -run TestGreeting -v
Check the official README

Growth

Growth trends · Last 30 days

23,476 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
130
Open PRs
472

Development activity is still being collected.

Built with

Categories and tags

Categories

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • workflows
  • workflow-engine
  • workflow-automation
  • workflow-management
  • workflow-management-system
  • distributed-systems
  • golang
  • service-bus
  • service-fabric
  • microservices-architecture
  • microservice-framework
  • microservice-orchestration
Stars
23,476
Forks
1,973
Watchers
123
Open issues
583
Contributors
293
Owner type
Organization
Primary language
Go
License
MIT
Repository last updated
Oct 5, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?