Oracle NoSQL Database is a fully managed database cloud service that offers predictable low latency, dynamic scalability, high performance, and reliable data storage for document, key-value, and fixed-schema data. It is easy to start using the service in a matter of minutes. Since it is fully managed by Oracle, developers focus only on application development and data store requirements without the hassle of managing the underlying infrastructure, software, security, and high availability.
Learn more at the Oracle NoSQL Database home page.
Learn more on the Oracle NoSQL Database Cloud getting started page.
Oracle NoSQL Database manages the underlying infrastructure, software, security, capacity scaling, operations, and maintenance. You receive guaranteed high availability of the database service and elastic scaling to meet your application workloads.
Some typical use cases for Oracle NoSQL Database:
High-Level Features Comparison
|NoSQL Database Cloud Service||NoSQL Database Enterprise Edition (EE)|
|Infrastructure and software management/maintenance (servers, storage, networking, security, OS, and NoSQL software)||Managed by Oracle||Managed by customer|
|Database deployment||Oracle Cloud only||Customer on-premises data centers or BYOL in Oracle Cloud or other cloud vendors.|
|Licensing/Edition||Paid subscription or always-free service||Enterprise Edition (paid) or Community Edition (free open source)|
|Throughput||Throughput capacity is managed at each NoSQL Table level through NoSQL APIs or Oracle Cloud Infrastructure (OCI) Console. The capacity is measured in Write Units, Read Units. Throughput capacity per table can be adjusted to meet the dynamic workloads. When the limits for a table is exceeded, users are notified. At the tenancy level, there are maximum service limits. More details here.||Throughput capacity is managed at each NoSQL cluster. The capacity depends on the size of the NoSQL cluster deployed. Larger cluster size provides more throughput capacity for user tables.|
|Storage||Storage capacity is managed at each NoSQL Table level through NoSQL APIs or Oracle Cloud Infrastructure (OCI) Console. The capacity is measured in gigabytes (GB). Storage capacity per table can be adjusted to meet the dynamic workloads. When the limit for a table is exceeded, users are notified. At the tenancy level, there are maximum service limits. More details here.||Storage capacity is managed at each NoSQL cluster. The capacity depends on the number of disks and specific configuration in each storage node deployed in the cluster. Larger cluster size and disk capacity provide more storage for user tables.|
|Interoperability||Interoperates with NoSQL Database Enterprise Edition through a single programmatic interface with no application code modification.||Interoperates with NoSQL Database Cloud Service through a single programmatic interface with no application code modification.|
|Installation||No customer installs. Customers start using the service right away by creating NoSQL Tables.||Customers download and install the software to set up the NoSQL cluster in multiple storage nodes.|
Yes – Oracle NoSQL Database Hosted Environment is a NoSQL cluster environment that is dedicated to your tenancy, with all of the read and write units as well as the local attached storage are dedicated to your tenancy.
Learn more at the Oracle NoSQL Database help center.
Upon termination of your subscription, you will have 60 days to transfer your data for the terminated service from Oracle Cloud to a local system. After 60 days, Oracle permanently deletes any remaining content and software related to the terminated service.
Oracle NoSQL Database stores multiple copies of the data across availability domains for redundancy. If one availability domain (within a region) goes down, the data is still available to the application from the other availability domains. Oracle NoSQL Database guarantees 99.995% availability for your data.
Yes. Data is encrypted at rest with Advanced Encryption Standard (AES 256).
Yes. Data is encrypted in motion (transferring data between the application and Oracle NoSQL Database Cloud Service) with HTTPS.
Oracle NoSQL Database Hosted Environment offers a NoSQL cluster environment that is dedicated to your tenancy with dedicated direct attached storage. You control the access from your tenancy.
No. Oracle NoSQL Database manages the cluster and topology for you.
Learn more at the Oracle NoSQL Database data regions and service endpoints page.
Data is only replicated across availability domains within a region. Cross-region replication will be available soon.
The application should run in Oracle Cloud Infrastructure for the best performance. There are different instance shapes available for your application depending on its complexity and the workloads. A list of different shapes can be found on the Compute Pricing page.
It is advisable to run the application using Oracle Cloud infrastructure for the best user and customer experience.
Software development kits (SDKs) are available for the following programming languages. Follow the steps on download and installation in the links below.
SDKs work on either the cloud service or an on-premises NoSQL database.
Document, fixed schema, and key-value.
If the provisioned throughput limits are exceeded on read/write operations, Oracle NoSQL Database will throttle the requests and throw a ThrottlingException error to the application. The provisioned throughput limits can be increased if needed.
Yes - Oracle NoSQL Database Cloud Service offers on-demand capacity that automatically manages the read and write capacities to meet the needs of dynamic workloads.
Yes - You can also modify the capacity mode from provisioned capacity to on-demand capacity and vice-versa, using the following methods:
Predictable single-digit millisecond latency for database operations.
Yes. Oracle NoSQL Database provides ACID compliant transactions for full create, read, update, and delete (CRUD) operations, with adjustable durability and consistency transaction guarantees.
You can use the migrator tool to upload data. Download Oracle NoSQL Database Migrator.
Yes. Please refer to the documentation for additional information.
Yes. Your application can change the provisioned number of read units, write unites or storage capacity through the TableLimits API.
You can also change the provisioned number of read units, write units, or storage capacity using the service UI.
Additionally, you can change the capacity mode of your table from provisioned to on-demand, and vice versa.
Determine the size in bytes and round up to the next KB.
5 terabytes (TB) per tenant. This is the sum of all storage capacities of the tables provisioned within a tenancy. For more information, refer to the limits page or contact Oracle.
Oracle NoSQL Database is subject to the following usage limits. A tenant may create multiple tables up to these limits.
Per Table Limits
Per Tenant Limits
Customers to contact Oracle if they need more write/read units or storage above the maximum usage limits. For more information, refer to the limits page.
The maximum number of tables per tenant is 30. Learn more at the service limit page.
No. Latest software updates will take place behind the scenes. Your applications will run without a noticeable effect.
Please refer to the pricing section on the Oracle NoSQL Database Cloud Service page.
Yes. Please refer to the online calculator. Select Presets - Oracle Databases, then select Oracle NoSQL Database Cloud.
Read Unit per Month is defined as the throughput of up to one kilobyte (KB) of data per second for an eventually consistent read operation (i.e., where the data returned may not be the most recently written data to the database; if no new updates are made to the data, eventually all accesses to that data will return the latest updated value) over a one-month period, or approximately two million six hundred thousand (2.6 million) reads. Each month is deemed to have seven hundred forty-four (744) hours or approximately two million six hundred thousand (2.6 million) seconds. So over a one-month period, one (1) read unit will provide you with approximately 2.6 million reads. To achieve the throughput of up to one kilobyte (KB) of data per second for an absolute consistent read operation (i.e., where the data returned is expected to be the most recently written data to the database), the equivalent of two read units per month need to be provisioned.
Write Unit per Month: is defined as the throughput of up to one kilobyte (KB) of data per second for a write operation over a one month period, or approximately two million six hundred thousand (2.6 million) writes. Each month is deemed to have seven hundred forty-four (744) hours or approximately two million six hundred thousand (2.6 million) seconds. So over a one-month period, one (1) write unit will provide you with approximately 2.6 million writes.
Please refer to the detailed description in our documentation.
Please refer to the detailed description in our documentation.
Yes. Since the throughput can be scaled up or down programmatically at any time, make sure to provision the throughput accordingly for the workloads. In the provisioned model you are charged for what you provision.