OpenSpaces Persistency Scenarios

Added by Shay Banon, last edited by Gilad David Maayan on May 19, 2008  (view change)
  Search Here
Searching XAP 6.0 Documentation

                                               
Summary: Different Space persistency scenarios and how they can be configured with OpenSpaces.

This page is specific to:
GigaSpaces 6.0

If you're interested in another version, click it below:
• GigaSpaces 6.5

Overview

GigaSpaces XAP 6.0 provides specific configuration to answer different types of user requirements, and OpenSpaces simplifies the configuration and setup of each configuration.

  • GigaSpaces Mirror Service (also known as Persistency as a Service, or PaaS) provides reliable asynchronous persistency, allowing you to asynchronously integrate your data stored in our In-Memory Data Grid (IMDG) with a backend database, significantly reducing performance overhead.
  • 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 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 changes made in the space (DataPersister).

For more details, refer to the Database Cache and Persistency section.


GigaSpaces 6.0 Documentation Contents (Current Page in Bold)

    Java

    C++

    .NET

    Middleware Capabilities

    Configuration and Management

Add GigaSpaces wiki search to your browser search engines!
(works on Firefox 2 and Internet Explorer 7)

Labels

 
(None)