Summary: This section explains how to develop applications on XAP using the main modules and APIs
Section Contents
The In-Memory Data Grid — Explains the concepts of the GigaSpaces in-memory data grid (the Space), how to access it, and how to configure advanced capabilities, such as persistency, eviction, etc.
Space Topologies — Explains the topologies and clustering mechanism of the GigaSpaces in-memory data grid (the Space)
Modeling and Accessing Your Data — This section will teach you how to design your data for distributing on the data grid and about the various APIs for accessing you data.
Caching Scenarios — GigaSpaces IMDG supports three different caching mechanisms: In-line Cache, Side Cache and Client Side Cache.
FIFO Support — How to get entries in the same order in which they were written to the space.
Transaction Management — OpenSpaces provides an implementation of Spring's PlatformTransactionManager enabling you to use XAP's distributed transaction manager.
Other Data Access APIs — This section review the different APIs one can use to access the space
JDBC Driver — GigaSpaces allows applications to connect to the IMDG using a JDBC driver. A GigaSpaces JDBC driver accepts SQL statements, translates them to space operations, and returns standard result sets.
Map API — Using GigaSpaces as a distributed cache. Interacting with the space using the Hashtable API.
Memcached API — memcached support on top of the space.
Services on Top of the Data Grid — This page provides an overview of the various service components that are available on top of the GigSpaces DataGrid framework. It also outlines when to choose each one of them
Reloading Business Logic — Service reloading allows you to reload business logic without bringing down the Processing Unit.
Task Execution over the Space — Task executors allow you to easily execute grid-wide tasks on the space using the GigaSpace API.
Aggregators — Aggregating Data with GigaSpaces In-Memory Data-Grid using built-in aggregators.
Dynamic Language Tasks — GigaSpaces supports the execution of tasks using scripting languages like JavaScipt and Groovy. These can be defined dynamically using the JDK 1.6 dynamic languages support. The dynamic language support is based on the ordinary task executors and OpenSpaces remoting support.
Space Based Remoting — Remoting allows you to use remote invocations of POJO services, with the space as the transport layer.
Executor Based Remoting — Executor Remoting allows you to use remote invocations of POJO services, with the space as the transport layer using OpenSpaces Executors.
Event Driven Remoting — Event Driven Remoting allows you to use remote invocations of POJO services, with the space as the transport layer using a polling container on the space side to process the invocations
Event Processing — This section will guide you through event processing APIs and configuration on top of the space
Archive Container — Allows archiving of space objects to an external persistency service.
Notify Container — The notify event container uses the space inherited support for notifications, using a GigaSpaces unified event session API.
Polling Container — Allows you to perform polling receive operations against the space.
Data Event Listener — Describe the common Space Data Event Listener and its different adapters.
Event Exception Handler — Describe the common Exception Event Listener and its different adapters.
JMS API Support — GigaSpaces allows applications to use the space as a messaging hub. Applications use JMS to create topics and queues as usual; these are transparently translated into space Entries.