The Salesforce platform is built on a multi-tenant architecture which means every Salesforce Org will be using the same computing and storage resources. For this reason, it’s imperative to understand governor limits in Salesforce.
Common Salesforce Limits
For the full list of limits, you can refer to this page.
Salesforce has the governor limits segregated by the transaction type. If it’s a Synchronous transaction then the limits are low while if it’s an Asynchronous transaction, limits are much higher.
| Description | Synchronous Limit | Async Limit |
| Total number of SOQL queries issued | 100 | 200 |
| Total number of records retrieved by SOQL queries | 50, 000 | 50, 000 |
| Total number of SOSL queries issued | 20 | 20 |
| Total number of records retrieved by a single SOSL query | 2000 | 2000 |
| Total number of DML statements issued | 150 | 150 |
| Maximum number of methods with the future annotation allowed per Apex invocation | 50 | 0 in batch and future contexts; 1 in queueable context
|
Conclusion
If we don’t put a cap on using the available resources, only one instance could use up all of the resources. Hence it won’t be available for other instances. It’s important to limit the use of resources effectively hence Salesforce has put limits on different operations that you can do.
Learn more about Salesforce with my related articles below!
Additional Resources
- Salesforce Dynamic Apex
- Salesforce Org-Wide Defaults
- Salesforce Developer: Apex Governor Limits
Cover Photo by Sigmund on Unsplash
Additional Photo by Grant Lemons on Unsplash
