Pivotal GemFire® v8.1

Pivotal GemFire Features Demonstrated in the Tutorial

Pivotal GemFire Features Demonstrated in the Tutorial

Use the tutorial to explore Pivotal GemFire's main features.

GemFire distributed system JVMs running GemFire form a distributed system. Each JVM is a GemFire peer member in the distributed system. A peer member connects to a GemFire distributed system and shares data with other peer members through data regions that are configured to distribute events among themselves.

To start a GemFire peer, you create a GemFire cache in each member. The cache manages the connectivity to other GemFire peers. Peers discover each other through multicast messaging or a TCP locator service.

Regions Regions are an abstraction on top of the distributed system. A region lets you store data in many JVMs in the system without regard to which peer's memory the data is stored in. Regions give you a map interface that transparently fetches your data from the appropriate cache. The Region class extends the java.util.Map interface, but it also supports querying and transactions.
Replicated regions A replicated region keeps a full copy of the region on each GemFire peer.
Partitioned regions Partitioned regions allow you to configure the number of copies of data in your distributed system. GemFire partitions your data so that each peer only stores a part of the region contents.
Client caching A GemFire distributed system is a mesh network, where all peers are connected directly to all other peers. GemFire also supports clients of the distributed system, which are connected only to a few of the peers in the distributed system. When peers are configured for client connections, they become servers to the clients as well as peers. Clients can have their own local cache of data from their server's distributed system, and they can update their local cache by registering with the server to receive changes to the data. GemFire also provides C++ and C# client APIs.
Shared-nothing persistence GemFire supports shared-nothing persistence, where each peer persists its partition of the data set to its local disk. GemFire persistence also allows you to maintain a configurable number of copies of your data on disk.
Cluster Configuration Service When you configure a GemFire cluster using gfsh, the Cluster Configuration Service uses locators to save and share a configuration to members of a cluster.