Cross-cutting Concepts

Concepts that apply across the whole application rather than to a single building block are described in the following pages:

Error Handling — how errors are surfaced and handled.
Logging — logging and metrics conventions (Application Insights).
Authentication — identity, roles, and access via EnBW IAM.
Domain Model — the business objects KBP works with, how they relate, their key states, and the system of record behind each.
Contract Loading — the deprecated background contract preload with its Redis cache, its consumers, and the on-demand target architecture.
Feature Access Management — how features.json, the API entity tree and the frontend user-action policies decide what the frontend shows, calls and navigates to, and where backend and frontend are coupled.

Feature-based access management, which is also cross-cutting, is described in the Solution Strategy.