cadence-workflow/cadence

Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 13 seconds ago
Added to GitGenius on September 7th, 2026
Created on February 21st, 2017
Open Issues & Pull Requests: 202 (+0)
GitHub issues: Enabled
Number of forks: 915
Total Stargazers: 9,431 (+0)
Total Subscribers: 1,420 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.2 days
Mean response time: 409.5 days
90th percentile: 1570.0 days
Tracked items: 646

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 72% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "kind/bug" is answered fastest, typically in about 13 hours, while "improvement" waits about 34 months. Almost all tracked open issues have seen activity in the last three months. Only 3% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 124
New in 7 days: 3
Closed in 7 days: 1
Avg open age: 950 days
Stale 30+ days: 98
Stale 90+ days: 15

Recent activity

Opened in 7 days: 2
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • needs-info (383)
  • kind/feature (212)
  • kind/bug (161)
  • bug (159)
  • feature (152)
  • customer (82)
  • up-for-grabs (71)
  • triage/needs-info (66)

Most active issues this week

Detailed Description

Cadence is a distributed orchestration engine that executes asynchronous long-running business logic in a scalable and resilient way.

Cadence addresses the challenge of reliably executing complex workflows across distributed systems where individual steps may fail, be retried, or span extended periods. The engine persists workflow state to a database (supporting Cassandra, MySQL, or PostgreSQL) and coordinates execution through multiple backend services. Workers running your workflow code communicate with the Cadence backend to receive tasks, execute business logic, and report results. The platform handles retries, timeouts, and state management automatically, allowing developers to write workflows as straightforward code rather than managing distributed coordination manually.

Teams should adopt Cadence when building systems that require durable, long-running processes with complex retry logic and failure handling. It suits microservice architectures where workflows orchestrate calls across multiple services, financial transaction processing, data pipelines, and any scenario where workflow state must survive service restarts. The project provides official SDKs for Go and Java, with community-maintained Python and Ruby libraries available. A web UI at localhost:8088 displays workflow histories and execution traces. Kubernetes deployment is supported through an official Helm chart, with guided installation available via KubeStellar Console. The CLI tool enables operational management of workflows, task lists, domains, and clusters.

The project maintains active continuous integration with automated testing. Code coverage is tracked and publicly reported. The team responds to community contributions through discussions and maintains multiple official client libraries alongside the core engine. Documentation includes sample implementations for both Go and Java, and the project accepts community-developed language bindings and framework layers built on top of the core platform.