The Invisible Problem in BPM Business Process Management (BPM) promises transparency. You model your processes, automate tasks, and track execution, but some critical parts remain invisible: User activities and external system calls are black boxes. You see when a task starts and ends, but not what happens inside. This lack of visibility creates blind spots. Is the user struggling with a poorly designed form? Is the third-party system slow? You can’t tell. Without insights into these (black) b...

The Disconnect Between Theory and Practice In domain-centric architectures like Clean, Onion, or Hexagonal Architecture combined with Domain-Driven Design (DDD), the business domain model should drive everything. The domain layer is supposed to be the heart of the system — independent of frameworks, databases, or APIs, and technology-agnostic. Yet, in customer projects, new features are often initiated by designing the database schema or REST API first. I repeatedly see colleagues, despite the...

Introduction: Addressing the Migration Challenge If your Camunda 7 codebase looks like the following, migrating to Camunda 8 will feel like a nightmare.. Framework calls are spread across controllers, services, and even repositories, meaning you’ll have to touch every layer during migration. A time-consuming, error-prone, and stressful process. Framework usage spread across all layers: a migration nightmare The root cause is tight coupling between your business logic and the process engine....