Summary: Space Persistency provides advanced persistency capabilities for the space architecture.
OverviewThe Space Persistency is made of two components, A space data source & a space synchronization endpoint. The two components mentioned above are in charge of the following activities:
GigaSpaces Space Persistency provides the SpaceDataSource and SpaceSynchronizationEndpoint classes which can be extended and then used to load data and store data into an existing data source. Data is loaded from the data source during space initialization (SpaceDataSource), and from then onwards the application works with the space directly. Meanwhile, the space persisting the changes made in the space via a SpaceSynchronizationEndpoint implementation. Persistency can be configured to run in Synchronous or Asynchronous mode:
Space Persistency APIThe Space Persistency API contains two abstract classes one should extend in order to customize the space persistency functionality.
For detailed API information see Space Data Source API and Space Synchronization Endpoint API. RDBMS Space PersistencyGigaSpaces comes with a built-in implementation of SpaceDataSource and SpaceSynchronizationEndpoint called Hibernate Space Persistency. See Space Persistency Initial Load to allow the space to pre-load its data. You can also use splitter data source SpaceDataSourceSplitter that allows you to split data sources according to entry type. NoSQL DB Space PersistencyThe Cassandra Space Persistency Solution allows applications to push the long term data into Cassandra database in an asynchronous manner without impacting the application response time and also load data from the Cassandra database once the GigaSpaces IMDG is started or in a lazy manner once there is a cache miss when reading data from GigaSpaces IMDG. The GigaSpaces Cassandra Space Peristency Solution leverages the Cassandra CQL, Cassandra JDBC Driver and the Cassandra Hector Library. Every application's write or take operation against the IMDG is delegated into the Mirror service that is using the Cassandra Mirror implementation to push the changes into the Cassandra database. Advanced Information & Operations
|
![]() |
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence |