The Zeebe team is excited to announce the 0.12 release. To get started with Zeebe 0.12, please see our installation guide.
It’s been 3 months since the Zeebe 0.11 release, and we’ve been hard at work adding new BPMN symbols that will enable Zeebe to support a range of new use cases.
The 0.12 release also includes a number of architectural changes to Zeebe that make it a much simpler system that’s more focused on its core use case: high-throughput, low-latency workflow automation.
If you’ve already read the Zeebe 0.12 release announcement, then you know that in addition to significant advancements in BPMN support, Zeebe 0.12 includes changes to the scope of the problem that Zeebe solves and introduces a couple of new concepts.
In this post, we’ll walk through those changes in more detail so that it’s clear what’s different about Zeebe and why we’ve decided to take a different approach.
Hi everyone, here’s our roundup of goings-on in and around the Zeebe project for September 2018. This month, we’ll cover newly-supported BPMN symbols in Zeebe, a Zeebe + Apache Kafka demo, conference talk recordings featuring Bernd, and more.
In this blog post, we’ll share a few highlights from the microservices orchestration survey that we fielded in July 2018. If you’d like to download a report with results, you can do so here.
Hello Zeebe community! We’re back with a “What’s New” post for August 2018 where we’ll share updates about features in Zeebe, upcoming events where you can meet our team, and other general happenings in the project.
When checking in for a flight online, normal people hope that everything works the way it’s supposed to. That usually means no error messages, and at the end of the process, getting a boarding pass in your selected format.
We at Camunda, however, are not “normal people”.
A problem during check-in is a bit of a thrill for us because it gives us a peek into how a company handles software failures in a high-traffic application.
We never know exactly what’s happening under the hood, of course, but we like to speculate.
This is part 2 in a 2-part series about BPMN and how it’s being applied to new use cases. You can find part 1 here. A sincere thanks to Bernd Rücker for his feedback during the writing of both blog posts.
Welcome back to our discussion of BPMN (Business Process Model and Notation) and its role in emerging use cases such as microservices orchestration. You don’t have to read the posts in order to be able to follow along, but if you’re new to BPMN, you might find it helpful to start with part 1.
To recap, the first post covered:
- An introduction to BPMN
- Why a well-established standard that thrived in the past can thrive in the future, too
- Common orchestration patterns supported by BPMN
- The current state and future plans of BPMN in Zeebe
In this part 2, we’ll:
- Look at examples where using a graphical model instead of a code-based model simplifies workflow definition
- Dive into tooling for building graphical models in BPMN (and other ways to define workflows)
- Reassure you that BPMN’s graphical models are nothing to be afraid of–even if you’ve had a bad experience with graphical models in the past
A sincere thanks to Bernd Rücker for his feedback during the writing of this blog post.
This is part 1 of 2 in a 2-part blog post series. Part 2 is available here.
We’re building Zeebe to be a next-generation workflow engine for emerging use cases such as microservices orchestration–use cases that may require an engine to handle hundreds of thousands (or millions) of new workflow instances per second.
And to do that, we’re using a graphical modeling standard that’s been around for almost 15 years: BPMN (Business Process Model and Notation).
It’s time for the July 2018 edition of “What’s New In Zeebe”, where we share an update of what we’re working on in between releases plus other news from the project.
When we talk about Zeebe, we also talk a lot about the challenges that organizations face when managing business processes that span many independent microservices.
“Microservices orchestration” is a useful term for describing one potential solution to this problem. But every organization will take a different approach to a microservices architecture, and we want to be sure we have a clear understanding of what microservices orchestration means to the many different users who might benefit from Zeebe.