Zeebe
Zeebe is a distributed workflow engine for orchestrating business processes across multiple microservices, powering Camunda Platform 8.
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
11/100 Low
- Maintained
- 0last commit 1502 days ago
- Popular
- 00 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 404 GB minimum RAM, runs on ARM
- GitHub stars
- 0
- Open issues
- 15
- Last commit
- 2022-10-11
- Activity
- stale
Checked 16 days ago - source: GitHub (kitepad/zeebe)
Resources & Compatibility
Minimum requirements: 4 GB RAM, 32 GB disk. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Install the Pyzeebe Python package Run `pip install pyzeebe` in the same place where your script will run. This installs the Python helper that lets your code talk to the Zeebe broker, so your imports and Zeebe calls will work. source
- Connect to the Zeebe broker address Point the connection at the Zeebe broker's host and port, for example by using `create_insecure_channel(grpc_address='localhost:26500')`. If this address is wrong, your worker or client cannot reach Zeebe and processes or jobs will not start. source
- Start the worker to listen for jobs After defining your task functions, start the worker with `loop.run_until_complete(worker.work())`. This begins the Python event loop that keeps the worker checking for jobs, so your tasks will actually get processed instead of just being defined. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Why does my PyZeebe worker fail to start processes or jobs?
Install PyZeebe and point the connection at the broker's host and port, for example local port 26500. If the address is wrong, the worker or client cannot reach Zeebe.
How are Zeebe workflows deployed?
Zeebe workflows are modeled in BPMN and deployed to a Zeebe broker.
Is there a price list for self-hosted Zeebe 8.6 production use?
The source only records a request for a price list for self-hosted Zeebe 8.6 production use, not the price itself.
Can a self-managed Zeebe deployment become inactive without error logs?
A self-managed test deployment has experienced Zeebe becoming inactive without further notice or error logs.
Answers sourced from forum.camunda.io, forum.camunda.io, forum.camunda.io, github.com
Community
- Drinking Our Champagne: Chaos Experiments with Zeebe against Zeebe - Reddit (reddit)
- Price list for self-hosted Zeebe 8.6 - #3 by vat78 - Discussion ... (forum)
- Welcome to the Zeebe forum - Community Feedback - Camunda Forum (forum)
- Understanding Zeebe - Discussion & Questions - Camunda Forum (forum)
Collected 48 days ago - public community threads