> Markdown version of [/videos/100144-solving-architectural-entropy-with-runnable-diagrams?t=847](https://www.wearedevelopers.com/videos/100144-solving-architectural-entropy-with-runnable-diagrams?t=847). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Solving Architectural Entropy With Runnable Diagrams

Are your microservices locally correct but globally chaotic? Learn how runnable BPMN diagrams tame architectural entropy, turning static whiteboards into an executable orchestration layer.

- **Speakers:** [Mourjo Sen](https://www.wearedevelopers.com/@mourjo-sen)
- **Event:** World Congress 2026 Europe
- **Published:** July 9, 2026
- **Duration:** 31:38
- **URL:** https://www.wearedevelopers.com/videos/100144-solving-architectural-entropy-with-runnable-diagrams

## Summary

Software architecture inherently degrades over time, a phenomenon known as architectural entropy. While the shift from monolithic structures to microservices successfully compartmentalized complex domain logic, it inadvertently fragmented our end-to-end understanding of software. Engineering teams now face "macroscopic entropy," where a system acts as a haphazard web of crisscrossing point-to-point interactions. This fragmentation leads to a heavy coordination overhead within individual services and obscures the broader business intent, creating frustrating scenarios where a microservice is locally correct but the system is globally incorrect. Resolving this lack of clarity requires systems thinking—specifically, shifting focus from merely analyzing isolated components to synthesizing how those specialized parts act together cooperatively. To achieve this synthesis, developers must embrace process-domain duality by adopting an explicit "language for the system." Human beings utilize an evolutionary superpower called pre-attentive processing, enabling us to instantly comprehend visual patterns without deep cognitive effort. This is exactly why engineering teams rely so heavily on whiteboard diagrams; however, static documentation quickly decays into outdated relics of the past. The solution lies in transitioning to runnable, executable diagrams using Business Process Model and Notation (BPMN). By maintaining the visual diagram as the actual operational definition of state and flow—which the system compiles and executes via standard XML—developers bridge the gap between human-centric business logic and machine-level execution. Implementing this explicit visual orchestration layer prevents domain-driven services from drifting from their original design intent. With a dedicated process language, intricate coordination workflows—such as inserting a "pay later" delay, handling system-wide failures, or managing asynchronous third-party webhooks—are untangled from deep within individual microservices and promoted back to an explicit system layer. The domain services remain highly cohesive and specialized, while the runnable diagram dictates the execution sequence. In an increasingly complex, AI-led software era, this executable transparency tames systemic randomness, making distributed systems significantly easier to reason about, debug, and safely evolve.

**Keywords:** architectural entropy, runnable diagrams, business process model and notation, microservice coordination overhead, macroscopic system fragmentation, process-domain duality, pre-attentive visual processing, visual orchestration layer, distributed system debugging, systems thinking synthesis, domain-driven design constraints, executable system diagrams, global workflow correctness, async webhook management, human-centric system design

## Chapters

1. **Identifying root causes within distributed microservice architectures** (01:01) — How debugging complex systems reveals the gap between local microservice correctness and unpredictable global behavior.
1. **Macroscopic entropy and the compounding complexity of ecosystems** (05:01) — Evolving systems create inherently complex interaction meshes that degrade architectural intent into chaotic macroscopic entropy.
1. **Understanding the cost of coordination in fragmented systems** (07:57) — Modularization unintentionally scatters system knowledge, replacing core feature logic with convoluted microservice coordination and defensive programming.
1. **System thinking and the necessity of architectural synthesis** (14:07) — Moving beyond system analysis requires a process-level language that synthesizes isolated domain tasks into unified user outcomes.
1. **Leveraging pre-attentive processing for visual system languages** (17:14) — Aligning architectural definitions with innate human visual processing prevents structural degradation and renders documentation executable.
1. **Modeling conceptual workflows across distinct domain application boundaries** (19:24) — Tracking contextual state across dedicated microservices creates executable pathways that decouple processes from implicit internal logic.
1. **Adapting end-to-end architectures with visual coordination modeling** (23:41) — Explicit diagrammatic execution minimizes the cognitive burden required to adapt system features and handle cross-domain operation failures.
1. **Bridging domain code and human comprehension with executable schemas** (27:53) — Executing business process models as standardized markup bridges semantic gaps between localized domain implementations and systemic behavior.

## Related Moments

- [Aligning agile teams and stakeholders using architecture diagrams](https://www.wearedevelopers.com/videos/379-communicate-efficiently-with-software-architecture-diagrams) (from "Communicate efficiently with Software Architecture Diagrams")
- [Redesigning complex architectures by eliminating redundant diagram connections](https://www.wearedevelopers.com/videos/379-communicate-efficiently-with-software-architecture-diagrams) (from "Communicate efficiently with Software Architecture Diagrams")
- [Balancing architectural complexity with practical business value](https://www.wearedevelopers.com/videos/1052-autonomous-microservices-with-event-driven-architecture) (from "Autonomous microservices with event-driven architecture")
- [Using understanding-oriented documentation to explain integrations and software architecture](https://www.wearedevelopers.com/videos/798-continuous-documentation-for-your-code) (from "Continuous Documentation for Your Code")
- [Moving architectural complexity instead of genuinely reducing it](https://www.wearedevelopers.com/videos/2085-software-development-is-not-getting-easier) (from "Software Development is (not) getting easier")
- [Building engineering cultures that support long-term software architecture](https://www.wearedevelopers.com/videos/1998-from-code-to-culture-why-leadership-determines-software-quality) (from "From Code to Culture: Why Leadership Determines Software Quality")

## Related Articles

- [Why Event-Driven Architecture Isn’t About Speed (and When You Actually Need It)](https://www.wearedevelopers.com/magazine/745-why-event-driven-architecture-isn-t-about-speed-and-when-you-actually-need-it)
- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)
- [How to Avoid Over-Engineering](https://www.wearedevelopers.com/magazine/546-how-to-avoid-over-engineering)
- [Why You Shouldn’t Build a Microservice Architecture](https://www.wearedevelopers.com/magazine/118-why-you-shouldn-t-build-a-microservice-architecture)

## Related Jobs

- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Software Solution Architekt](https://www.wearedevelopers.com/jobs/ext/1458613-software-solution-architekt) at **BWI GmbH**
- [Senior Software Engineer, Enterprise Products](https://www.wearedevelopers.com/jobs/ext/1841248-senior-software-engineer-enterprise-products) at **GitHub**
- [Principal Software Engineer, Database Infrastructure](https://www.wearedevelopers.com/jobs/ext/1465908-principal-software-engineer-database-infrastructure) at **GitHub**
- [Senior Cloud Software Architect (all genders welcome) for our Intelligent Service Operations Hub](https://www.wearedevelopers.com/jobs/ext/1284556-senior-cloud-software-architect-all-genders-welcome-for-our-intelligent-service-operations-hub) at **Rosenxt Group**
- [Enterprise Architect - ERP](https://www.wearedevelopers.com/jobs/ext/1965168-enterprise-architect-erp) at **ZEISS Group**