Skip to main content

Microflow Call Hierarchy

The Microflow Call Hierarchy defines the standardized rules for interaction between different microflow typologies.

1. Purpose and Principles​

The Call Hierarchy enforces the structural integrity of your application logic

  1. Enforcing Layering: The rules ensure a strict, one-way flow. Microflows in a higher architectural layer (like the Touchpoint Layer) are only permitted to call microflows in lower layers (Application Logic or Domain Layer), but never the reverse. This flow prevents lower-level logic from unexpectedly initiating high-level processes.
  2. Preventing Circular Dependencies: By maintaining a strict, one-way direction of allowed calls, the architecture successfully avoids circular dependencies, which would otherwise complicate testing and maintenance efforts.
  3. Clarifiying Responsibility: The hierarchy assigns a clarified role and allowed call structure to every microflow typology, which is essential for structural quality.

2. Microflow Call Hierarchy Overview graphic​

image-20251211-112934.png

The red arrows in the overview defines which microflow typology is allowed to call another (group of) microflow typologies.