Skip Headers
Oracle® Coherence Getting Started with Oracle Coherence
Release 3.4

Part Number E13819-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

A Coherence Features by Edition

A.1 Coherence Server Editions

Table A-1 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

* Fault-tolerant data caching

Application data management

* Fault-tolerant data caching

* Data management including write-behind, transactions, analytics and events

Enterprise-wide data management

* 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 (see note 1)

Yes

Yes

Yes

 

TCMP cluster technology (see notes 3, 7)

Yes

Yes

Yes

 

Support for cross-platform Data Clients

Yes

Yes

Yes

 

Multicast-free operation (WKA)

Yes

Yes

Yes

Security

Network traffic encryption

Yes

Yes

Yes

 

Java Authentication & Authorization Service (JAAS)

Yes

Yes

Yes

Management & Monitoring

Management host (see note 2)

Yes

Yes

Yes

 

Manageable through clustered JMX

 

Yes

Yes

Caching

Local cache, Near cache, continuous query cache, real-time events

Yes

Yes

Yes

 

Fully replicated data management

Yes

Yes

Yes

 

Partitioned data management

Yes

Yes

Yes

 

Data source integration through read-through/write-through caching

Yes

Yes

Yes

Integration

Hibernate integration

Yes

Yes

Yes

 

HTTP session management for application servers

 

Yes

Yes

 

BEA Portal "p13n cache" integration

 

Yes

Yes

Analytics

Parallel InvocableMap and QueryMap (see note 4)

 

Yes

Yes

Transactions

Write-behind caching

 

Yes

Yes

 

J2CA Resource Adapter

 

Yes

Yes

Compute Grid

InvocationService

 

Yes

Yes

 

WorkManager

 

Yes

Yes

Enterprise Data Grid

WAN support (see note 5)

   

Yes

 

Support for cross-platform Real Time Clients

   

Yes


A.2 Coherence Client Editions

In Table A-2, note that the Data Client may be used with all Coherence Server Editions. The Real Time Client may only be used with Grid Edition. Extend/TCP is an abbreviation for Coherence*Extend configured for transport over TCP/IP.

Table A-2 Coherence Client Editions



Data Client (see note 9) Real Time Client (see note 10) (configured as Extend/TCP Client; see note 11) Real Time Client (see note 10) (configured as Compute Client)
   

Data Grid client for use anywhere

* Access to data and services on the data grid

Real time desktop client

* Access to data and services on the data grid

* Real time synchronization with the data grid

Server-class client

* 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

Yes

Yes

Yes

 

.NET

Yes

Yes

 

Client API

Data transformation (PIFPOF / ExternalizableLite / XmlBean)

Yes

Yes

Yes

 

InvocationService

Yes (see note 6)

Yes (see note 6)

Yes

 

NamedCache (core)

Yes

Yes

Yes

 

NamedCache (with ObservableMap real time events)

 

Yes

Yes

 

MemberListener

   

Yes

Connectivity

Coherence*Extend client (see note 8)

Yes

Yes

Yes

 

Multicast-free operation

Yes (see note 8)

Yes (see note 8)

Yes

 

TCMP cluster technology (see note 7)

   

Yes

Security

Network traffic encryption

Yes

Yes

Yes

 

Java Authentication & Authorization Service (JAAS)

   

Yes

Caching

Local cache

 

Yes

Yes

 

Near cache

 

Yes

Yes

 

Continuous query cache

 

Yes

Yes

 

Fully replicated cache

   

Yes

 

Partitioned Data Management

     

Transactions

Local transactions

   

Yes

Integration

Hibernate integration

   

Yes

 

HTTP session management for application servers

   

Yes

 

BEA Portal "p13n cache" integration

   

Yes

Management & Monitoring

Management host

   

Yes

 

Manageable through clustered JMX

   

Yes

Compute Grid

InvocationService

   

Yes

 

WorkManager

   

Yes


Notes:

  1. Coherence TCMP clusters must be homogeneous with respect to the Coherence Edition. A TCMP cluster of one type (for example, Caching Edition) may connect to a TCMP cluster of another type (for example, 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, 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 through 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 (for example, data management, remote invocation, management and monitoring, and so on).

  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 may be transported over TCP/IP (optimal performance) or over a pre-existing JMS provider (for compatibility with existing infrastructure).