Summary: GigaSpaces's persistency approach consists of several paradigms for data persistency, according to the application needs. This section gives a basic overview of each paradigm.

Overview

The space can load data from external data sources, store data into external data sources, and persist data into a relational data source or an indexed file.
The space can also be used as a Hibernate or JDO second level cache.

Persistency Architecture

GigaSpaces provides several persistency models, which allow different modes of interaction with a database.

GigaSpaces exposes several interfaces and persistency implementations. Each provides a different persistency model suitable for a different scenario. Two models are described below:

  • External Data Source
  • JDBC Storage Adapter

External Data Source

GigaSpaces different External Data Source interfaces (with a built-in implementation using Hibernate) can be used to store data in an existing data source and in the space. Data is loaded from the data source during space initialization (DataProvider), and from then onwards the application works with the space directly. Meanwhile, the data source is constantly updated with all the changes made in the space (DataPersister).

The External Data Source support following options:

  • Reliable async persistency - see Async Persistency - Mirror

  • Central and distributed direct persistency - see Direct Persistency

JDBC Storage Adapter

The GigaSpaces JDBC Storage Adapter supports implicit data recovery from the database when a space is started, stores Entry meta data, and persists a redo log. The data source and space are constantly synchronized with each other.

GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence