DOCSEARCHbyAlgolia
Submit Docs

GigaSpaces Documentation

website·Indexed 40 days ago

https://docs.gigaspaces.com/latest/landing.html

Documentation for GigaSpaces, featuring XAP (In-Memory Data Grid) and SpaceDeck (Smart DIH). It covers data grid basics, distributed processing, the Document API, and integration with Spring Data and the Drools Rule Engine. Includes guides on WAN Gateway replication, Processing Units, and the REST Manager API.

Tokens
662.2K
Snippets
2.4K
Records
4.1K
Agent score
62%

What's inside GigaSpaces

  1. Overview of GigaSpaces XAP Data Access APIs

    GigaSpaces XAP supports multiple common interfaces for accessing data, allowing developers to choose the most appropriate API for their specific use case while operating on the same underlying data. Supported data access APIs include:

    • JPA (Java Persistence API)
    • Document API
    • SQL
    • JDBC (Java Database Connectivity)
    • Memcached
    • Spring Data
    • Native POJO-based API

  2. Overview of DB2 Delta Server synchronization

    The DB2 Delta Server pattern is used when legacy applications or backend systems update a DB2 database directly (bypassing the data grid). The Delta Server listens for notifications of these database activities and delegates the updates to the GigaSpaces data grid, ensuring the IMDG remains consistent with the system of record.

  3. Overview of Space-Based Remoting

    Space-Based Remoting allows for remote invocations of Plain Old Java Object (POJO) services using the GigaSpaces Space as the transport layer. By using the Space as the underlying protocol, remoting gains several architectural benefits:

    • High Availability: Remote invocations inherit the high availability of the Space's cluster topology.
    • Automatic Load Balancing: In partitioned cluster topologies, invocations are automatically routed to the correct partition via the routing handler.
    • Performance: Uses fast internal OpenSpaces objects for efficient serialization and network transport.
    • Asynchronous Execution: Native support for asynchronous invocations (using Futures), with synchronous support built on top of it for higher throughput.

  4. Overview of XAP Hot Deploy Utility

    The Hot Deploy Utility enables the refresh of business logic running as a Processing Unit (PU) through a rolling upgrade. This process ensures no system downtime or data loss. The tool achieves this by placing new PU code in the Grid Service Manager (GSM) deploy folder and sequentially restarting each PU instance.

  5. Overview of GigaSpaces Metrics Framework

    GigaSpaces provides a framework to collect and report metrics from a distributed runtime environment into a metric repository. This allows for the analysis of system behavior and trend identification. The framework supports predefined metrics bundled with the system as well as custom user-defined metrics. Supported reporting destinations include InfluxDB, CA APM Introscope, or custom-developed metrics reporters.

  6. Overview of Spring Security authentication and authorization

    Spring Security (formerly Acegi Security) provides a framework for handling authentication and authorization. It uses a namespace that allows security configuration via XML. Key built-in authentication providers include:

    • DaoAuthenticationProvider: Retrieves user information from a database.
    • LdapAuthenticationProvider: Authenticates against an LDAP server.
    • JaasAuthenticationProvider: Retrieves user information from a JAAS login configuration.

    Note: Password Encoding must be applied to secure credentials.

  7. Overview of LRMI Network Monitoring

    LRMI monitoring allows developers and administrators to track which clients are invoking specific methods on services (e.g., read/write requests to a space). This is used to identify high-load remote proxies, investigate version conflicts, and monitor both inbound and outbound communication for a specific JVM. Note: This feature is available in licensed editions (Premium and above) and is not part of the open-source edition.

  8. Overview of GigaSpaces Space Filters

    Space Filters are interceptors within the GigaSpaces Space engine that allow developers to implement user-defined logic or integrate external systems when space operations are executed. Space Filters are only supported for embedded spaces. They can be configured using the UrlSpaceFactoryBean via a FilterProvider, which manages the ISpaceFilter implementation and its characteristics, such as priority and whether it is active during backup.

  9. Overview of GigaSpaces Standalone Mode

    Standalone mode allows GigaSpaces products to be run using the open source and GigaSpaces editions for initial evaluation, development, and testing. In this mode, the system acts as a simple cluster manager with limited functionality and administration capabilities compared to full editions.

  10. Overview of MemoryXtend for Disk (SSD/HDD)

    MemoryXtend for Disk provides high-speed persistence for GigaSpaces by tiering data to external storage (SSD, HDD, or All-Flash-Arrays) using a RocksDB-based blobstore. This architecture allows the system to handle operational workloads larger than the available JVM heap while keeping all indexes in RAM for performance.

    Architecture Components:

    • Space Partition Instance: A JVM heap acting as an LRU cache. It stores indexes, metadata, transactions, replication redo logs, leases, and statistics.
    • Blobstore: A persistent key/value store based on a log-structured merge tree. It consists of:
      • MemTable: Off-heap RAM for incoming writes; flushed to SST files when full.
      • Log (WAL): A write-ahead log used to recover the store to a consistent state after failure.
      • SST Files: Disk-based structures optimized for high throughput and sequential I/O.
      • Built-in Cache: Part of the Space partition tier that stores objects in their native form.

  11. Overview of the GigaSpaces Export/Import Tool

    The Export/Import tool is used for migrating data to new GigaSpaces deployments, capturing data snapshots, and bootstrapping disparate environments. It leverages the GigaSpaces Task Execution API to send export or import tasks to each primary space instance (partition) on the grid, making each primary instance responsible for its own data operation.

  12. Overview of Distributed WAN Gateway architecture

    A Distributed (multi-instance) WAN Gateway setup is used when a system contains large Space clusters or produces a high volume of activity that exceeds the throughput of a single gateway. In this topology, each partition (primary and backup instances) replicates its activity via a dedicated gateway instance. This allows the system to utilize full CPU and network bandwidth across different machines, reducing the risk of redolog accumulation and data lag between source and target Spaces.