The GemFire cache is the entry point to GemFire caching management. GemFire provides different APIs and XML configuration models to support the behaviors of different members.
The cache provides in-memory storage and management for your data.
You start your peer or server cache using a combination of XML declarations and API calls. Close the cache when you are done.
You have several options for client cache configuration. Start your client cache using a combination of XML declarations and API calls. Close the client cache when you are done.
When you create your cache in a secure system, you provide credentials to the connection process for authentication by already-running, secure members. Clients connect to secure servers. Peers are authenticated by secure locators or peer members.
In a secure system, you can create clients with multiple, secure connections to the servers from each client. The most common use case is a GemFire client embedded in an application server that supports data requests from many users. Each user may be authorized to access a subset of data on the servers. For example, customer users may be allowed to see and update only their own orders and shipments.
You can specify a callback application that is launched after the cache initialization.