Understanding Salesforce Governor Limits: The Architecture Handbook
The Systems Architect's Survival Guide to Multi-Tenant Concurrency, Heap Management, and Transactional CPU Budgets.
Figure 9: Synchronous vs asynchronous governor limit allocations.
Key Findings & Architecture Notes
- •Governor limits are enforced per transaction; an unhandled LimitException immediately rolls back all uncommitted DML in that execution context.
- •Synchronous transactions permit 100 SOQL queries, 150 DML statements, 10,000ms CPU time, and 6MB heap size.
- •Asynchronous transactions (Queueable, Batch, @future) double the limits to 200 SOQL queries, 60,000ms CPU time, and 12MB heap size.
The Multi-Tenant Contract
Governor limits ensure cloud multi-tenancy remains secure, predictable, and economically viable across shared data center clusters.
Subject Index
About Marcus Vance
Principal Salesforce Technical Architect & Venture Contributor • London Bureau
Marcus Vance is a certified Salesforce Technical Architect and systems engineer with over 12 years of experience designing multi-cloud enterprise topologies, high-volume Apex integrations, and CRM infrastructure across European banking and SaaS enterprises.