Bernd Ruecker: “There is quite some value in going for reactive, asynchronous or event-driven architectures”

Bernd is an author of “Practical Process Automation” and co-author of “Real-Life BPMN”. He is a regular speaker at conferences around the world and a frequent contributor to several technology publications. He focuses on new process automation paradigms that fit into modern architectures around distributed systems, microservices, domain-driven design, event-driven architecture, and reactive systems.     

What is your background and what sparked your interest in distributed systems?

I am a software developer at heart. I worked in a lot of process automation projects in a lot of big companies. I contributed to various open-source workflow engines for more than 15 years and I’m the Co-Founder and Chief Technologist of Camunda – an open-source process automation vendor.

More and more customers distribute their systems, so I got intrigued by the challenges that come with that.

Reactive is a new buzzword for many traditional developers. What is your prediction for its importance in application development over the next couple of years?

I think there is quite some value in going for reactive, asynchronous or event-driven architectures to be able to handle the increasing complexity of todays systems. So I think almost every bigger system will have some degree of reactiveness.

 What is the biggest challenge companies deploying Reactive systems are facing?

Most developers are not very experienced with reactive systems, asynchronous communication or event-driven architecture. In fact, even a solid understanding of the challenges of distributed systems is missing for many people. This is a huge problem and quickly leads to brittle architectures.

What is the best solution to this challenge?

Learning – and speaking about learnings 🙂

 What is your most ambitious professional dream that you hope to achieve one day?

Getting workflow engine technology (or at least a solid understanding what it does and when it is useful) to almost every developer on the planet. I am on it 😉

Who should attend your talk at Reactive Summit and what will they learn?

Some interactions require state, for example as part of a so-called Saga, a long running business transaction, that is split into multiple small technical ones.  The challenge is to keep state in a way that allows your overall system and its components to stay reactive.

Every developer that has to occasionally deal with sequences of tasks will benefit from learning about Sagas and different ways to implement them, which is what I will talk about.

Do not miss Bernd and his talk “Orchestration, Conversations and the Saga Pattern: How State Helps you to Stay Reactive” at virtual Reactive Summit on November 10. Book your ticket now!

Leave a Reply