“There is a lot of valuable information in this Slack, but whenever I come back to find it, it’s gone because of the 10,000 message limit. Can we move this community to Discord, which has persistent message history?” That message, from a community member in the Zeebe Slack, triggered a DevRel project that resulted in the Slack Archivist – a Slack bot that allows valuable conversations to be archived from the community Slack to a dedicated searchable topic in our Discourse-powered Forum. The Problem Slack is ubiquitous. You probably have it open right now, and are in several different Slack teams. We use Slack internally at Camunda, on a paid plan, and when it came time to stand something up...

One of the things that I love about being a Developer Advocate is attending and speaking at conferences. I loved that as a developer – in fact, I first met (now, fellow-) Camunda Developer Advocate Niall Deehan at the Camunda booth when speaking at NDC Oslo, in 2017. A essential part of the conference experience is getting some cool swag. My wardrobe is literally 70% conference and swag t-shirts. But as a Developer Advocate, I get to be one of the people handing out cool swag (as well as still snagging some cool stuff while I’m there). The recent move to online events has changed the world – creating some constraints, but also opening some novel possibilities: No more travelling...

On Monday, July 22, Camunda CTO Daniel Meyer and Zeebe Developer Advocate Josh Wulf joined me to host a webinar to discuss the Zeebe 0.20.0 release–which, in case you haven’t heard, is our first production-ready release of Zeebe. Did we mention we’re excited? The webinar recording is available online: https://camunda.com/learn/webinars/zeebe-mid-year-update-july-2019/

Today, we released Zeebe 0.20.0, and we’re really excited about this release. It’s a milestone for the project and the first time we’re removing the “developer preview” label from Zeebe and designating it “production ready”. You can learn more about Zeebe 0.20.0 here. Along with production readiness, there’s another important update with this release: with Zeebe 0.20.0, we’re introducing the Zeebe Community License v1.0. We decided to make this license change early in the Zeebe journey before we had already reached a “production-ready” state so that users can take applications into production with an understanding of our vision for Zeebe from both a technical and licensing standpoint.

As the year comes to a close, we’ll take a moment to review what was accomplished in Zeebe in 2018 and discuss what’s next to come. 2018 was an exciting year with many new features and significant conceptual updates that changed the scope of Zeebe. We’ll cover both in this post, and we’ll also talk about our efforts to spread the word about Zeebe around the globe.

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.