Menu Close
Settings Close

Language and Page Formatting Options

Feature Support Document

Red Hat JBoss Data Grid 6.6

For use with Red Hat JBoss Data Grid 6.6.1

Christian Huffman

Red Hat Engineering Content Services

Abstract

Details JBoss Data Grid feature support and technology preview status information.

Chapter 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.1. 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/115883 for details about supported containers). Additionally, Library mode is supported outside the listed containers as a standalone application.

1.2. 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.0 includes full support for both Remote Client-Server mode and Library mode.

Table 1.1. JBoss Data Grid Features

Feature Remote Client-Server Mode (Supported) Library Mode (Supported)
File Cache Store and Loading
JDBC Cache Store and Loading
LevelDB Cache Store and Loading
Cassandra Cache Store and Loading
Cache Passivation
Remote Cache Store
Cluster Cache Store
Asynchronous Store
Cluster Configuration Using UDP
Cluster Configuration Using TCP
Mortal and Immortal Data
Eviction Strategy
Expiration
Unscheduled Write-behind Cache Store
Write-through Cache Store
Clustering Mode (local)
Clustering Mode (replicated)
Clustering Mode (invalidation)
Clustering Mode (distribution)
Asynchronous Clustering Modes
Marshalling
Management Using JMX
Cross-Datacenter Replication and State Transfer
JBoss Operations Network (JON) Integration and Plugin
Asymmetric Cluster
Command Line Interface (CLI)
Role-based Access Control
Node Authentication and Authorization
Encrypted Communication Within the Cluster
Per Invocation Flags
Handling Network Partitions
Spring Integration
Apache Camel Component for JBoss Fuse
Querying (by values)
Continuous Queries
Clustered Listeners and Notifications for Cache Events
Near Caching
JSR-107 Support
CDI
Asynchronous API
Distributed Streams 1
Deploy custom cache store to JDG Server  
Connection Pooling with JDBC Cache Stores  
REST Interface  
Memcached Interface  
Hot Rod Java client  
Hot Rod C++ Client  
Hot Rod .NET Client  
Hot Rod Node.js Client  
Data Compatibility Between Client-server Protocols  
Data Compatibility Between Hot Rod Java and C++ Client  
Rolling Upgrades for Hot Rod Cluster  
Rolling Upgrades for REST Clusters  
Controlled Shutdown and Restart of Cluster  
Authentication and Encryption over Hot Rod (Java client)  
JBoss Data Grid's Hot Rod Client as a JBoss EAP Module  
Externalizing HTTP sessions from JBoss EAP 7 to remote JDG cluster  
Remote Task Execution  
Apache Spark Integration  
Apache Hadoop Integration  
Administration Console  
READ_COMMITTED and REPEATABLE_READ Isolation Modes  
Lazy Deserialization  
Using the infinispan.xml File in Conjunction with APIs  
Custom Interceptors   2
Grouping API  
Java Transactional API (JTA) Support and Configuration  
Java Transactional API (JTA) Deadlock Detection  
Transaction Recovery  
Transaction and Batching  
Key Affinity  
Distributed Execution Framework  
JPA Cache Store  
JBoss Data Grid as a JBoss EAP Module  
JDG as Lucene Directory  
1: Distributed Streams are available in JBoss Data Grid's Remote Client-Server Mode via Remote Task Execution.
2: Custom Interceptors are deprecated in JBoss Data Grid 7.0.0, and are expected to be removed in a subsequent version.

Appendix A. Revision History

Revision History
Revision 6.6.0-2Fri Jun 23 2017John Brier
Removed unsupported mixed mode cluster from features table.
Revision 6.6.0-1Wed 7 Sep 2016Christian Huffman
Updating for 6.6.1.
Revision 6.6.0-0Mon 25 Jan 2016Christian Huffman
Initial draft for 6.6.0.

Legal Notice

Copyright © 2017 Red Hat, Inc.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.