1# Virtual Camunda Meetup Vienna! zeebe.io & Incident Handling

Camunda Vienna
Camunda Vienna
Public group

Online event

This event has passed

Details

Hi all!

It’s time to meet again! We would like to invite you to our next Camunda Meetup on Thursday, June 18th.

In 2017 Daniel Meyer came to Vienna and had a talk a about Camunda’s at that time “brand new” engine zeebe.io. Since then a lot happened and Zeebe has developed to the heart of Camunda Cloud. So we thought it’s a good idea to have a closer look at zeebe again.

We are very happy that we were able to invite Deepthi Akkoorath from Camunda to have this “closer look” together with someone who really knows what’s going on. All of you who attended the CamundaCon 2019 in Berlin might have already had a chance to see one of her talks, all those who haven’t, be sure not to let this chance slip!

Additionally Mario Fleischhacker from J-IT will have a practical talk on how to handle incidents in camunda during runtime.

And for all of you who haven't checked out Camunda Release 7.13 yet - we will give a short overview of the highlights :-)

As we do not yet know when we can finally ditch facial masks, this time the meetup will be held as a remote session!

Agenda:

6:00pm: Zoom Sessions starts
6:15pm - 6:30pm: Introduction to the meetup and Camunda
6:30pm - 7:15pm: Deepthi Akkoorath, Camunda
7:15pm - 7:30pm: Break
7:30pm - 8:00pm: Mario Fleischhacker, J-IT
8:00pm - end: Networking + Zoom breakout sessions (Feel free to bring your own drinks. :D)

------

#1 Talk

Deepthi Akkoorath / zeebe.io

Abstract:

Zeebe is the cloud-native distributed workflow engine powering Camunda Cloud. By rethinking the architecture of a workflow engine, Zeebe achieves true horizontal scalability and fault tolerance making it a perfect fit for Camunda Cloud. Let's take a look under the hood and discuss how it works.

------

#2 Talk

Mario Fleischhacker / Handling Incidents during runtime

Abstract:

Processes are usually modelled to handle expected exceptions automatically. Sometimes though, a state is reached where an incident occurs, that isn’t handled by the bpmn diagram. We developed a way to notify our systems automatically when that happens. Wanna see how we did it? Be sure to join us in our talk on handling incidents during runtime!

We are looking forward to meet you!
Peter, Maximilian, Deepthi & Mario.