Taming the event chaos with a workflow engineby Filip Hrisafov & Joram Barrez

So, you've built your solution: a set of well-architected microservices, a shiny UI and tying it all together with event sourcing using Kafka. However, now the legal department comes along and they're asking to get insight on which data is used where and by whom. Marketing wants to generate daily PDF reports to publish on the website. Management is requesting that a ticket gets created whenever something goes wrong with a business-critical event. And yet another department wants to reuse some of the events for a customized integration with a legacy system. You can feel it, soon enough it's chaos. Pure pandemonium. A cobweb of scattered data and services calling each other or external API's. And nobody around anymore can keep the oversight. In this session we present how to solve these problems with Flowable, an open source set of engines implementing the BPMN (process), CMMN (case) and DMN (rules) standards. Through multiple live-demos and lots of code examples, we demonstrate how to orchestrate, manipulate and eventually tame the event chaos using Flowable, Spring Boot and Kafka. FILIP HRISAFOV Filip Hrisafov is a Platform Architect at Flowable and a Flowable core developer. He is also the project lead of the MapStruct project. He is passionate about Open Source and sharing the knowledge with the Open Source community. JORAM BARREZ Joram Barrez is a Flowable open source Core Developer and Principal Software Architect at Flowable AG. He’s been active in the open source space for more than a decade: before co-founding Flowable, he co-founded Activiti and was a jBPM core developer at Red Hat.