The multi-tenant architecture within Salesforce presents developers with several considerations that must be taken when they are writing code for the platform.
The design of the multi-tenant system prevents any data from being accessed outside it’s intended org, which means additional security considerations (outside the usual ones) aren’t required, simply because of the multi-tenant nature.
The platform resources are, however, shared and all orgs within instances are using the same CPUs and memory for all of their Apex operations and it is here where the considerations must be made. These considerations are to ensure that Apex code is performant as any code deemed to be using excessive resources (as defined by the governor limits) will be terminated to prevent it from monopolising resources and causing detrimental effects on other tenants.
References:
The multi-tenant architecture within Salesforce presents developers with several considerations that must be taken when they are writing code for the platform.
The design of the multi-tenant system prevents any data from being accessed outside it’s intended org, which means additional security considerations (outside the usual ones) aren’t required, simply because of the multi-tenant nature.
The platform resources are, however, shared and all orgs within instances are using the same CPUs and memory for all of their Apex operations and it is here where the considerations must be made. These considerations are to ensure that Apex code is performant as any code deemed to be using excessive resources (as defined by the governor limits) will be terminated to prevent it from monopolising resources and causing detrimental effects on other tenants.
References: