Oracle Coherence sits at the in memory data grid layer of Fusion Middleware. Three editions, two metrics, and a cluster math model that audit findings consistently miss. This article maps the cost mechanics.
Oracle Coherence is the in memory data grid inside Oracle Fusion Middleware. Three editions ship: Standard Edition, Enterprise Edition, and Grid Edition. Each edition carries a per processor list price and a Named User Plus alternative.
The commercial model is straightforward. The audit risk is not. Coherence clusters span many JVMs across many hosts, and every cluster member counts toward the license count under Oracle technology counting rules.
Read this alongside the Oracle knowledge hub, the Oracle services, the WebLogic cloud guide, and the Vendor Shield subscription.
The three Coherence editions differ on feature set, not just price. Picking the wrong edition either over pays for unused features or under licenses on a feature already in production.
| Feature | Standard Edition | Enterprise Edition | Grid Edition |
|---|---|---|---|
| List price per processor | 5,000 USD | 23,000 USD | 35,000 USD |
| NUP minimum per processor | None | 10 | 10 |
| Replicated and partitioned cache | Yes | Yes | Yes |
| Near cache and continuous query | No | Yes | Yes |
| Live events and CDC | No | Yes | Yes |
| Distributed transactions | No | No | Yes |
| Topology Manager | No | No | Yes |
| Federation and persistence | No | Limited | Full |
Coherence offers two metrics. Per processor (counting cluster member JVMs on physical hosts under the Oracle core factor table). Per Named User Plus (named human or device users with a 10 NUP minimum per processor on Enterprise and Grid).
The cluster is where Coherence audit findings concentrate. Coherence customers consistently under count cluster members in two places: extend clients and proxy servers.
| Cluster component | Host count | Cores per host | Coherence processors |
|---|---|---|---|
| Cache servers | 12 | 16 | 96 (with 0.5 factor) |
| Storage disabled members | 4 | 8 | 16 (with 0.5 factor) |
| Proxy servers | 4 | 8 | 16 (with 0.5 factor) |
| Total Coherence processors | 20 hosts | -- | 128 processors |
Coherence on VMware triggers the same Oracle hard partitioning challenge as Oracle Database. The Oracle audit position counts every host in the cluster, then every host in the data center connected to vCenter.
A financial services customer runs a Coherence Enterprise Edition cluster of 96 cores across 12 hosts. The deployment supports a trading session cache with near cache, continuous query, and live events. No distributed transactions, no federation.
| Line item | Quantity | Unit | List cost |
|---|---|---|---|
| Coherence Enterprise Edition processor | 48 (96 core at 0.5 factor) | 23,000 USD list | 1.104M USD |
| Annual support 22 percent | -- | -- | 242,880 USD per year |
| 5 year TCO at list | -- | -- | 2.32M USD |
The seven step checklist takes a Coherence licensing position from current state to a negotiated renewal.
Enterprise Edition covers replicated cache, partitioned cache, near cache, continuous query, and live events. Grid Edition adds distributed transactions (XA), full federation, full persistence with snapshot recovery, and Topology Manager.
Grid Edition list price is 35,000 USD per processor versus Enterprise at 23,000 USD. Most deployments do not require distributed transactions or federation, so Enterprise covers the feature set at 34 percent lower list.
WebLogic Suite ships with Coherence Enterprise Edition for restricted use. The restricted use scope covers Coherence used for WebLogic clustering (session replication, cluster wide JNDI). It does not cover Coherence used by application code as a general purpose in memory data grid.
The audit finding on this point is one of the most common middleware findings. If application code uses Coherence APIs for cache, the deployment requires a separate Coherence license, not the WebLogic Suite restricted use.
Oracle treats VMware as soft partitioning. The audit position counts every host in the cluster, then every host in the data center connected to the vCenter. The buyer side counter is to cluster pin Coherence workloads with documented affinity rules, run a separate vCenter for Oracle workloads, and document that vMotion does not cross the cluster boundary.
The audit defense relies on quarterly topology export, vMotion event logs, and affinity rule documentation. Without this discipline, a 12 host Coherence cluster can expand to a 60 to 120 host audit position.
Extend clients connecting to the Coherence cluster through the Coherence Extend protocol are not counted as cluster members. The proxy servers that serve the extend clients are counted as cluster members on the licensed processor count.
The buyer side discipline is to document the number of proxy servers, the proxy server host placement, and the proxy server processor count. The extend client population itself does not drive license cost.
Yes. Oracle Coherence Enterprise and Grid Editions support BYOL to OCI under the Oracle Cloud Authorized License policy. The processor conversion follows the OCPU model on OCI: one OCPU equals one Coherence processor.
The economic case for OCI BYOL on Coherence is strongest where the existing on premise deployment is over licensed due to VMware soft partitioning. Moving to OCPU based OCI clears the soft partitioning challenge and aligns the license count to the deployment.
Redress runs Coherence advisory inside the Vendor Shield subscription, the Oracle middleware practice, and on engagement basis where a Coherence audit or renewal is open. The output is a cluster topology map, an effective license position, a hard partitioning audit, an edition recommendation, and a negotiation memo.
The engagement is led by former Oracle commercial professionals on the buyer side. We have run Coherence advisory across financial services, telecom, retail, and manufacturing customers running clusters from 40 cores to 800 cores.
Redress runs Coherence licensing advisory inside the Vendor Shield subscription, the Oracle services, the Software Spend Assessment, and the Renewal Program.
Read the related Oracle hub, the WebLogic cloud licensing, the Oracle Database licensing guide, the virtualization guide, the ULA negotiation guide, the audit services, the licensing consultants guide, the benchmarking page, the about us page, and the contact page.
Buyer side reference on Oracle ULAs across Database, middleware, and applications. The five stage ULA lifecycle, the certification math, the technical defenses, and the seven levers procurement carries to the certification window.
Independent. Buyer side. Written for CIOs, CFOs, procurement leaders, and Oracle licensing professionals running an active ULA or considering one. No Oracle kickback. No conflict on the table.
Open the white paper in your browser. Corporate email only.
Open the Paper →Coherence audit findings concentrate in two places. The cluster member count and the WebLogic Suite restricted use boundary. Discipline on both turns a 1.1 million USD list position into a controlled 386,000 USD spend.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Coherence cluster math, WebLogic restricted use boundaries, Fusion Middleware audit patterns, partitioning defenses, and middleware renewal lessons from every Oracle engagement we run on the buyer side.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
