Cadence is a distributed, scalable, durable, and highly available orchestration engine we developed at Uber Engineering to execute asynchronous long-running business logic in a scalable and resilient way.
Business logic is modeled as workflows and activities. Workflows are the implementation of coordination logic. Its sole purpose is to orchestrate activity executions. Activities are the implementation of a particular task in the business logic. The workflow and activity implementation are hosted and executed in worker processes. These workers long-poll the Cadence server for tasks, execute the tasks by invoking either a workflow or activity implementation, and return the results of the task back to the Cadence server. Furthermore, the workers can be implemented as completely stateless services which in turn allows for unlimited horizontal scaling.
The Cadence server brokers and persists tasks and events generated during workflow execution, which provides certain scalability and reliability guarantees for workflow executions. An individual activity execution is not fault tolerant as it can fail for various reasons. But the workflow that defines in which order and how (location, input parameters, timeouts, etc.) activities are executed is guaranteed to continue execution under various failure conditions.
This repo contains the source code of the Cadence server. To implement workflows, activities and worker use Go client or Java client.
See Maxim's talk at Data@Scale Conference for an architectural overview of Cadence.
We highly recommend that you use Cadence service docker to run the service.
Try out the sample recipes for Go or Java to get started.
Try out Cadence command-line tool to perform various tasks on Cadence
Try out Cadence Web UI to view your workflows on Cadence.
(This is already available at localhost:8088 if you run Cadence with docker compose)
We'd love your help in making Cadence great. Please review our contribution guide.
If you'd like to propose a new feature, first join the Cadence discussion group and Slack channel to start a discussion and check if there are existing design discussions. Also peruse our design docs in case a feature has been designed but not yet implemented. Once you're sure the proposal is not covered elsewhere, please follow our proposal instructions.
MIT License, please see LICENSE for details.