Bernd Rücker
Passionate about developer friendly
workflow automation technology.

Newsletter:

Bio

Throughout my 15+ years in software development, I have helped automating highly scalable core workflows at global companies including T-Mobile, Lufthansa and Zalando. I have contributed to various open source workflow engines. I am co-founder and developer advocate of Camunda, an open source software company reinventing workflow automation. I co-authored "Real-Life BPMN," a popular book about workflow modeling and automation, now in its fifth edition and available in English, German and Spanish. I regularly speak at conferences and write for various magazines. I am currently focused on new workflow automation paradigms that fit into modern architectures around distributed systems, microservices, domain-driven design, event-driven architecture and reactive systems.

In entwickle seit über 15 Jahren Software und habe zahlreichen Kunden dabei geholfen, Kernprozesse zu automatisieren, so z.B. der Bestellprozesse bei Zalando, Auftragsprozesse bei T-Mobile oder Patenanträge in der Schweiz. Ich habe aktiv an der Entwicklung verschiedener Open Source Workflow Engines mitgearbeitet und bin Mitgründer der Camunda, ein Open Source Unternehmen das Workflow Automatisierung neu erfindet. Ich bin Co-Author des "Praxishandbuch BPMN", spreche regelmäßig auf Konferenzen und schreibe für verschiedene Magazine. Seit geraumer Zeit beschäftige ich mit Workflow Automation Paradigmen die in moderne Architekturen rund um Microservices, Domain Driven Design, Event Driven Architecture und reaktiver Systeme passen.

Download profile picture.

Use freely for references to me (e.g. conference websites).

Publications and Talks

Recent talks

3 common pitfalls in microservice integration and how to avoid them

2018-06 The New York City Java Meetup Group (New York)

Complex Event Flows in Distributed Systems

2018-06 QCon (New York)

3 common pitfalls in microservice integration and how to avoid them

2018-06 QCon (New York)

Lost in transaction? Über (In-)Kosistenz in verteilten Systemen

2018-06 Entwicklertag (Karlsruhe)

Workflows mit BPMN automatisieren. Lessons Learned.

2018-06 Developer Week (Nuremberg)

Lost in transaction? Strategies to deal with (in-)consistency in modern architectures.

2018-06 Devoxx Poland (Krakow)

3 common pitfalls in microservice integration and how to avoid them

2018-06 JBCN Conf (Barcelona)

Workflow automation in the serverless age

2018-05 Codemotion (Amsterdam)

Break your event chains! Complex event flows in distributed systems.

2018-05 Craft-Conf (Budapest)

3 Common Pitfalls in Microservice Integration and How to Avoid them

2018-04 Java With the Best (Online)

Zeebe.io - Event-driven Microservice Orchestration

2018-03 Java User Group (Erfurt)

Long-running services and Camunda

2018-03 DDD Meetup (Cologne)

Patience pays off. How long running services reduce complexity.

2018-03 Voxxed (Vienna)

3 Common Pitfalls in Microservice Integration and How to Avoid them

2018-03 Qcon (London)

Complex event flows in distributed systems

2018-02 O'Reilly Software Architecture (New York City)

Lost in transaction - Strategies to deal with (in-)consistency in modern architectures

2018-02 Jfokus (Stockholm)

Microservices with Camunda

2018-01 Camunda Days (Berlin, Hamburg, Düsseldorf, Frankfurt, Munic, Zürich, Vienna)

Workflow Engines at scale

2017-11 WJAX (Munic)

(Micro-)service collaboration

2017-11 WJAX (Munic)

Break your event chains

2017-11 MuCon (London)

Let your domain events flow

2017-10 KanDDDinsky (Berlin), DDD Belgium (Gent), JCon (Düsseldorf)

Complex event flows in distributed systems

2017-10 O'Reilly Software Architecture (London)

Orchestration of Microservices (Java edition)

2017-09 JUG (Amsterdam), JUG (Frankfurt)

Orchestration of Microservices (.NET edition)

2017-09 Basta (Mainz)

7 sins of workflow

2017-09 BedCon (Berlin), Java Forum Nord (Hannover)

Tackling complex event flows

2017-09 DDD Meetup (Berlin)

Let your microservices flow

2017-09 JavaBin (Trondheim, Bergen)

Orchestration of Microservices

2017-07 JFS (Stuttgart)

Orchestration of Microservices

2017-05 JAX (Mainz)

Business Rules with DMN

2017-05 JAX (Mainz)

Long running processes in DDD

2017-04 DDD eXchange (London)

Let your microservices flow

2017-04 Goto Meetup (Oslo)

Open source workflow and rule management with Camunda

2017-04 JavaBIn (Oslo)

Because your business is more complex than Netflix

2017-03 Voxxed (Vienna)

BPMN und Workflows in .NET - das geht!

2017-02 Basta (Frankfurt)

The 7 sins of workflow

2017-01 JFokus (Stockholm)

Prozesse digitalisieren - heute und morgen

2016-11 Digitalisierung und IT in Versicherungen (Vienna)

Camunda BPM

2016-11 Jfall (Ede)

BPMN & CMMN. Wann nehme ich welchen Standard?

