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.

GigaSpaces XAP 6.0 provides specific configuration to answer five main types of user requirements.

Choose the scenario that best suits your requirements from the list below:

You want your data to be saved to the database asynchronously, acquiring high performance You don't want to risk data loss		Highly recommended – Persistency as a Service Learn how failure scenarios are handled when working with PaaS.
You want all your data to be saved to disk You don't want to deal with how it is saved to disk or what type of database it is saved in		Durability
You want to integrate your existing database with your memory You want to work directly with the memory, without being aware of the database		External data source integration
You are dealing with large amounts of data You need to store more data than your database is capable of holding.		Capacity
You are working with remote applications communicating over a problematic network You want to assure that messages won't be lost in the event of a long failure period		Durable/reliable messaging

For GigaSpaces' main database cache and persistency concepts, see the Database Cache and Persistency Overview section.

Read the list of known issues in GigaSpaces 6.0 or in GigaSpaces 6.0.1.

Section Contents

• Database Cache and Persistency Overview — GigaSpaces main database cache and persistency concepts: JDBC Storage Adapter; External Data Source; Hibernate; Mirror Service; indexed file.
• Database Cache and Persistency Scenarios
• Data Sources Integration
  • GigaSpaces for Hibernate ORM Users — Using GigaSpaces Community Edition as a Hibernate cache provider; creating a Hibernate-integrated Data Grid with your existing ORM.
  • Mirror Service — A Mirror is an asynchronous replica of data sent by spaces in a cluster. This data is asynchronously batched into the Mirror Service, which interacts with its configured data-source.
  • Read-Through and Write-Through — About space write-through and read-through operations and how to configure them by implementing the External Data Source interface, or by using a standard Hibernate interface.
• Disk Persistency for Space Data — Achieving persistency for space data.
  • Persistency Into Indexed File — Using the command line or GigaSpaces Browser to create a persistent space backed up by an indexed file.
  • Persistency into RDBMS — Persistency configuration files; creating persistent space using JDBC; configuring JDBC connection pool; configuring DB2 7.2.
  • Persistent Space Schema — A configuration schema that defines how a space should persist its in-memory data to disk-based storage (either RDBMS or indexed file).
  • Transient Entries — How to specify that some objects in a persistent space should not be saved to persistent storage.