Apex Developer Guide

Getting Started
Writing Apex
Ways to Invoke Apex
Invoking Apex
Apex Transactions and Governor Limits
Using Salesforce Features with Apex
Actions
Approval Processing
Authentication
Chatter Answers and Ideas
Chatter in Apex
Moderate Chatter Private Messages with Triggers
Moderate Feed Items with Triggers
Communities
Email
Platform Cache
Platform Cache Features
Platform Cache Considerations
Platform Cache Limits
Platform Cache Partitions
Platform Cache Internals
Store and Retrieve Values from the Session Cache
Use a Visualforce Global Variable for the Session Cache
Store and Retrieve Values from the Org Cache
Platform Cache Best Practices
Salesforce Knowledge
Salesforce Connect
Salesforce Reports and Dashboards API via Apex
Force.com Sites
Support Classes
Territory Management 2.0
Visual Workflow
Integration and Apex Utilities
Finishing Touches
Reference
Appendices
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Platform Cache Considerations

Review these considerations when working with Platform Cache.
  • Cache isn’t persisted. There’s no guarantee against data loss.
  • Data in the cache isn’t encrypted.
  • The cache doesn’t support concurrent operations. Multiple, simultaneous user requests (for example, from different browser windows) can lead to stale or overwritten data in the cache.
  • Cache misses can happen. We recommend constructing your code to consider a case where previously cached items aren’t found.
  • Session cache doesn’t support asynchronous Apex. For example, you can’t use future methods or batch Apex with session cache.
  • Session cache doesn’t support Anonymous Apex blocks. For example, if you execute Anonymous Apex in the Developer Console, you get an error.
  • Cache operations made using the put and remove methods in the Cache Namespace aren’t supported in constructors of Visualforce controllers.
  • Partitions must adhere to the limits within Salesforce.
  • The session cache can store values up to eight hours. The org cache can store values up to 48 hours.