Abstract: A system and method can support recovery of persisted data from persistent storage of a distributed data grid, and provide persistent store versioning and integrity. A coordinator in the distributed data grid can receive a plurality of identifiers from one or more members of the distributed data grid, wherein each said identifier is associated with a persisted partition in a persistent storage for the distributed data grid. Then, the coordinator can select an identifier for each partition, wherein each selected identifier is associated with a most recent valid version of a partition. Furthermore, the coordinator can determine an active member in the distributed data grid that is responsible for recovering said partition from a persisted partition associated with the selected identifier.

Abstract: A system and method can support persistence in a distributed data grid. A plurality of members in the distributed data grid can persist a plurality of partitions associated with one or more cache services in persistent storage. Furthermore, a coordinator, which may be a member in the distributed data grid, can synchronize a view of partition ownership among the plurality of members in the distributed data grid, and form a distributed consensus on which partition can be recovered from which member in the distributed data grid.

Abstract: A system and method can support recovery of persisted data from persistent storage of a distributed data grid, and provide persistent store versioning and integrity. A coordinator in the distributed data grid can receive a plurality of identifiers from one or more members of the distributed data grid, wherein each said identifier is associated with a persisted partition in a persistent storage for the distributed data grid. Then, the coordinator can select an identifier for each partition, wherein each selected identifier is associated with a most recent valid version of a partition. Furthermore, the coordinator can determine an active member in the distributed data grid that is responsible for recovering said partition from a persisted partition associated with the selected identifier.

Abstract: A system and method can support persistence in a distributed data grid, such as persistent store versioning and integrity. A resolver in the distributed data grid can receive a plurality of identifiers from one or more members of the distributed data grid, wherein each said identifier is associated with a persisted partition in a persistent storage for the distributed data grid. Then, the resolver can select an identifier for each partition, wherein each selected identifier is associated with a most recent valid version of a partition. Furthermore, the resolver can determine a member in the distributed data grid that is responsible for recovering said partition from a persisted partition associated with the selected identifier.

Abstract: A system and method can support data interoperability in a distributed data grid. The system can provide an acceptor in the distributed data grid, wherein the acceptor is associated with a cache that is based on the distributed data grid. Furthermore, the acceptor can receive incoming data from a first client, which can be a non-native client that is associated with a client application. Additionally, the system allows a second client, which can be a native client associated with the distributed cache, to share the received incoming data with the first client.

Abstract: A system and method can support persistence in a distributed data grid, such as persistent store versioning and integrity. A resolver in the distributed data grid can receive a plurality of identifiers from one or more members of the distributed data grid, wherein each said identifier is associated with a persisted partition in a persistent storage for the distributed data grid. Then, the resolver can select an identifier for each partition, wherein each selected identifier is associated with a most recent valid version of a partition. Furthermore, the resolver can determine a member in the distributed data grid that is responsible for recovering said partition from a persisted partition associated with the selected identifier.

Abstract: A system and method can support persistence in a distributed data grid, such as providing a persistent snapshot of a running system. The system allows one or more cache services to run on a plurality of cluster members in the distributed data grid. Furthermore, the system can collect a catalogue of state information associated with said one or more cache services from the plurality of cluster members in the distributed data grid, and create a snapshot for said one or more cache services running on the distributed data grid.

Abstract: A system and method can support persistence in a distributed data grid. A plurality of members in the distributed data grid can persist a plurality of partitions associated with one or more cache services in persistent storage. Furthermore, a coordinator, which may be a member in the distributed data grid, can synchronize a view of partition ownership among the plurality of members in the distributed data grid, and form a distributed consensus on which partition can be recovered from which member in the distributed data grid.

Abstract: A system and method can support data interoperability in a distributed data grid. The system can provide an acceptor in the distributed data grid, wherein the acceptor is associated with a cache that is based on the distributed data grid. Furthermore, the acceptor can receive incoming data from a first client, which can be a non-native client that is associated with a client application. Additionally, the system allows a second client, which can be a native client associated with the distributed cache, to share the received incoming data with the first client.