📄️ Configuration Overview
Prism uses a 6-layer configuration model that separates concerns between users, platform policies, and runtime implementation. This architecture ensures that application teams can declaratively specify their needs while the platform handles the operational complexity.
📄️ Namespace Configuration
This document describes how to configure a Prism namespace. Namespaces are the primary way to request data access patterns in Prism.
📄️ Backend Registry
The Backend Registry is Layer 4 of the configuration model and defines all available backends that Prism can use for data storage and messaging. Platform operators manage this registry to control where data is physically stored.
📄️ Slot Matching
Slot matching is the process by which Prism automatically binds pattern requirements to available backends. This is a key part of Layer 3 (Pattern Selection) and Layer 4 (Backend Binding) in the configuration model.
📄️ Cluster Administration
This document describes the Prism admin cluster configuration and operational controls. The admin cluster is the control plane that manages all namespace assignments, backend registrations, and cluster-wide policies.