2016-11 WJAX (Munic)

Geschäftsregeln mit DMN

2016-11 WJAX (Munic)

Workflows mit BPMN 2.0 automatisieren

2016-09 Basta (Mainz)

Workflows (BPMN), Business Rules (DMN), Case Management (CMMN) – live & in Action

2016-09 BedCon (Berlin)

BPM und Microservices

2016-07 Java EE Summit (Berlin)

Workflows mit BPMN & Business Rules mit DMN - Open Source und in Action mit Camunda BPM (won best presentation award)

2016-07 JFS (Stuttgart)

BPM War Stories. Oder: Wie baue ich eine BPM-Architektur auf?

2016-05 SEACON (Hamburg)

Open Source Workflows, Business Rules and Case Management live and in action

2015-11 Devoxx (Antwerp)

⇓ Show more ⇓

Upcoming talks and events

Orchestration of Microservices

GopherCon
2018-08-02 London

Lost in transaction? Strategies to deal with (in-)consistency in distributed systems

Full Stack Fest
2018-09-04 Barcelona

Lost in transaction? Über (In-)Kosistenz in verteilten Systemen

Herbstcampus
2018-09-05 Nurremberg

3 common pitfalls in microservice integration and how to avoid them

JavaZone Noway
2018-09-12 Oslo

3 common pitfalls in microservice integration and how to avoid them

Java Forum Nord
2018-09-13 Hannover

Kommunikation zwischen Microservices

Basta
2018-09-25 Mainz

Workflows mit BPMN automatisieren. Lessons Learned.

Basta
2018-09-25 Mainz

3 common pitfalls in microservice integration and how to avoid them

JUG
2018-09-25 Mainz

Coordinate cloud-native components using distributed state machines

Cloud Native
2018-09-28 London

3 common pitfalls in microservice integration and how to avoid them

JCon
2018-10-09 Dusseldorf

Lost in transaction? Strategies to deal with (in-)consistency in distributed systems.

JCon
2018-10-09 Dusseldorf

3 common pitfalls in microservice integration and how to avoid them

JAX
2018-10-10 London

The Big Picture: Monitoring and Orchestration of Your Microservices Landscape with Kafka and Zeebe

Kafka Summit
2018-10-16 San Francisco

Lost in transaction? Strategies to deal with (in-)consistency in distributed systems

BaselOne
2018-10-18 Basel

Orchestration of Microservices

GoLab
2018-10-23 Florence

3 common pitfalls in microservice integration and how to avoid them

O'Reilly Software Architecture
2018-10-29 London

3 common pitfalls of microservice integration

WJAX
2018-11-08 Munic

3 common pitfalls of microservice integration

Codemotion
2018-11-20 Berlin

3 common pitfalls of microservice integration

DOAG
2018-11-21 Nurremberg

3 common pitfalls in microservice integration

JVMCon
2018-11-27 Cologne

3 common pitfalls in microservice integration

.NET Developer Conference
2018-11-28 Cologne

Zeebe.io - New Open Source Project for event-driven Microservice Orchestration

JUG Münster
2018-12-05 Muenster

3 typische Stolperfallen bei der Microservice-Integration

IT Tage
2018-12-10 Frankfurt

Selected blog posts

Architecture options to run a workflow engine

This week a customer called and asked (translated into my own words and shortened):

“We do composite services, orchestrating two or three CRUD-Services to do something more useful. Our architects want to use your workflow engine for this because the orchestration flow might be long running. Is this a valid scenario for workflow? Currently we run one big central cluster for the workflow engine — won’t this get a mess?”

These are valid questions which recently we get asked a lot, especially in the context of microservices, modern SOA initiatives or domain-driven design. Modern workflow engines are incredibly flexible. In this blog post I will look at possible architectures ...

Read more...

Use Camunda without touching Java and get an easy-to-use REST-based orchestration and workflow engine

I talk a lot about microservice architectures with “non-Java-folks”, let it be a C# developer, a Node.JS/JavaScript nerd or GoLang enthusiasts. All face the problem that they need an orchestration engine in their microservice architecture — or simply want to leverage workflow, ordering of activities, handling of timeouts, Saga and compensation, or other cool features.

The Open Source BPM platform from Camunda serves these use cases very well. Developer friendliness is one of the key values behind the product ...

Read more...

Saga: How to implement complex business transactions without two phase commit.

The Saga pattern describes how to solve distributed (business) transactions without two-phase-commit as this does not scale in distributed systems. The basic idea is to break the overall transaction into multiple steps or activities. Only the steps internally can be performed in atomic transactions but the overall consistency is taken care of by the Saga. The Saga has the responsibility to either get the overall business transaction completed or to leave the system in a known termination state. So in case of errors a business rollback procedure is applied which occurs by calling compensation steps or activities in reverse order.

Read more...

Real-Life BPMN

I co-authored the "Real-Life BPMN"-book, which is currently available in the 5th edition and got dozens of 5-star ratings at amazon. We already sold more than 30.000 copies worldwide.

Get it at Amazon in English, in German or in Spanish.

The company I co-founded and love to work for as developer advocate: