Sua Pesquisa não corresponde a nenhum resultado
Oracle NoSQL Database is a fully managed database cloud service that offers low latency, flexible, scalable, high performance, and reliable data storage for document, key-value, and table data models. It is easy to start using the service in a matter of minutes. Since it is fully managed by Oracle, developers focus only on their application development and data store requirements. They never deal with the time consuming tasks and processes of managing back-end servers, storage, cluster deployment, topology, software installation/patches/upgrades, backup, operating systems, and high availability.
Product road maps are available upon request.
Oracle NoSQL Database handles software and hardware provisioning, management, scaling, and mission critical 24x7 support. You receive guaranteed high availability of the database service and elastic scaling of the hardware resources as your provisioned workload demands change.
No. Oracle NoSQL Database manages the topology of the cluster for you.
Not at the first release.
No, all the upgrading to a newer version of the software will take place behind the scenes. Your applications will run without a noticeable effect.
Any application that requires extremely fast storage and retrieval of data. In general use cases for Oracle NoSQL Database:
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.
The 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.
It is the responsibility of the owner of the application to implement a strategy that will ensure that the application remains active.
Initially Ashburn (IAD). Other OCI sites will be available later.
Data is only replicated across Availability Domains within a region, not across regions. Cross-Region replication will come at a later time.
Yes, all data is encrypted at rest using AES 256.
Yes, using https.
The application should run in the Oracle Cloud Infrastructure. There are a number of hardware options available for your application depending on the complexity of the application. A list of options can be found on the Oracle Cloud Infrastructure web page.
Visit https://cloud.oracle.com/en_US/nosql to get started. Also visit our documentation portal at: http://www.oracle.com/pls/topic/lookup?ctx=cloud&id=CSNSD-GUID-88373C12-018E-4628-B241-2DFCB7B16DE8
Oracle is encouraging that the application is run on systems within the Oracle Cloud data center for the best user and customer experience.
Java is required at the first release, with other programming languages available later and will include Python, node.js, C#, C++, and Go.
Tables, Key-Value and JSON.
If the provisioned throughput limits are exceeded on read/write operations then Oracle NoSQL Database will throttle the requests and throw a ThrottlingException exception to the application.
Read latencies are expected to be less than 10 milliseconds for a 1 KB payload and write latencies are expected to be less than 15 milliseconds for a 1 KB payload.
Yes, Oracle NoSQL Database is fully ACID compliant for any data. Oracle NoSQL Database also supports eventually consistent reads for those applications that wish to trade off consistency for cost.
Yes. You can use the Oracle NoSQL Cloud Simulator, which is a free download from the Oracle Cloud Downloads page. However, you cannot run production level software with Oracle NoSQL Cloud Simulator and it is not scaleable. It can be downloaded as part of the Oracle NoSQL Cloud SDK located on the OTN Cloud Downloads page.
Send email to: firstname.lastname@example.org, or contact us through https://cloudcustomerconnect.oracle.com/pages/home. We monitor both regularly.
At the initial release, the customer will need to upload their data to the Oracle Cloud Infrastructure Object Storage, and then have their Oracle NoSQL Database application read from the Oracle Cloud Infrastructure Object Storage.
This will be in a future release.
Read Unit per Month: Defined as the throughput of up to 1 kilobyte (KB) of data per second for an eventually consistent read operation over a month, approximately 2.6 million reads. **To achieve the throughput of up to 1 KB of data per second for an absolute consistent read, the equivalent of two eventually consistent read units need to be provisioned.
If an item size is less than 1 KB, it is rounded up to 1 KB. For example, if it is 0.5 KB, it will be 1 KB for the provisioned throughput calculation. If the item size is larger than 1 KB, it is rounded up to the next multiple of 1KB. Example, if an item size is 1.5 KB, it will be rounded up to 2 KB for the provisioned throughput.
Write Unit per Month: Defined as the throughput of up to 1 KB of data per second for a write operation over a month, approximately 2.6 million writes. **
A Write Unit provides approximately 3,600 writes per hour. If an item size is less than 1 KB, it is rounded up to 1 KB. For example, if an item's size is 0.5 KB, it will be rounded up to 1 KB for the provisioned throughput calculation. If the item size is larger than 1 KB, it is rounded up to the next multiple of 1 KB. For example, if an item size is 9.1 KB, it will be rounded up to 10 KB for the provisioned throughput.
** Each month is considered to have 744 hours or approximately 2.6 million seconds.
A discussion of how many bytes an item uses can be viewed in the Oracle NoSQL Database Capacity Planning White Paper.
The pricing for your use of Oracle NoSQL Database can be viewed at: http://cloud.oracle.com/en_US/nosql/pricing.
Please see the document: https://docs.oracle.com/en/cloud/get-started/subscriptions-cloud/csgsg/monthly-flex.html to determine if Monthly Flex is right for your usage and commitment.
A detailed discussion can be viewed in the Oracle NoSQL Database Capacity Planning White Paper.
Yes, the application can change the provisioned amount for the number of read units, the number of write unites or the storage needed, through the TableLimits API. Independently, the read units, write units or GB of storage can be increased or decreased. The increased values for read, write or storage are immediately provisioned.
Determine the size in bytes and round up to the next KB.
Yes, until you decrease the limits or end the service.
Yes. We have an online calculator which can be accesed at: https://cloud.oracle.com/en_US/cost-estimator
Below are 3 typical scenarios for a quick view which show some examples of different table throughput and sizes.
See the calculator at https://cloud.oracle.com/en_US/cost-estimator for more precise information.
5 Terabytes (TB) per tenant. This will be the sum of all of the tables that a tenant provisions.
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.
The maximum number of tables per tenant is 30.