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.
The Zeebe team is pleased to announce the Zeebe 0.11.0 release, which includes:
- Snapshot replication for fast failover
- An updated default output mapping for task and workflow instance payloads for simpler workflow creation
- Easier access to deployment events, including a list of all workflows deployed to Zeebe
- Accessing and setting the payload of workflow or job as generic map or POJO
In the rest of this post, we’ll cover release highlights in more detail and point you to resources for getting started with Zeebe.
It’s time for the second 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.
In the past few weeks, we’ve mentioned Zeebe’s performance in horizontal scalability benchmarks that we run internally, but we haven’t yet explained how exactly we run these benchmarks. We decided we should take it one step further and open up the benchmark to anyone who wants to try it.
Update: On Monday, June 11, the Zeebe team released version 0.10.1 (download and changelog available here), a patch that fixes an issue with stream processing, and also released a 0.10.1 update for zbctl, the Zeebe command line interface (download and changelog available here).
The Zeebe team is pleased to announce the Zeebe 0.10.0 release, which includes:
Welcome to the first-ever edition of “What’s New In Zeebe”, where we share our progress on the journey of building Zeebe, the world’s first high-throughput, resilient, and horizontally-scalable workflow engine.
The Zeebe team is pleased to announce the Zeebe 0.9.0 release. In this post, we’ll provide a brief overview of release highlights along with resources to help you get started.