Just like Single-tenant, Multi-tenant applications can cache contents to improve performance at runtime. Each tenant has its own cache for storing tenant-specific data. Data shared among tenants, i.e., Single-tenant is cached in a centralized way.

Cache Invalidation

To force the evaluation of cached content on the next usage, OutSystems Platform provides cache invalidation with the following System actions:


Allows invalidating the cache either at application module level or for a specific Tenant of the module.

If only the module is specified, the cache is invalidated for the module and all its tenants.

Example 1

In the OnLineShop application, currency exchange rates are shared among all tenants and are updated at the end of the day. When that happens, the cache must be invalidated for all tenants.

By specifying the module and the tenant when using the EspaceInvalidateCache, the cache is invalidated for that specific tenant of the module.

Example 2

In the OnlineShop application, each tenant has its own product catalog and caching is performed per tenant. When an end-user uploads new products to the catalog, the corresponding tenant cache must be invalidated. By invalidating cache for a specific tenant, you avoid the overhead of invalidating the cache for all tenants.


Allows invalidating cache of a tenant across all modules.

Use the EspaceInvalidateCache instead to constrain the invalidation of cached data for a single modules, thus reducing the invalidation impact.

See Also

About Multi-Tenancy | About Caching Contents | Invalidating the Cache