Announcing the Zeebe 0.15 Release: Start Events, Boundary Events, and More

Written by Mike Winters on in the Releases category.

The Zeebe team is happy to announce the 0.15 release. You can download Zeebe 0.15 from the release page on Github.

In this post, we’ll discuss some of the highlights from the release and share other project updates.

Questions? Feedback? The Community page on our website lists a number of ways that you can get in touch with us. We monitor and respond to messages on the Slack group and user forum on an ongoing basis, and we’d love to hear from you.

Zeebe 0.15 Release Highlights

Zeebe 0.15 includes more progress with BPMN symbols, adding support for the Message Start Event and Timer Start Event as well as Non-Interrupting Boundary Events.

The Message Start Event makes it possible to create a workflow instance based on the receipt of a message. We could modify our typical order process example so that new workflow instances are started whenever an “Order Placed” message is published by an external system and received by Zeebe.

An order process with a message start event.

Learn more about the Message Start Event in the documentation.

The Timer Start Event makes it possible to create a workflow instances periodically based on some time characteristic. For example, we might use the Timer Start Event to schedule a backup workflow that runs once every 24 hours.

A file backup process with a timer start event.

Learn more about the Timer Start Event in the documentation.

Non-interrupting Boundary Events makes it possible to follow an outgoing sequence flow from an event without cancelling the activity to which the event is attached.

For example, in our order process, we might want to send a customer an update if an order hasn’t shipped within 48 hours and another update every 48 hours after that until the order ships; however, we don’t want to cancel order fulfillment when we send these notifications.

In this case, we can use the Non-interrupting Timer Boundary Event.

An order process with a non-interrupting timer boundary event.

Learn more about the Non-interrupting Message Boundary Event and Non-interrupting Timer Boundary Event in the documentation.

These features represent the last of the BPMN work that’s planned before a production-ready Zeebe release in mid-2019. That doesn’t mean we’re done working on BPMN symbols forever, and we expect to add support for more symbols in the future based on user feedback, but these are the final BPMN-related features on our near-term roadmap.

Kafka Summit NYC - April 2019

The one and only Bernd Rücker, Camunda co-founder and Developer Advocate, will be presenting at Kafka Summit in New York City on April 2, 2019. You can read more about his talk “Complex Event Flows In Distributed Systems”, and if you’re at the event, be sure to swing by the Camunda booth to ask questions about Zeebe and microservices orchestration.

And in case you missed it, Bernd wrote a blog post in December 2018 describing a prototype Apache Kafka connector for Zeebe, including a link to the repository so you can try it out yourself.

Credit Sense Goes Zeebe

Credit Sense, a company providing transaction analysis for financial institutions, published a blog post about their experience with Zeebe so far where they also highlight a NodeJS client they created then open sourced for the community.

It’s one of the first public Zeebe user stories that we’re aware of, and we greatly appreciate Credit Sense’s NodeJS contribution, so we wanted to be sure to highlight it here.

That’s all for now. Thanks for reading, and please don’t hesitate to reach out with questions.