Infinispan Hot Rod: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 14: Line 14:


<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
:[[Infinispan_HotRod_Client#Relationship_between_RemoteCacheManager_and_a_Server-Side_Cache_Container|HotRod client API]]
:[[Infinispan_HotRod_Java_Client#Relationship_between_RemoteCacheManager_and_a_Server-Side_Cache_Container|HotRod Java client API]]
</blockquote>
</blockquote>


Line 23: Line 23:
</blockquote>
</blockquote>


=HotRod Client=
=HotRod Clients=


<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
* [[Infinispan HotRod Java Client|Java Client]]
:[[Infinispan HotRod Client]]
* [[Infinispan HotRod C++ Client|C++ Client]]
</blockquote>

Latest revision as of 19:32, 26 June 2017

Internal

Overview

HotRod is Infinispan’s custom binary, language neutral protocol for communication between clients and servers. The protocol was designed to enable faster interactions compared to other existing text based protocols and to allow clients to make more intelligent decisions with regards to load balancing, failover and even data location operations. When interacting with Infinispan via the Hot Rod protocol, it is mandated that keys and values are byte arrays, to ensure platform neutral behavior. HotRod does not know about objects and types.

HotRod Connector

The HotRod connector is configured in the infinispan:server:endpoint Section.

For more details on HotRod clients and how they connect to a HotRod server:

HotRod Java client API

The HotRod connector exposes a series of JMX and CLI metrics. For more details on the exposed metrics, see:

HotRod Connector Metrics

HotRod Clients