Cache Lightning Platform Data - Salesforce Developer Guide

Using the Platform Cache can enable Salesforce applications to run faster because they will store reusable data in memory. Salesforce applications can easily and quickly access these available data, which removes the necessity to replicate calculations and requests to the database on successive transactions in Salesforce org.

To use Platform Cache, first founded split-up (partition)s using the Platform Cache split-up (partition) tool in Setup. Once you have got the split-up (partition)s, you will be able to add, access, and remove data from them using the Platform Cache Apex API.

Use Platform Cache split-up (partition)s to spice up the performance of our applications. split-up (partition) allows us to disperse cache space within the way that works best for our Salesforce applications. Cache data to delegate separations ensures that it is not exaggerated by other applications or less necessary data.

Don't forget to check out: Illustrations in Salesforce Lightning Experience

In Salesforce to access the split-up (partition) tool in Setup, enter Platform Cache within the short Find box, then select Platform Cache.

Use the Platform Cache split-up (partition) tool to:
Request trial cache.
Create, edit, or delete cache split-up (partitions).
Allocate the session cache and org cache capacities of each split-up (partition) to balance performance across apps.
View a snapshot of the organization’s current cache capacity, breakdown, and split-up (partition) allocations (in KB or MB).
View details about each split-up (partition).
Make any split-up (partition) the default split-up (partition).

To use Platform Cache, create a minimum of one split-up (partition). Each division has one session cache and one organization cache segment and you will be ready to allot distinct volume to each segment. The Session cache could also be customary to store information for every single user session, and organization cache is for data that any users in an organization can access. You will distribute your organization’s cache space across any number of split-up (partitions). Session and org cache allocations are often zero, or five or greater, which they have to be whole numbers. The Total of all split-up (partition) allotment, including the default split-up (partition), equals the Platform Cache total allotment. the full allotted capacity of all cache segments must be but or up to the organization’s overall capacity.

You can define any split-up (partition) because the default split-up (partition), but you may be able to have only one default split-up (partition). When a split-up (partition) has no allocation, cache operations (such as get and put) do not seem to be invoked, and no error is returned.

Capacity calculations occur every 5 minutes by default to make sure you are seeing the latest capacity and allocation, then, click Recalculate. You can Request a Platform Cache Trial.

Check out another amazing blog by Mohit here: Back Up Metadata to Secure and Restore Your Customizations | Salesforce Guide

To test performance improvements by using Platform Cache in your own organization, you will request a trial cache for your production organization. Enterprise org, Unlimited org, and Performance org, editions org include some cache, but adding more cache often provides greater performance. When your trial request is approved, you may allocate the capacity to split-up (partitions) and experiment with using the cache for various scenarios. Testing the cache on an attempt basis helps you to form an informed decision about whether to shop for the cache.