Oracle NoSQL Database Third-Party Support: Preserve Your Distributed Key-Value Infrastructure Without Oracle's OCI Migration Mandate

What Oracle NoSQL Database Third-Party Support Actually Covers

Oracle NoSQL Database (formerly Oracle NoSQL Database KVStore) is a distributed key-value and document store built on Berkeley DB Java Edition (BDB JE). The KVStore architecture uses a replication factor-based distribution model across Storage Nodes (SNs) organised into Replication Groups (RGs), with an Administration Service managing topology, and a KVProxy providing REST, HTTPKV, and Java Driver API access. Oracle NoSQL EE (Enterprise Edition) adds security features (Kerberos, LDAP, TLS), advanced monitoring, and the Oracle Enterprise Manager integration that production deployments depend on. Organisations that built data ingestion pipelines, session state management, or reference data caching on Oracle NoSQL have integrated application code using the Oracle NoSQL Java Driver API, the Oracle NoSQL C Driver, or the Oracle NoSQL Python Driver — APIs that have no direct equivalent in OCI NoSQL's Table API model.

Third-party support for Oracle NoSQL Database covers the complete KVStore stack: Storage Node Agent (SNA) processes, Administration process, KVProxy, replication group topology management, BDB JE underlying storage engine, Oracle NoSQL Java/C/Python Driver support, and Oracle NoSQL security configuration (TLS, Kerberos). When your Oracle NoSQL environment moves to TPS, GoVendorFree engineers provide incident resolution, topology rebalancing guidance, replication lag diagnosis, BDB JE log cleaner tuning, and driver-side performance optimisation — without Oracle's requirement to upgrade to the latest EE release or transition to OCI.

Oracle's commercial posture on NoSQL KVStore on-premise has shifted decisively toward OCI: new NoSQL feature development is concentrated on OCI NoSQL's serverless Table API model, while on-premise KVStore receives only maintenance updates. Oracle TPS provides the commercial alternative that maintains on-premise NoSQL capability at 50–65% lower annual cost while your data architecture roadmap is evaluated on your terms.

Oracle NoSQL Database Version Support Matrix

Oracle NoSQL 18c and 19c — the versions most commonly deployed in enterprise production environments — are in Sustaining Support or Extended Support respectively. Organisations paying Oracle's annual maintenance fees for these versions receive no new feature delivery and security patches only through Oracle's CPU process. Oracle Database TPS combined with Oracle NoSQL TPS provides comprehensive cost reduction for environments where NoSQL KVStore sits adjacent to an Oracle Database relational tier in a polyglot data architecture.

Why Oracle NoSQL Customers Move to Third-Party Support

Three structural barriers consistently drive Oracle NoSQL customers to TPS: OCI NoSQL Table API incompatibility, KVStore driver API lock-in, and on-premise deployment topology requirements.

Barrier 1 — OCI NoSQL Table API Incompatibility

Oracle's OCI NoSQL Database Service is built around a serverless Table API with a columnar data model — fundamentally different from Oracle NoSQL KVStore's key-value and JSON document model. Applications using the Oracle NoSQL Java Driver's KVStore API to perform Key, Value, and Depth-keyed operations, Major/Minor key range queries, and Avro-serialised record storage cannot be migrated to OCI NoSQL's Table API without application-level refactoring of every data access pattern. For a financial services firm with 200–500 data access paths in a real-time aggregation engine, or a telecoms operator with millions of subscriber key-value records accessed via complex major/minor key range queries, the migration programme runs to £600K–£2.5M over 12–24 months — not including the performance re-validation against original latency SLAs. TPS eliminates that commercial migration pressure immediately.

Barrier 2 — KVStore Driver API and Avro Serialisation Lock-In

Oracle NoSQL KVStore applications are tightly coupled to the Oracle NoSQL Driver API's programming model: KVStore handle management, DurabilityPolicy configuration for write consistency, Consistency objects for read-your-writes semantics, and Avro schema management for binary record serialisation. The Avro schema registry embedded in Oracle NoSQL KVStore is Oracle-proprietary and has no equivalent in OCI NoSQL's JSON or columnar Table API. Applications that store 50–500 Avro schemas across a KVStore namespace — representing years of schema evolution with backward and forward compatibility management — cannot migrate those schemas to OCI NoSQL without re-implementing the serialisation layer in application code. For high-throughput data platforms processing millions of records per hour, re-implementing Avro schema management outside of KVStore adds £200K–£800K in additional infrastructure engineering cost. TPS protects the existing investment while that engineering cost is evaluated properly.

Barrier 3 — On-Premise Deployment and Data Sovereignty Requirements

Oracle NoSQL KVStore's enterprise deployment model — where Storage Nodes run on bare-metal or dedicated virtual machines in customer-controlled data centres — provides the data locality and network proximity required for sub-millisecond key-value access latency. For IoT data ingestion platforms processing sensor data at edge data centres, or for financial services firms with data residency requirements under UK GDPR Article 44–49 that restrict transfer of personal data to OCI's multi-tenant cloud infrastructure, on-premise KVStore is a regulatory and architectural requirement — not a technology preference. GoVendorFree's audit defence service ensures that Oracle licence audit methodologies applied to KVStore environments — where Oracle has historically attempted to count licence entitlement across all Storage Node processors — are challenged with accurate contractual analysis.

Oracle NoSQL Database TPS by Industry

