The Zeebe Blog
We’re back with another round of Zeebe and Operate alpha releases just in time for the end of 2019, and we’re excited to share what’s new.
You can find out how to get started with Zeebe and Operate in the docs.
In the rest of the post, we’ll highlight the new capabilities included in this release.
BPMN Support in Zeebe: Event Subprocess with Message Start Event In our November 2019 alpha release post, we announced support for the timer event subprocess, and with this alpha2 release, we’ve added support for the interrupting and non-interrupting message event subprocess, too.
I get questions about running Zeebe at “zero-scale”. That means workers that consume no resources when there are no tasks to perform.
The Zeebe service on Camunda Cloud includes a generic HTTP-Worker that can be used to achieve this. The HTTP-Worker polls for jobs of type “Camunda-HTTP”, and then invokes a REST endpoint based on the HTTP verb and URL set in the task headers. If you are not on Camunda Cloud you can use zeebe-http-worker, or just write your own.
I am happy to announce that Spring Zeebe 0.7.0 has been released using Zeebe Core 0.21.1 and Spring Boot 2.2.0.RELEASE.
If you find any issues with these projects please report them here.
Moving forward we want to quickly align Spring Zeebe projects with Zeebe releases in a more coordinated way and we want to refine these projects dependencies to make sure that they are aligned with the Spring Boot release train.
We’re excited to announce the release of Zeebe 0.22.0-alpha1 and Operate 1.2.0-alpha1.
You can find information about how to get started with Zeebe and Operate in the docs.
In the rest of this post, we’ll cover highlights from the releases along with other project updates.
I recently spoke with Dan Shapir, CTO of Israeli/Australian fintech company Pay-K, and the author of the Zeebe NestJS integration. We talk about Zeebe; NestJS; building reliable, refactorable applications at scale; and hiring developers in one of the most competitive markets in the world.
Designing a resilient system means planning for, and alerting on various failure states. The Zeebe Cloud Canary npm package adds alerting to your Node.js Zeebe applications.
There are a few things that can go wrong in a Zeebe system that you definitely want to surface operationally. Your client applications might exception and halt. The broker might fail - whether due to a hardware failure or some edge-case condition that puts it in an infinite restart loop while recovering (it could be memory constrained, for example, and rescheduled by K8s before it can recover its state on boot up).
The upcoming 0.22 release of Zeebe includes a feature many users have been asking for: the ability to start a workflow and retrieve its outcome with a single command.
The new gRPC command CreateWorkflowInstanceWithResult is available for testing in the current SNAPSHOT Docker image of Zeebe and the zeebe-node-next version of the Node.js client.
This command starts a workflow instance and returns the outcome when the workflow completes.
Use-cases A common scenario is to start a workflow in response to a REST request, and send back the outcome from the workflow in the REST response.
In this tutorial you will learn how to get a simple process definition running into a Zeebe Cluster which runs inside Kubernetes. The tutorial covers:
How to install Zeebe in your Kubernetes Cluster using the official Zeebe Helm Charts How to model a process definition with Zeebe Modeler How to interact with the Zeebe Cluster once it is running with zbctl (deploy and create new workflow instances) How to create Zeebe Workers with Spring Boot and How to monitor the process executions with Camunda Operate.
Jesse Van Muijden and his team, working in the Ministry of Social Welfare in the Netherlands, have developed a Zeebe-based system that brings transparency to government processes for citizens.
In this interview, we talk about the tech stack: Node.js, Kafka.js, Java, Docker, and Zeebe, the innovative solution they’ve designed, and Jesse’s experience developing on Zeebe in a “beyond agile” project, even as Zeebe has been undergoing development.
Check out the source code for their project on GitLab.
Today, we’re happy to announce the release of Zeebe 0.21 and Operate 1.1.0.
Refer to the Zeebe docs for instructions to download a release.
In this blog post we’ll highlight the changes since the 0.20 release.
New and Changed in Zeebe 0.21 New and Changed in Zeebe Modeler 0.7.0 New and Changed in Operate 1.1.0 New and Changed in Zeebe 0.21 Java 11 TLS Support on Gateway and Clients OAuth Support in Clients Broker Backpressure Long-polling Workers New BPMN Symbol: Multi-instance subprocess Java 11 Prior to 0.