Are you done yet? Mastering long-running processes in modern architectures

Are your services pushing transient failures to users? Learn how process orchestration builds resilient systems that recover from errors internally.

#1about 4 minutes

Explaining synchronous and asynchronous communication with metaphors

A pizza ordering metaphor illustrates the difference between synchronous blocking communication like a phone call and asynchronous non-blocking communication like an email.

#2about 7 minutes

Defining long-running processes and business reasons for waiting

Long-running processes are defined by periods of waiting, driven by business needs like human tasks, response delays, or mitigating buyer's remorse.

#3about 4 minutes

The hidden complexity of building stateful applications

Implementing stateful, long-running logic with simple database columns leads to accidental complexity around visibility, escalations, versioning, and reliability.

#4about 10 minutes

A live demo of a workflow engine with spring boot

A practical demonstration shows how to use a workflow engine like Camunda with Spring Boot to model, execute, and monitor a customer onboarding process.

#5about 9 minutes

Using long-running patterns to build resilient systems

Failures in distributed systems, such as an unavailable service during an airline check-in, necessitate long-running retry patterns to create a resilient architecture.

#6about 6 minutes

Implementing safe retries with idempotency and compensation

Safely retrying operations in a distributed system requires idempotent APIs to prevent duplicate actions and compensation logic to clean up after ultimate failures.

#7about 6 minutes

Designing clean service boundaries with orchestration

Empowering individual services to handle their own long-running logic, like payment retries, leads to cleaner service boundaries and avoids creating monolithic god services.

#8about 4 minutes

Why graphical models are powerful tools for developers

Graphical models like BPMN serve as living documentation, facilitate communication between business and technical teams, and provide crucial operational visibility.

#9about 9 minutes

Q&A on Camunda, implementation trade-offs, and scale

The speaker answers audience questions about Camunda's open-source model, the trade-offs of adopting a workflow engine, and how the technology scales.