Oracle NoSQL KVStore found its enterprise production deployments concentrated in industries requiring high-throughput, low-latency key-value access at scale with data locality constraints.

Financial Services — Data Aggregation and Reference Data

Investment banks and data vendors deployed Oracle NoSQL for real-time reference data distribution — security master data, pricing data, and corporate actions data distributed to trading systems across multiple data centres. KVStore's strong consistency model (configurable Durability) and its major/minor key structure make it well-suited to hierarchical reference data access patterns (instrument → price series → time-bucketed values). UK FCA Market Conduct and Systems and Controls requirements treat reference data infrastructure as regulated infrastructure with change management obligations — making OCI cloud migration a regulated change programme requiring FCA notification under SYSC 8. TPS saves £80K–£360K per year for mid-size financial services NoSQL deployments.

Telecommunications — Subscriber Profile Management

Telecoms operators use Oracle NoSQL for subscriber profile storage in Home Subscriber Server (HSS) and Policy and Charging Rules Function (PCRF) systems where per-subscriber data must be retrieved in under 1 millisecond to meet 3GPP LTE signalling plane requirements. KVStore's replication group architecture allows geographic distribution of subscriber data with replication factor-based redundancy that meets telecoms carrier-grade availability requirements (99.999%). Migrating to OCI NoSQL would introduce WAN latency between the OCI region and the telecoms Packet Core — latency that is incompatible with LTE and 5G signalling plane performance requirements. TPS preserves the on-premise KVStore investment at substantial cost reduction.

Retail and IoT — Sensor Data and Session State

Retailers and IoT platform operators deployed Oracle NoSQL for high-frequency sensor data ingestion at edge data centres and for distributed session state management in high-traffic e-commerce platforms. KVStore's write throughput (millions of operations per second on a properly sized cluster) and its configurable durability model (WRITE_NO_SYNC for maximum throughput vs SYNC for durability guarantee) provide the flexibility that IoT and e-commerce data platforms require. TPS saves £44K–£180K per year for mid-market Oracle NoSQL deployments covering 6–20 Storage Nodes.

Oracle NoSQL Database TPS Cost Model

Oracle NoSQL Database Enterprise Edition is licensed per processor on all Storage Nodes and on the Administration Service host. GoVendorFree calculates your TPS saving based on the processor count across your complete KVStore topology. Indicative four-profile saving model:

What GoVendorFree Oracle NoSQL TPS Includes

GoVendorFree Oracle NoSQL Database third-party support provides the following service coverage from day one of transition:

• KVStore topology incident resolution — Storage Node failure recovery, Replication Group rebalancing, Administration Service failover, and KVProxy reconnection
• BDB JE storage engine tuning — log cleaner configuration, cache size tuning for BDB JE page cache, replication stream backlog management, and write throughput optimisation
• Driver API support — Java Driver, C Driver, and Python Driver troubleshooting; DurabilityPolicy and Consistency configuration advisory; Avro schema evolution guidance
• Security configuration support — TLS configuration, Kerberos integration, LDAP user management, and security role assignment troubleshooting
• Replication and consistency advisory — Replication Factor tuning, consistency lag monitoring, and cross-data-centre replication topology guidance
• 15-minute P1 response SLA — engineer engagement within 15 minutes for Storage Node failure or data unavailability events, 24/7/365

Transitioning Oracle NoSQL to Third-Party Support

Oracle NoSQL TPS transitions require no changes to KVStore topology, application driver configuration, or data schema. The transition is at the support contract level only. Pre-transition assessment covers: Oracle support contract renewal dates and CSI numbers for NoSQL EE licences; current Storage Node count and processor licence entitlement validation; active Oracle SRs for resolution before transition; and GoVendorFree knowledge base onboarding for your specific KVStore version, topology, and custom component inventory (custom secondary indexes, Avro schema registry state).

GoVendorFree maintains engineering capability across KVStore 3.x through NoSQL 21c, including the BDB JE storage engine changes across major versions and the security architecture changes introduced in NoSQL 18c. Our NoSQL support engineers have managed KVStore deployments at financial services, telecoms, and IoT scale — with direct experience of Storage Node failure recovery, topology rebalancing under load, and BDB JE log cleaner emergency intervention. Our Oracle TPS service has supported Oracle NoSQL environments since 2017.

Oracle NoSQL Database TPS: Frequently Asked Questions

Does TPS cover Oracle NoSQL Community Edition (CE)?

GoVendorFree TPS is designed for Oracle NoSQL Enterprise Edition — the commercially licensed version with security, advanced monitoring, and OEM integration. CE is Apache-licensed open source and does not require Oracle support contracts. If your organisation has both CE and EE deployments, GoVendorFree will assess which components carry Oracle licence obligations as part of the pre-transition review.

Can we continue to evolve our Avro schemas under TPS?

Yes. TPS covers the Oracle NoSQL infrastructure and driver layer — it does not restrict your application's use of the Avro schema registry or driver APIs. Schema evolution, backward/forward compatibility management, and application driver upgrades within your supported KVStore version all continue without restriction under TPS.

Does Oracle NoSQL TPS work alongside Oracle Database TPS?

Yes — and polyglot environments running Oracle NoSQL alongside Oracle Database for relational workloads benefit from a combined TPS engagement that covers both data tiers. See our Oracle Database TPS guide for the complete Oracle Database savings model, and Oracle Coherence TPS guide for environments where Coherence also sits in the data tier alongside NoSQL KVStore.

Related Oracle TPS Guides