|Important: All Cloudant documentation has moved to the IBM Bluemix platform.
You can find the new content
and the ‘IBM Bluemix’ topic in particular
Content on this page will no longer be updated (Jan 31st, 2017).
Cloudant is also available as an IBM Bluemix service. Bluemix is an open-standards, cloud platform for building, running, and managing applications. Find out more about Bluemix, and start using it, at the home page.
The following table summarizes the performance measures for each of the plans.
|Base Price (per hour)||$0.00||See Pricing details.|
|Disk Space||Included||1 GB||20 GB|
|Not available||See Pricing details.|
The Lite plan is free, but limits you to a maximum of 1GB of data storage. There are also limits on the provisioned throughput capacity for lookups, writes and queries.
If you would like to store more than 1GB of data, or to have a greater throughput capacity, you should move to the Standard plan.
The Standard plan includes 20GB of data storage. Above 20GB, you are charged a defined cost per GB per hour. See the Pricing information for the current cost. On the Standard plan, you can also change the amount of provisioned throughput capacity for lookups, writes and queries.
You can see details of the throughput capacity within the plans available for your account,
and select the level of provisioning that you want to use,
through the Account tab of your Cloudant account Dashboard.
To move to a different throughput capacity,
select the provisioning you want,
then click the
Change Capacity button.
You are asked to confirm the change,
and reminded that the provisioning change can take up to 24 hours to complete.
Provisioned throughput capacity
Throughput provision is identified and measured as one of three kinds of events:
- A lookup, which is a read of a specific document, based on its
- A write, which is a write of an individual document, or a write due to an index build.
- A query, which is a request made to one of the Cloudant query endpoints, including the following types:
The measurement of throughput is a simple count of the number of events of each type, per second, where the second is a sliding window. If your account exceeds the number of throughput events that are provisioned for the plan, requests are rejected until the number of events within the sliding window no longer exceeds the number provisioned. It might help to think of the sliding one-second window as being any consecutive period of 1,000 milliseconds.
For example, if you are on the Standard plan and have provisioned 200 lookups per second, your account might make a maximum of 200 lookup requests during a consecutive period of 1,000 milliseconds (1 second). Subsequent lookup requests made during the sliding 1,000 millisecond period are rejected until the number of lookup requests in that period drops below 200 again.
When a request is rejected because the number of events is exceeded,
applications receive an HTTP response:
429 Too Many Requests.
the supported client libraries do not automatically attempt to retry
a request when a
429 response is received.
It is better to ensure that your application handles
429 responses correctly.
The reason is that the number of retries is limited;
regularly transgressing the number of requests is a strong indicator
that you should move to a different plan configuration.
you must ensure that your application is able to handle a
429 response correctly.
Disk Space Included
This value is the storage capacity included in the plan. It is used for both data and index storage.
All Standard and Lite plan service instances are monitored for disk space used. If the account uses more than the amount of storage that is provided in your plan configuration, it is considered to ‘overflow’. An overflow causes the account to be billed at the indicated price for each extra GB used beyond the plan allocation.
The extra amount of money that you must pay for using more disk space than is provided in the plan is called an ‘overage’. Overage is calculated on an hourly basis. It is not possible to overflow the disk space available in the Lite plan.
For example, assume that your Standard plan instance increases disk usage to 107 GB for half a day (12 hours). This change means your instance caused an overflow of 87 GB more than the 20 GB plan allocation, for 12 hours. Therefore, you would be billed an overage charge based on 87 GB x 12 hours = 1044 GB hours for that extra space.
Overage is calculated by using the maximum number of GB above the plan allocation during a particular hour within the billing cycle.
A worked overage example
Assume that you start a month of 30 days with a Standard plan service instance that uses 9 GB of storage. Next, your storage increases to 21.5 GB for 15 minutes during the hour beginning at 02:00 of day 3. The instance drops back to 9.5 GB for the next 10 minutes of hour 02:00, then increases to 108 GB for the next 25 minutes of hour 02:00. Finally, your instance finishes the hour and indeed the rest of month by dropping down to 28 GB.
This pattern means the maximum number of GB above the plan allocation was 88 GB during hour 2 of day 3. For hour 03:00 of day 3, and for the rest of the month, your instance was 8 GB above the plan allocation.
Therefore, for hour 02:00 of day 3, you would be billed an overage based on 88 GB x 1 hour = 88 GB hours.
For hour 03:00 of day 3 to the end of day 3, you would be billed an overage based on 8 GB x 21 hours = 168 GB hours.
For hour 00:00 of day 4 to the end of the month (of 30 days), you would be billed an overage based on 8 GB x 24 hours x 27 days = 5184 GB hours.
The total overage bill for the month would be based on a total of 88 + 168 + 5184 = 5440 GB hours.
By default, all plans are based on multi-tenant clusters. As part of your plan selection, you can choose from the following Bluemix Public regions:
- US South
- United Kingdom
Security, Encryption, and Compliance
High Availability, Disaster Recovery, and Backup
To provide High Availability (HA) and Disaster Recovery (DR) within a data center, all data is stored in triplicate across three separate physical servers in a cluster. You can provision accounts in multiple data centers, then use continuous data replication to provide HA/DR across data centers.
Cloudant data is not automatically backed up. You can request enablement of an incremental backup feature, or alternatively implement your own solution by using one of several possible techniques that are described here.
Information about your usage is available in the Usage pane of the Activity tab within your Cloudant Dashboard.
If your monitoring indicates that a change to the provisioning in your plan might be advisable, for example if you are frequently approaching the maximum number of database lookups, then you can modify the provisioning through the Service pane on the Account tab of the Dashboard.
All plans are implemented on multi-tenant clusters. All data is stored in triplicate, across three separate physical nodes for High Availability and Data Recovery.
Support for Standard plan service instances is optional. It is provided by purchasing “Bluemix Standard Support”. Support is not available for the Lite plan.
Cloudant DBaaS Enterprise on single tenant dedicated hardware is available in a Bluemix Dedicated configuration.