Hosting hundreds of independent websites on distinct domains typically leads to fragmented server clusters, duplicate dependencies, and high operational overhead. A unified **Multi-Tenant CMS Engine** resolves incoming `Host` headers in $O(1)$ memory time, dynamically loading the tenant's bespoke React views, stylesheet tokens, and database collections within a single shared Node.js runtime.
1. Request Ingress & Tenant Resolution Pipeline
| Pipeline Stage | Processing Layer | Operational Responsibility |
|---|---|---|
| 1. Ingress & TLS | Nginx Reverse Proxy (:443) | Wildcard SSL/TLS termination, HTTP/2 multiplexing, and Gzip/Brotli compression. |
| 2. Host Header Normalization | Express Root Middleware | Strips port suffixes, lowercases strings, and matches canonical 301 redirect tables. |
| 3. Tenant Context Lookup | NavigationService (In-Memory) | Retrieves tenant settings, navigation hierarchies, and sidebar items from RAM. |
| 4. MVC View Dispatch | Domain Switchboard Router | Executes tenant-specific controller or delegates to modular React MVC views. |