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 resilient way.
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
4 releases in the last 90 days, the latest 5 days ago, with 181 contributors on GitHub.
Gained 36% more stars in the last 90 days than in the 90 days before.
Use Cases & Benefits
- Provides a distributed, scalable, and durable orchestration engine for executing asynchronous long-running business workflows.
- Ensures fault-tolerant and highly available workflow execution with support for multiple databases and SDKs in Go and Java.
- Use for automating complex business processes that require reliable state management over extended periods.
- Use for building microservices platforms that need resilient service orchestration and workflow automation.
- Use for monitoring and debugging workflows via a web UI and CLI tools integrated with Cassandra, MySQL, or PostgreSQL backends.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
Apache 2.0
Permissive: commercial use, modification and redistribution are allowed with attribution; includes an explicit patent grant from contributors.
Community files
- README: present
- Contributing guide: present
Watch-outs
No watch-outs from GStars' checks.
General guidance from repository metadata, not legal advice. How we score
From the README
Cadence Workflow is an open-source platform since 2017 for building and running scalable, fault-tolerant, and long-running workflows. This repository contains the core orchestration engine and tools including CLI, schema managment, benchmark and canary.
Cadence backend consists of multiple services, a database (Cassandra/MySQL/PostgreSQL) and optionally Kafka+Elasticsearch. As a user, you need a worker which contains your workflow implementation. Once you have Cadence backend and worker(s) running, you can trigger workflows by using SDKs or via CLI.
Try out the sample recipes for Go or Java.
Visit http://localhost:8088 to check workflow histories and detailed traces.
You can implement your workflows with one of our client libraries:
There are also unofficial Python and Ruby SDKs developed by the community.
You can also use iWF as a DSL framework on top of Cadence.
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
Forks
930+25
Open issues
217+36
Compared with peers in Backend
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 8, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| anthropics/skills | 192.3K | +5.2K | 75 | — |
| zed-industries/zed | 94.7K | +2.3K | 75 | 6 days ago |
| google/skills | 23.8K | +2.0K | 75 | — |
| NationalSecurityAgency/ghidra | 99.4K | +1.8K | 75 | 19 days ago |
| DuarteSantos8/openGym | 20.8K | +1.7K | 75 | 7 days ago |
| cadence-workflow/cadence | 9.5K | — | 60 | 5 days ago |
| Category median | 94.7K | +2.0K | 75 | — |
Discover Repositories
Search across tracked repositories by name or description