Chapter 1. Introduction

1.1. Introduction

This document clarifies some important information related to features and support for Red Hat JBoss Data Grid, such as:

  • The two JBoss Data Grid Usage Modes
  • Supported JBoss Data Grid features
  • JBoss Data Grid features that are limited to a technology preview.

1.2. About Usage Modes

Red Hat JBoss Data Grid offers two usage modes:

  • Remote Client-Server mode
  • Library mode

Remote Client-Server mode, which provides a managed, distributed and clusterable data grid server. Applications can remotely access the data grid server using Hot Rod , memcached or REST client APIs.

Library mode allows the user to build and deploy a custom runtime environment. The Library usage mode hosts a single data grid node in the applications process, with remote access to nodes hosted in other JVMs. Tested containers for JBoss Data Grid Library mode includes JBoss Enterprise Web Server and JBoss Enterprise Application Platform (see https://access.redhat.com/articles/2435931 for details about supported containers). Additionally, Library mode is supported outside the listed containers as a standalone application.

1.3. Features and Usage Modes

The following table presents a list of features and indicates the usage mode for each feature. Red Hat JBoss Data Grid 7.2 includes full support for both Remote Client-Server mode and Library mode.

Table 1.1. JBoss Data Grid Features

FeatureRemote Client-Server Mode (Supported)Library Mode (Supported)

File Cache Store and Loading

3141

3141

JDBC Cache Store and Loading

3141

3141

LevelDB Cache Store and Loading

3141

3141

Cassandra Cache Store and Loading

3141

3141

Cache Passivation

3141

3141

Remote Cache Store

3141

3141

Cluster Cache Store

3141

3141

Asynchronous Store

3141

3141

Cluster Configuration Using UDP

3141

3141

Cluster Configuration Using TCP

3141

3141

Mortal and Immortal Data

3141

3141

Eviction Strategy

3141

3141

Expiration

3141

3141

Unscheduled Write-behind Cache Store

3141

3141

Write-through Cache Store

3141

3141

Clustering Mode (local)

3141

3141

Clustering Mode (replicated)

3141

3141

Clustering Mode (invalidation)

3141

3141

Clustering Mode (distribution)

3141

3141

Asynchronous Clustering Modes

3141

3141

Marshalling

3141

3141

Management Using JMX

3141

3141

Cross-Datacenter Replication and State Transfer

3141

3141

JBoss Operations Network (JON) Integration and Plugin

3141

3141

Asymmetric Cluster

3141

3141

Command Line Interface (CLI)

3141

3141

Role-based Access Control

3141

3141

Node Authentication and Authorization

3141

3141

Encrypted Communication Within the Cluster

3141

3141

Per Invocation Flags

3141

3141

Customizable Network Partition Handling

3141

3141

Spring Integration

3141

3141

Apache Camel Component for JBoss Fuse

3141

3141

Querying (by values)

3141

3141

Continuous Queries

3141

3141

Clustered Listeners and Notifications for Cache Events

3141

3141

Near Caching

3141

3141

JSR-107 Support

3141

3141

CDI

3141

3141

Asynchronous API

3141

3141

Distributed Streams1

3141

3141

Off Heap Cache Storage

3141

3141

Ickle Query Language

3141

3141

EAP Integration

3141

3141

Deploy custom cache store to JDG Server

3141

 

Connection Pooling with JDBC Cache Stores

3141

 

REST Interface

3141

 

Memcached Interface

3141

 

Hot Rod Java client

3141

 

Hot Rod C++ Client

3141

 

Hot Rod .NET Client

3141

 

Hot Rod Node.js Client

3141

 

Data Compatibility Between Client-server Protocols

3141

 

Data Compatibility Between Hot Rod Java and C++ Client

3141

 

Rolling Upgrades for Hot Rod Cluster

3141

 

Controlled Shutdown and Restart of Cluster

3141

 

JBoss Data Grid’s Hot Rod Client as a JBoss EAP Module

3141

 

Externalizing HTTP sessions from JBoss EAP 7 to remote JDG cluster

3141

 

Externalizing HTTP sessions from JBoss Web Server to remote JDG cluster

3141

 

Remote Task Execution

3141

 

Apache Spark with Scala 2.11

3141

 

Apache Hadoop Integration

3141

 

Administration Console

3141

 

READ_COMMITTED and REPEATABLE_READ Isolation Modes

 

3141

Lazy Deserialization

 

3141

Using the infinispan.xml File in Conjunction with APIs

 

3141

Grouping API

 

3141

Java Transactional API (JTA) Support and Configuration

 

3141

Java Transactional API (JTA) Deadlock Detection

 

3141

Transaction Recovery

 

3141

Transaction and Batching

 

3141

Key Affinity

 

3141

Distributed Execution Framework

 

3141

JPA Cache Store

 

3141

JBoss Data Grid as a JBoss EAP Module

 

3141

JDG as Lucene Directory

 

3141

1: Distributed Streams are available in JBoss Data Grid’s Remote Client-Server Mode via Remote Task Execution.

1.4. Hot Rod Features by Language

The following table presents a list of Hot Rod features and indicates the languages supported for each feature.

Table 1.2. Hot Rod Client Features by Language

 JavaC++C#Node.js

Cross-site Failover

3141

3141

3141

3141

Authentication

3141

3141

3141

3141

TLS-based Encryption

3141

3141

3141

3141

Server Name Indication (SNI)

3141

3141

3141

3141

Asynchronous API

3141

3141

3141

 

Near Caching

3141

3141

3141

 

Continuous Queries

3141

3141

3141

 

Remote Event Listeners

3141

  

3141

Remote Querying

3141

   

Remote Execution

3141

   

1.5. Technology Preview Features

The following features are included in Red Hat JBoss Data Grid 7.2 as a technology preview only:

  • Querying data via the REST interface: This technology preview feature provides the ability to query data via the REST interface using Ickle queries in JSON format. For more information, see Querying Data via the REST Interface in the Developer Guide.
  • The Hot Rod C++ Client includes the following features as technology preview:

    • Remote Querying
    • Remote Execution
  • The Hot Rod C# Client includes the following features as technology preview:

    • Remote Querying
    • Remote Execution
Warning

Technology Preview features are not supported with Red Hat production service level agreements (SLAs), may not be functionally complete, and are not recommended to be used for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.