# cadence-workflow mit Homebrew installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für cadence-workflow in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:cadence-workflow ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install cadence-workflow ``` Evidenz: local Homebrew formula metadata ## Paketfakten - **Paketschlüssel:** brew:cadence-workflow - **Paketmanager:** Homebrew - **Paketmanager-Seite:** - **Version:** 1.4.1 - **Quellzusammenfassung:** Distributed, scalable, durable, and highly available orchestration engine - **Homepage:** - **Repository:** - **Upstream-Dokumentation:** - **Lizenz:** Apache-2.0 - **Quellarchiv:** - **Zuletzt aktualisiert:** 2026-07-04T16:53:42+09:00 - **Generiert:** 2026-07-08T18:08:21+00:00 ## Executables - cadence-canary (cli) - cadence-cassandra-tool (cli) - cadence-server (cli) - cadence-sql-tool (cli) - cadence-canary (Alias) - cadence-cassandra-tool (Alias) - cadence-server (Alias) - cadence-sql-tool (Alias) ## Build-Abhängigkeiten - go ## Installationsverhalten - Post-install-Hook: nicht definiert - Bottle: verfügbar auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Version und Aktualität - Seite generiert: 2026-07-08 - Manager-Version: 1.4.1 - Manager aktualisiert: 2026-07-04 - lokale Daten: OK - Upstream-Repository: https://github.com/cadence-workflow/cadence - Info: No cached GitHub release or tag data was available. ## Projektgeschichte und Nutzung Cadence Workflow is Uber-originated durable execution infrastructure for long-running business logic. It provides a distributed orchestration engine, CLI, SDKs, persistence integrations, visibility services, and operational tools for workflows that need retries, timers, signals, history, and resilience across process crashes. ### Projektgeschichte The Cadence repository describes the platform as open source since 2017 and containing the core orchestration engine plus CLI, schema management, benchmark, and canary tools. Its backend runs multiple services with a database such as Cassandra, MySQL, or PostgreSQL, optionally paired with Kafka and Elasticsearch/OpenSearch-style visibility components. Cadence grew out of the durable workflow lineage associated with systems such as Amazon SWF and later inspired the 2019 Temporal fork. Official Cadence documentation now frames Cadence and Temporal as sharing the same durable execution model while diverging in governance, ecosystem, cost model, and operational emphasis. ### Adoptionsgeschichte Cadence's adoption is anchored by large-scale Uber production use. The official comparison page says Cadence grew at Uber from fewer than 100 domains at the Temporal fork point to over 4,000 domains, facilitating billions of workflows and hundreds of billions of updates monthly. The project also moved into broader open-source governance: the official FAQ identifies Cadence as a CNCF Sandbox project under the Linux Foundation, with an ecosystem of about 150 companies and open governance. The Homebrew formula packages the server-side tools and CLI-oriented binaries for local development and operations. ### Wie es verwendet wird A typical Cadence deployment runs backend services, persistence, optional visibility infrastructure, and workers containing application workflow code. Operators use the Cadence CLI to inspect and operate workflows, task lists, domains, and clusters; the Homebrew package includes server, SQL schema, Cassandra schema, and canary tools. ### Warum Paket-Nerds sich dafür interessieren Cadence is significant in package-manager culture because it packages a distributed system, not just a command. The formula exposes multiple operational binaries, schema tools, config trees, and version-coupled server/client expectations, which makes it a useful case study for packaging infrastructure software that straddles local development, production operations, and service orchestration. ### Zeitleiste - 2017: Cadence is open sourced according to the official repository README. - 2019: Temporal is created as a fork of Cadence. - 2020s: Cadence continues as Uber-scale durable execution infrastructure with Go and Java SDKs, CLI, Web UI, and schema tools. - 2023: Cadence joins the CNCF Sandbox, per official Cadence documentation. - 2026: Official docs describe 4,000+ Uber domains and billions of workflows monthly. ### Related projects - Related projects include the official Cadence Go and Java SDKs, Cadence Web UI, Cadence IDLs, Helm charts, iWF, and Temporal. The durable execution lineage is commonly discussed alongside Amazon SWF and Azure Durable Functions. ### Quellen - - - - source_facts.package-manager ## Sicherheitshinweise broad file, network, media, or database tool signal. infrastructure mutation or orchestration signal. - **Geiger-Risiko:** orange / mittel - broad file, network, media, or database tool signal - infrastructure mutation or orchestration signal ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: config/, config/base.yaml, config/development.yaml, config/.yaml, config/.yaml, cadence/config/dynamicconfig/development.yaml, /etc/custom-dynamicconfig/development.yaml, config/config_template.yaml ## Details aus der Quelldatenbank - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** cadence-workflow - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Conflicts With:** cadence - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Verwandte Links - [Cloud CLI packages](https://www.automicvault.com/de/pkg/cloud-clis/) - Belongs to a cloud or infrastructure command family. - [Secret-risk packages](https://www.automicvault.com/de/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals. - [Terminal utility packages](https://www.automicvault.com/de/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Networking and protocol packages](https://www.automicvault.com/de/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata. - [go](https://www.automicvault.com/de/pkg/brew/go/) - Build dependency declared by Homebrew. - [apache-brooklyn-cli](https://www.automicvault.com/de/pkg/brew/apache-brooklyn-cli/) - Shares av.db curated category or tags: cli, cloud-infrastructure, orchestration. - [dstack](https://www.automicvault.com/de/pkg/brew/dstack/) - Shares av.db curated category or tags: cli, cloud-infrastructure, orchestration. - [etcd](https://www.automicvault.com/de/pkg/brew/etcd/) - Shares av.db curated category or tags: cli, cloud-infrastructure, distributed-systems. - [juju](https://www.automicvault.com/de/pkg/brew/juju/) - Shares av.db curated category or tags: cli, cloud-infrastructure, orchestration. - [liqoctl](https://www.automicvault.com/de/pkg/brew/liqoctl/) - Shares av.db curated category or tags: cli, cloud-infrastructure, orchestration. - [nomad-pack](https://www.automicvault.com/de/pkg/brew/nomad-pack/) - Shares av.db curated category or tags: cli, cloud-infrastructure, orchestration. - [openliberty-jakartaee8](https://www.automicvault.com/de/pkg/brew/openliberty-jakartaee8/) - Shares av.db curated category or tags: cli, cloud-infrastructure, microservices. - [openliberty-jakartaee9](https://www.automicvault.com/de/pkg/brew/openliberty-jakartaee9/) - Shares av.db curated category or tags: cli, cloud-infrastructure, microservices. - [inngest-cli](https://www.automicvault.com/de/pkg/npm/inngest-cli/) - Local package facts share a topical domain. Shared terms: cli, cloud, cloud-infrastructure, infrastructure, orchestration. ## Combined YAML source View the package source record on GitHub. [combined/cadence-workflow.yml](https://github.com/automic-vault/db/blob/main/combined/cadence-workflow.yml) ## Quellen - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - cross-ecosystem install command graph