Coherence Features by Edition

Coherence Server Editions
Caching Edition
(Formerly known as Clustered Edition) 		Application Edition
(Formerly known as Enterprise Edition) 		Data Grid Edition


Application caching solution Application data management Enterprise-wide data management


* Fault-tolerant data caching





* Fault-tolerant data caching
* Data management including
write-behind, transactions,
analytics and events


* Fault-tolerant data caching
* Data management including
write-behind, transactions,
analytics and events
* Support for heterogeneous
clients
Connectivity Embedded Data Client and Real Time Client functionality 1
●
●
●
  TCMP cluster technology 3, 8
●
●
●
  Support for cross-platform Data Clients
●
●
●
  Multicast-free operation (WKA)  
●
●
Security Network traffic encryption
●
●
●
  Java Authentication & Authorization Service (JAAS)
●
●
●
Management & Monitoring Management host 3
●
●
●
  Manageable via clustered JMX  
●
●
Caching Local cache, Near cache, continuous query cache, real-time events
●
●
●
  Fully replicated data management
●
●
●
  Partitioned data management
●
●
●
  Data source integration via read-through/write-through caching
●
●
●
Integration Hibernate integration
●
●
●
  HTTP session management for application servers 4
●
●
●
  BEA Portal "p13n cache" integration  
●
●
Analytics Parallel InvocableMap and QueryMap 5  
●
●
Transactions Write-behind caching  
●
●
  J2CA Resource Adapter  
●
●
Compute Grid InvocationService  
●
●
  WorkManager  
●
●
Enterprise Data Grid WAN support 6    
●
  Support for Compute Clients    
●
  Support for cross-platform Real Time Clients    
●

Coherence Client Editions (for use with Data Grid Edition)
Data Client Real Time Client Compute Client


Data Grid client for use anywhere Real time desktop client Server-class client
    * Access to data and services
on the data grid





* Access to data and services
on the data grid
* Real time synchronization with
the data grid



* Access to data and services
on the data grid
* Real time synchronization with
the data grid
* Server-class client:
manageability, monitoring,
Quality of Service, performance
Client API Data transformation (PIFPOF / ExternalizableLite / XmlBean)
●
●
●
  InvocationService
  ●7
  ●7
●
  NamedCache (core)
●
●
●
  NamedCache (with ObservableMap real time events)  
●
●
  MemberListener    
●
Connectivity Coherence*Extend client 9
●
●
●
  Multicast-free operation
  ●9
  ●9
●
  TCMP cluster technology 8    
●
Security Network traffic encryption
●
●
●
  Java Authentication & Authorization Service (JAAS)    
●
Caching Local cache  
●
●
  Near cache  
●
●
  Continuous query cache  
●
●
  Fully replicated cache    
●
Transactions Local transactions    
●
Integration Hibernate integration    
●
  HTTP session management for application servers    
●
  BEA Portal integration    
●
Management & Monitoring Management host    
●
  Manageable via clustered JMX    
●
Compute Grid InvocationService    
●
  WorkManager    
●

1 Coherence TCMP clusters must be homogeneous with respect to the Coherence Edition. A TCMP cluster of one type (e.g. Caching Edition) may connect to a TCMP cluster of another type (e.g. Data Grid Edition) as a Data Client or as a Real Time Client, but this requires server-side connection licenses. The connection type is configurable and defaults to Real Time Client.

2 Supports integration with a local MBeanServer. This, in conjunction with local JMX "agents", allows this node to provide management and monitoring features. Clustered JMX support adds the ability for this node to manage and monitor remote nodes as well.

3 Coherence Editions may not be mixed within the context of a single TCMP-based cluster. Integration of different Edition types is accomplished via Coherence*Extend (with each cluster acting as either a Data Client or a Real Time Client).

4 Caching Edition does not support InvocationService, which is required for an additional "sticky" load balancer optimization.

5 Parallel support for InvocableMap and QueryMap will result in server-side execution whenever possible, minimizing data transfer, allowing use of indexing, and parallelizing execution across the cluster. Without parallel support, the operations will retrieve the full dataset to the client for evaluation (which may be very inefficient).

6 Data Grid Edition is required for WAN deployments.

7 InvocationService requests from Data Client and Real Time Client are client-only, and there are limitations in Coherence 3.2.

8 Tangosol's cluster-aware wire protocol (TCMP) provides detailed knowledge of the entire cluster that enables direct server access for lower latency and higher throughput, faster failover/failback/rebalancing, and the ability for any participating member to act as a service provider (e.g. data management, remote invocation, management and monitoring, etc.).

9 Coherence*Extend is used to extend the core TCMP cluster to a greater ranging network, including desktops, other servers and WAN links. The Coherence*Extend protocol may be transported over TCP/IP (optimal performance) or over a pre-existing JMS provider (for compatibility with existing infrastructure).

Error formatting macro: rate: java.lang.NullPointerException
Error formatting macro: rate: java.lang.NullPointerException
Unknown macro: {rate-table}