Two C's and three D's. About Camel, Camunda and Domain-Driven Design!

We think it is about time to meet again! :-) Jürgen, Markus, Peter, Stephan and me want to meet you again! We have beer, beverages, some food, a pretty cool location (with a roof!)... and the following program:

18:00 Welcome Reception. Get yourself a drink!

~ 18:30 Camel, Camunda and both C’s together!

In his talk Stephan Pelikan, senior developer working for PHACTUM, will give you an overview of Apache’s Camel project: why you should care and what this tool can do for you. Camel is an implementation of many of the important “Enterprise Integration Patterns” described in Gregor Hohpe’s famous book! Maybe you already know that Camel is easily usable together with Camunda? By combining the two Stephan tackles the need to route information coming from different sources to processes. And to do the opposite: routing information from the process to different targets and recipients. Going beyond the basics, Stephan will explain the relationship to Camunda’s “External Tasks”, and how one can leverage them to decouple the technical concerns of process execution and communication with “the world out there”. He will show us what he contributed to the Camunda/Camel integration project to enable that degree of decoupling. Expect code examples and real life experience of more than two years using Camel with Camunda!

~ 19:30 Break. Get yourself a drink and grab some finger food!

~ 20:00 Domain-Driven Design. Relating three D’s to Process Modeling!

In this talk Martin Schimak introduces you to central ideas of “Domain-Driven Design” (DDD) and relates them to approaches we find in process modeling and execution. DDD is a software design discipline first described in 2004, when Eric Evans published his nowadays well-known “blue book”. Since then, DDD has become a movement, which cannot be fully appreciated by reading any single book. It complements agile processes by addressing the engineering issues we face when building software for more complex business. One of Evans' central suggestions should be a no-brainer in 2018: bring software developers together with domain experts and engage in a close collaboration! But how do we actually deal with the unavoidable complexities of that endeavour? DDD suggests a healthy obsession with language and to embrace modeling and design as the important ongoing concern for our core initiatives. Modeling... yes, but: in a lightweight manner. Practically achievable. Iterative. And closely aligned with what matters: executable software.

~ 21:00 Stay a bit longer! And get yourself a drink! :-)