Commercial Real Estate Multi-Tenant Sharding Strategy Brief
Architect a scalable database sharding and isolation plan for commercial property leasing ledgers.
Use this template when architecting multi-tenant database partitioning for commercial REITs and property management systems. It provides clear guidance on shard key selection, regulatory isolation, and high-availability replication.
Role: Staff Database Reliability Engineer with deep expertise in multi-tenant commercial real estate ledger architectures.
Context
- Real Estate Portfolio: {{reit_portfolio_name}}
- Core Database Engine: {{core_database_engine}}
- Annual Ledger Transactions: {{annual_transaction_volume}}
- Sharding Key Candidate: {{partition_key_candidate}}
- Regulatory Isolation Level: {{reporting_isolation_requirement}}
- Disaster Recovery Target: {{disaster_recovery_rpo_minutes}} minutes RPO
Task
Deliver a database partitioning and sharding architectural brief for {{reit_portfolio_name}} that divides high-volume lease and payment ledgers while guaranteeing {{reporting_isolation_requirement}} compliance and meeting {{disaster_recovery_rpo_minutes}} RPO.
Method
- Profile skew and tenant transaction density across {{annual_transaction_volume}} records in {{core_database_engine}}.
- Evaluate routing efficiency using {{partition_key_candidate}} for point-in-time lease accounting queries.
- Define shard topology across physical compute instances to satisfy {{reporting_isolation_requirement}}.
- Formulate cross-shard reporting strategies for portfolio-wide consolidated financial rollups.
- Design shard rebalancing mechanics to handle large enterprise tenant portfolio acquisitions.
- Specify automated write-ahead log replication topologies to enforce the {{disaster_recovery_rpo_minutes}} minute RPO.
- Detail schema migration orchestration across distributed shards without leasing system downtime.
Constraints
- MUST enforce tenant isolation based on {{reporting_isolation_requirement}}.
- MUST NOT require distributed multi-shard ACID transactions for standard lease payment writes.
- Data replication topology must strictly guarantee {{disaster_recovery_rpo_minutes}} minutes maximum data loss.
- Sharding strategy must remain native to or proven on {{core_database_engine}}.
Output format
- Architectural Decision Summary (150-200 words)
- Shard Key Analysis & Routing Topology (diagram description and shard mapping table)
- Cross-Tenant Aggregation & Reporting Blueprint (bulleted design rules)
- Replication & Failover Strategy (step-by-step failover specification)
Self-review
- Check that partition boundaries prevent cross-shard locking during standard payment processing.
- Verify RPO calculations match the {{disaster_recovery_rpo_minutes}} minute constraint.
- Ensure all sections directly address the scaling needs of {{reit_portfolio_name}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.