Skip to main content

Cadence

Orchestrate with Confidence: The Open-Source Workflow Engine for Tomorrow

🔬 What is Cadence?

Featured reading

Blog
Introducing Cadence Schedules
Cadence Schedules bring first-class recurring workflow execution to the platform with overlap policies, backfill, pause/unpause, and full observability, all without touching your workflow code.
Read post →
Doc
Schedules
Cadence Schedules let you run workflows on a recurring cadence with overlap policies, backfill, pause/unpause, and catch-up, without writing any scheduling glue code in your workflow.
Learn more →
Video
Custom Workflow Controls in Cadence Web
What if your workflow could tell operators exactly what's happening, and let them take action, right from the Cadence Web UI?
Watch video →
Blog
Encrypt Cadence History Payloads (And Know What You Didn't Encrypt)
AES-256-GCM encryption makes Cadence history payloads opaque, but the DataConverter only covers part of the data surface.
Read post →
FAQ
Cadence FAQ
Answers to common questions about Cadence — what it is, how workflows and activities differ, how failures are handled, and when to use it instead of a message queue.
Read FAQ →
FAQ
Migrating from Temporal to Cadence
Practical guide for migrating Go or Java applications from Temporal to Cadence — SDK package mapping, concept renames, and client setup differences.
Read FAQ →
Community
Community Meetups
Join the recurring Cadence community meetup to share demos, ask questions, and connect with maintainers.
Join us →
Blog
Bypass the 2 MB Limit Without Shrinking Your Workflow
The claim-check pattern offloads large Cadence payloads to an external blob store so only a tiny reference travels through workflow history.
Read post →
Blog
Your Workflow History Is Storing More Than You Think
Cadence writes every workflow input, activity parameter, signal, and query response into history as JSON — a custom DataConverter can add compression, encryption, or claim-check offload without changing workflow code.
Read post →
Doc
Workflow Engine and Workflow Orchestration
Cadence is an open-source workflow engine for Go, Java, and Python — fault-tolerant, stateful, and built for long-running distributed applications.
Learn more →
Doc
Open Source Workflow Engine
Cadence is an open-source, self-hostable workflow engine for durable, fault-tolerant distributed applications — deploy on SQLite, Docker, or Kubernetes.
Learn more →
Blog
Signal Handling in the Cadence Python Client
Learn how to register a workflow signal handler and send signals to a running workflow using the Cadence Python client.
Read post →
Blog
Two Hidden Deadlocks in Cadence Matching: 1 Day, 2 Engineers, 6 Lines of Code
How the new Cadence Shard Manager found and mitigated two latent deadlocks in the Matching service in a single day.
Read post →
FAQ
Cadence Best Practices
Answers to common questions and recommended patterns for building reliable, maintainable Cadence workflows and activities.
Read FAQ →
Doc
Deploy Cadence with Helm on GKE (PostgreSQL + OpenSearch)
A codelab for deploying Cadence on Google Kubernetes Engine using Helm with PostgreSQL, Kafka, and OpenSearch for advanced visibility.
Start codelab →
Doc
Data Converters: Encryption & Compression
Implement custom Cadence DataConverters to compress, encrypt, serialize, or offload workflow payloads using the Go and Java samples.
Learn more →
Doc
How To Write Tests With Workflow Replayer and Shadower
A codelab on writing Go tests for Cadence workflows using the Workflow Replayer and Shadower to catch non-deterministic changes.
Start codelab →