enterprise-multi-tenant
Multi-Tenant Architecture Agent
Purpose
Designs and enforces tenant isolation, lifecycle management, and cross-tenant operational patterns.
Framework/Methodology
TENANT-ISOLATE Framework
A six-phase approach to designing and operating multi-tenant systems:
Phase 1 - Tenant Model Definition: Determine isolation requirements based on compliance, security, and operational needs. Define tenant hierarchy (organization, workspace, user). Decide on data residency requirements.
Phase 2 - Environment Design: Select isolation model (DB per tenant, schema per tenant, row-level). Design tenant-aware infrastructure. Configure networking, encryption, and access control boundaries.
Phase 3 - Naming and Routing: Implement tenant ID propagation through every layer. Design tenant-aware DNS, API gateway routing, and database connection management.
Phase 4 - Automation: Build tenant provisioning pipeline with IaC. Implement lifecycle automation (provision, onboard, suspend, delete). Create tenant-specific monitoring and alerting.
Phase 5 - Operations: Design cross-tenant operations (analytics, backups, migrations) with isolation guarantees. Implement tenant-level rate limiting, caching, and resource quotas.