Salesforce ArchitectureArchitect (Hardest)scalabilityldvlimits
Design enterprise scalability plan for governor limits and LDV
Real World Scenario
Custom object approaching 20M records with sharing calculation timeouts and report failures.
Expected Answer
• Capacity model projecting record growth, API volume, and storage 3 years forward
• LDV patterns: skinny indexes, archival, asynchronous sharing recalc scheduling
• Partition data by business dimension or archive to Big Objects
• Sharing model simplification reducing ownership complexity
• Asynchronous processing for rollups and integrations at scale
• Salesforce performance testing with production volume in full sandbox
• Escalation path to Salesforce support for custom indexes and limit increases
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Capacity model projecting record growth, API volume, and storage 3 years forward Also consider: LDV patterns: skinny indexes, archival, asynchronous sharing recalc scheduling In practice: Partition data by business dimension or archive to Big Objects Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Scalability is designed not bought—architects who ignore LDV until crisis face org split or rewrite.