Clean Architecture

Domain‑centric, dependency‑inversion style family emphasizing concentric layers (entities, use cases, interfaces) and the Dependency Rule.

Enabled By Platform Building Blocks

  • API Management: Securely exposes APIs, enforces policies, manages discoverability, and enables AI agent integration.
  • Identity & Access Management: Provides authentication, authorization, and federation for all services.

What it is

Best viewed as a family of domain‑centered, dependency‑inversion styles (closely related to Hexagonal and Onion). Many teams use it as a style; others apply its principles (boundaries, Dependency Rule, use‑case orientation) within other patterns.

Benefits

  • Framework-agnostic domain core
  • Improved testability and maintainability

Distinctions vs. Hexagonal

  • Clean organizes the code into rings (entities, use cases, interfaces)
  • Hexagonal organizes around ports/adapters for I/O
  • Teams often combine both; treat them as a family of domain‑centric styles