A workflow engine coordinates steps while keeping durable execution state. In the original Zeebe experiment, the broker and monitoring interfaces had separate roles: running work and inspecting its progress.
The recorded local setup
git clone https://github.com/zeebe-io/zeebe-docker-compose
cd zeebe-docker-compose/operate-simple-monitor
docker-compose up -d
* Zeebe broker - port 26500
* Operate - web interface http://localhost:8080 (login: demo/demo)
* Simple Monitor - web interface http://localhost:8082
# Example bpmn file: https://raw.githubusercontent.com/zeebe-io/zeebe-docker-compose/master/bpmn/diagram_1.bpmnThe listing includes demonstration credentials and local interface ports. Those are part of the old sample, not an access-control model for an exposed deployment. The repository layout and docker-compose command have not been verified against a new release.
Durable execution still needs application rules
Retrying a failed step does not guarantee that an external side effect is safe to repeat. Worker behavior, idempotency, failure handling, and the evidence recorded by the workflow matter alongside the engine.
The source linked the Compose examples and a Java client example. No workflow or container was started for this revision.