Oracle Coherence Editions

KEY FEATURE SUMMARY

  Standard Edition Enterprise Edition 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 55 54 53
TCMP cluster technology 3,8 52 51 50
Support for cross-platform Data Clients 49 48 47
Multicast-free operation (WKA)   46 45
Security      
Network traffic encryption 44 43 42
Java Authentication & Authorization Service (JAAS) 41 40 39
Management & Monitoring      
Management host 3 38 37 36
Manageable via clustered JMX   35 34
Caching      
Local cache, Near cache, continuous query cache, real-time events 33 32 31
Fully replicated data management 30 29 28
Partitioned data management 27 26 25
Data source integration via read-through/write-through caching 24 23 22
Integration      
Hibernate integration 21 20 19
HTTP session management for application servers 4   18 17
BEA Portal "p13n cache" integration   16 15
Analytics      
Parallel InvocableMap and QueryMap 5   14 13
Transactions      
Write-behind caching   12 11
J2CA Resource Adapter   10 9
Compute Grid      
InvocationService   8 7
WorkManager   6 5
Enterprise Data Grid      
WAN support 6     4
Support for cross-platform Real Time Clients     3

  • 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 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 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.).
  • 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).
2 1