Coherence Features by Edition

Skip to end of metadata
Go to start of metadata
This page is for archival purposes only. Please refer to the Oracle® Fusion Middleware Licensing Information document for the latest licensing and feature breakdown information.

Coherence Server Editions



Standard Edition
(Formerly known as Caching Edition)
Enterprise Edition
(Formerly known as Application Edition)
Grid Edition
(Formerly known as 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, 7
  Support for cross-platform Data Clients
  Multicast-free operation (WKA)  
Security Network traffic encryption
  Java Authentication & Authorization Service (JAAS)
Management & Monitoring Management host 2
  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  
  BEA Portal "p13n cache" integration  
Analytics Parallel InvocableMap and QueryMap 4  
Transactions Write-behind caching  
  J2CA Resource Adapter  
Compute Grid InvocationService  
  WorkManager  
Enterprise Data Grid WAN support 5    
  Support for cross-platform Real Time Clients    

Coherence Client Editions



Data Client9 Real Time Client10
(configured as
Extend/TCP Client11)
Real Time Client10
(configured as
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
API Language Java
  .NET
 
  C++
 
Client API Data transformation (PIFPOF / ExternalizableLite / XmlBean)
  InvocationService
  6
  6
  NamedCache (core)
  NamedCache (with ObservableMap real time events)  
  MemberListener    
Connectivity Coherence*Extend client 8
  Multicast-free operation
  8
  8
  TCMP cluster technology 7    
Security Network traffic encryption
  Java Authentication & Authorization Service (JAAS)    
Caching Local cache  
  Near cache  
  Continuous query cache  
  Fully replicated cache    
  Partitioned Data Management      
Transactions Local transactions    
Integration Hibernate integration    
  HTTP session management for application servers    
  BEA Portal "p13n cache" 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. Grid Edition) as a Data Client or as a Real Time Client, but this requires server-side 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 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).

5 Grid Edition is required for WAN and other deployments that implement cluster-to-cluster interconnects, including any deployment where responsibility for data and/or processing spans more than one data center and activities are coordinated between those data centers using any form of Coherence-provided messaging or connectivity, such as deployments that feature two or more TCMP clusters interconnected by Coherence*Extend.

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

7 Oracle'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.).

8 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 is transported over TCP/IP.

9 Data Client may be used with all Coherence Server Editions.

10 Real Time Client may only be used with Grid Edition.

11 Extend/TCP is an abbreviation for Coherence*Extend configured for transport over TCP/IP.

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.