[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-5096":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":23,"hasPages":25,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":37,"readmeContent":38,"aiSummary":39,"trendingCount":16,"starSnapshotCount":16,"syncStatus":17,"lastSyncTime":40,"discoverSource":41},5096,"cadence","cadence-workflow\u002Fcadence","cadence-workflow","Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.","https:\u002F\u002Fcadenceworkflow.io",null,"Go",9325,896,1418,129,0,2,7,42,9,76.56,"Apache License 2.0",false,"master",true,[5,27,28,29,30,31,32,33,34,35,36],"distributed-systems","golang","java","orchestration-engine","service-bus","service-fabric","services-platform","uber","workflow-automation","workflows","2026-06-12 04:00:24","# Cadence\n[![Build Status](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002Fcadence\u002Factions\u002Fworkflows\u002Fci-checks.yml\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002Fcadence\u002Factions\u002Fworkflows\u002Fci-checks.yml)\n[![Coverage](https:\u002F\u002Fcodecov.io\u002Fgh\u002Fcadence-workflow\u002Fcadence\u002Fgraph\u002Fbadge.svg?token=7SD244ImNF)](https:\u002F\u002Fcodecov.io\u002Fgh\u002Fcadence-workflow\u002Fcadence)\n[![Slack Status](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fslack-join_chat-white.svg?logo=slack&style=social)](https:\u002F\u002Fcommunityinviter.com\u002Fapps\u002Fcloud-native\u002Fcncf)\n[![Github release](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fv\u002Frelease\u002Fcadence-workflow\u002Fcadence.svg)](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002Fcadence\u002Freleases)\n[![License](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Flicense\u002Fcadence-workflow\u002Fcadence.svg)](http:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0)\n\nCadence 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.\n\n\n## Getting Started\n\nCadence backend consists of multiple services, a database (Cassandra\u002FMySQL\u002FPostgreSQL) and optionally Kafka+Elasticsearch.\nAs a user, you need a worker which contains your workflow implementation.\nOnce you have Cadence backend and worker(s) running, you can trigger workflows by using SDKs or via CLI.\n\n1. Start cadence backend components locally\n\n```\ndocker compose -f docker\u002Fdocker-compose.yml up\n```\n\n2. Run the Samples\n\nTry out the sample recipes for [Go](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002Fcadence-samples) or [Java](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002Fcadence-java-samples).\n\n3. Visit UI\n\nVisit http:\u002F\u002Flocalhost:8088 to check workflow histories and detailed traces.\n\n\n### Kubernetes Deployment\n\nFor a guided Kubernetes installation experience, [KubeStellar Console](https:\u002F\u002Fconsole.kubestellar.io\u002Fmissions\u002Finstall-cadence-workflow) provides a step-by-step mission that deploys Cadence using the official Helm chart from [cadence-charts](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002Fcadence-charts). The mission includes pre-flight checks, validation, troubleshooting, and rollback support.\n\n### Client Libraries\nYou can implement your workflows with one of our client libraries:\n- [Official Cadence Go SDK](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002Fcadence-go-client)\n- [Official Cadence Java SDK](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002Fcadence-java-client)\nThere are also unofficial [Python](https:\u002F\u002Fgithub.com\u002Ffirdaus\u002Fcadence-python) and [Ruby](https:\u002F\u002Fgithub.com\u002Fcoinbase\u002Fcadence-ruby) SDKs developed by the community.\n\nYou can also use [iWF](https:\u002F\u002Fgithub.com\u002Findeedeng\u002Fiwf) as a DSL framework on top of Cadence.\n\n### CLI\n\nCadence CLI can be used to operate workflows, tasklist, domain and even the clusters.\n\nYou can use the following ways to install Cadence CLI:\n* Use brew to install CLI: `brew install cadence-workflow`\n  * Follow the [instructions](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002Fcadence\u002Fdiscussions\u002F4457) if you need to install older versions of CLI via homebrew. Usually this is only needed when you are running a server of a too old version.\n* Use docker image for CLI: `docker run --rm ubercadence\u002Fcli:\u003CreleaseVersion>`  or `docker run --rm ubercadence\u002Fcli:master ` . Be sure to update your image when you want to try new features: `docker pull ubercadence\u002Fcli:master `\n* Build the CLI binary yourself, check out the repo and run `make cadence` to build all tools. See [CONTRIBUTING](CONTRIBUTING.md) for prerequisite of make command.\n* Build the CLI image yourself, see [instructions](docker\u002FREADME.md#diy-building-an-image-for-any-tag-or-branch)\n\nCadence CLI is a powerful tool. The commands are organized by tabs. E.g. `workflow`->`batch`->`start`, or `admin`->`workflow`->`describe`.\n\nPlease read the [documentation](https:\u002F\u002Fcadenceworkflow.io\u002Fdocs\u002Fcli\u002F#documentation) and always try out `--help` on any tab to learn & explore.\n\n### UI\n\nTry out [Cadence Web UI](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002Fcadence-web) to view your workflows on Cadence.\n(This is already available at localhost:8088 if you run Cadence with docker compose)\n\n\n### Other binaries in this repo\n\n#### Bench\u002Fstress test workflow tools\nSee [bench documentation](.\u002Fbench\u002FREADME.md).\n\n#### Periodical feature health check workflow tools(aka Canary)\nSee [canary documentation](.\u002Fcanary\u002FREADME.md).\n\n#### Schema tools for SQL and Cassandra\nThe tools are for [manual setup or upgrading database schema](docs\u002Fpersistence.md)\n\n  * If server runs with Cassandra, Use [Cadence Cassandra tool](tools\u002Fcassandra\u002FREADME.md)\n  * If server runs with SQL database, Use [Cadence SQL tool](tools\u002Fsql\u002FREADME.md)\n\nThe easiest way to get the schema tool is via homebrew.\n\n`brew install cadence-workflow` also includes `cadence-sql-tool` and `cadence-cassandra-tool`.\n * The schema files are located at `\u002Fusr\u002Flocal\u002Fetc\u002Fcadence\u002Fschema\u002F`.\n * To upgrade, make sure you remove the old ElasticSearch schema first: `mv \u002Fusr\u002Flocal\u002Fetc\u002Fcadence\u002Fschema\u002Felasticsearch \u002Fusr\u002Flocal\u002Fetc\u002Fcadence\u002Fschema\u002Felasticsearch.old && brew upgrade cadence-workflow`. Otherwise ElasticSearch schemas may not be able to get updated.\n * Follow the [instructions](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002Fcadence\u002Fdiscussions\u002F4457) if you need to install older versions of schema tools via homebrew.\n However, easier way is to use new versions of schema tools with old versions of schemas.\n All you need is to check out the older version of schemas from this repo. Run `git checkout v0.21.3` to get the v0.21.3 schemas in [the schema folder](\u002Fschema).\n\n\n## Contributing\n\nWe'd love your help in making Cadence great. Please review our [contribution guide](CONTRIBUTING.md).\n\nIf you'd like to propose a new feature, first join the [CNCF Slack workspace](https:\u002F\u002Fcommunityinviter.com\u002Fapps\u002Fcloud-native\u002Fcncf) in the **#cadence-users** channel to start a discussion.\n\nPlease visit our [documentation](https:\u002F\u002Fcadenceworkflow.io\u002Fdocs\u002Foperation-guide\u002F) site for production\u002Fcluster setup.\n\n\n### Learning Resources\nSee Maxim's talk at [Data@Scale Conference](https:\u002F\u002Fatscaleconference.com\u002Fvideos\u002Fcadence-microservice-architecture-beyond-requestreply) for an architectural overview of Cadence.\n\nVisit [cadenceworkflow.io](https:\u002F\u002Fcadenceworkflow.io) to learn more about Cadence. Join us in [Cadence Documentation](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002FCadence-Docs) project. Feel free to raise an Issue or Pull Request there.\n\n### Community\n* [Github Discussion](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002Fcadence\u002Fdiscussions)\n  * Best for Q&A, support\u002Fhelp, general discusion, and annoucement\n* [Github Issues](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002Fcadence\u002Fissues)\n  * Best for reporting bugs and feature requests\n* [StackOverflow](https:\u002F\u002Fstackoverflow.com\u002Fquestions\u002Ftagged\u002Fcadence-workflow)\n  * Best for Q&A and general discusion\n* [Slack](https:\u002F\u002Fcommunityinviter.com\u002Fapps\u002Fcloud-native\u002Fcncf) - Join **#cadence-users** channel on CNCF Slack\n  * Best for contributing\u002Fdevelopment discussion\n\n\n## Stars over time\n[![Stargazers over time](https:\u002F\u002Fstarchart.cc\u002Fuber\u002Fcadence.svg?variant=adaptive)](https:\u002F\u002Fstarchart.cc\u002Fuber\u002Fcadence)\n\n\n## License\n\nApache 2.0 License, please see [LICENSE](https:\u002F\u002Fgithub.com\u002Fcadence-workflow\u002Fcadence\u002Fblob\u002Fmaster\u002FLICENSE) for details.\n","Cadence 是一个分布式、可扩展、持久且高可用的编排引擎，用于以可扩展和弹性的方式执行异步长时间运行的业务逻辑。它支持使用 Go 和 Java 编写工作流，并提供了强大的容错能力和状态管理功能。核心特性包括自动故障恢复、版本控制和动态扩展等，适用于需要处理复杂业务流程、微服务编排以及长周期任务调度的场景。此外，Cadence 还提供了丰富的客户端库（如 Go 和 Java 的官方 SDK）及社区维护的 Python 和 Ruby 版本，方便开发者集成到现有系统中。通过其 CLI 工具或 UI 界面，用户可以轻松管理和监控工作流执行情况。","2026-06-11 03:02:30","top_language"]