You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please use https://github.ibm.com/cloud-docs/Cloudant for contributions to the documentation. Pushes to https://github.com/ibm-cloud-docs/Cloudant are only allowed by members of the documentation team. See [Documentation Update Process](https://github.ibm.com/cloud-docs/Cloudant/wiki/Documentation-Update-Process) for instructions.
23
+
Please use https://github.ibm.com/cloud-docs/Cloudant for contributions to the documentation. Pushes to https://github.com/ibm-cloud-docs/Cloudant are only allowed by members of the documentation team. See [Documentation Update Process](https://github.ibm.com/cloud-docs/Cloudant/wiki/Documentation-Update-Process) for instructions.
24
24
25
-
If you are not an IBM employee and want to make a documentation contribution, go to the [IBM Cloudant documentation](https://cloud.ibm.com/docs/services/Cloudant?topic=Cloudant-getting-started-with-cloudant#getting-started-with-cloudant) and click `Feedback` on the page where you want to comment.
25
+
If you are not an IBM employee and want to make a documentation contribution, go to the [IBM Cloudant documentation](https://cloud.ibm.com/docs/services/Cloudant?topic=Cloudant-getting-started-with-cloudant#getting-started-with-cloudant) and click `Feedback` on the page where you want to comment.
Copy file name to clipboardExpand all lines: monitor/capacity.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -319,12 +319,12 @@ See the following example JSON response with the target capacity set:
319
319
## View the current consumption of provisioned throughput capacity used
320
320
{: #view-current-capacity-consumption}
321
321
322
-
Use a GET method to the `/_api/v2/user/current/throughput` endpoint to see the current consumption of provisioned throughput capacity for an {{site.data.keyword.cloudant_short_notm}} instance. The current consumption shows the quantities of reads, writes, and global queries conducted against the instance for a given second. When you use this endpoint, it is a best practice to aggregate this data continuously over time to get a more comprehensive view of a {{site.data.keyword.cloudant_short_notm}} instance's throughput consumption patterns.
322
+
Use a GET method to the `/_api/v2/user/current/throughput` endpoint to see the current consumption of provisioned throughput capacity for an {{site.data.keyword.cloudant_short_notm}} instance. The current consumption shows the quantities of reads, writes, and global queries conducted against the instance for a given second. When you use this endpoint, it is a best practice to aggregate this data continuously over time to get a more comprehensive view of an {{site.data.keyword.cloudant_short_notm}} instance's throughput consumption patterns.
Copy file name to clipboardExpand all lines: offerings/learning-center.md
+23-23Lines changed: 23 additions & 23 deletions
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ You can use the [playlist](https://www.youtube.com/embed/playlist?list=PLzpeuWUE
23
23
## Introduction to {{site.data.keyword.cloudant_short_notm}} video
24
24
{: #cloudant-course-intro-video}
25
25
26
-
Learn about the {{site.data.keyword.cloudant_short_notm}} 17-part video series that provides an overview of the {{site.data.keyword.cloudant_short_notm}} database-as-a-service.
26
+
Learn about the {{site.data.keyword.cloudant_short_notm}} 17-part video series that provides an overview of the {{site.data.keyword.cloudant_short_notm}} database-as-a-service.
27
27
28
28
{: video output="iframe" data-script="#cloudant-course-intro-video-script" id="Introduction to IBM Cloudant video" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen}
29
29
@@ -38,7 +38,7 @@ This video is part 1 - *What is {{site.data.keyword.cloudant_short_notm}}?*
38
38
{{site.data.keyword.cloudant_short_notm}} is a database, run as a service in the {{site.data.keyword.cloud}}. Its job is to store your application's data securely and make it possible for you to retrieve it quickly and efficiently. {{site.data.keyword.cloudant_short_notm}}'s key features are shown in the following list:
39
39
40
40
Database
41
-
: Stores and retrieves data. More specifically, it is a JSON document store. JSON comes from JavaScript and represents simple objects in a universal file format.
41
+
: Stores and retrieves data. More specifically, it is a JSON document store. JSON comes from JavaScript and represents simple objects in a universal file format.
42
42
43
43
"Document"
44
44
: The unit of storage in {{site.data.keyword.cloudant_short_notm}}. Documents are added, updated, and deleted in their entirety.
@@ -63,7 +63,7 @@ That's the end of this part. The next part is called *The Document*.
63
63
## The Document video
64
64
{: #the-document-video}
65
65
66
-
Learn about {{site.data.keyword.cloudant_short_notm}} databases and documents work.
66
+
Learn about {{site.data.keyword.cloudant_short_notm}} databases and documents work.
@@ -148,7 +148,7 @@ That's the end of this part. The next part is called *The Document ID*.
148
148
## The `_id` video
149
149
{: #the-id-video}
150
150
151
-
Learn how `_id`s work in {{site.data.keyword.cloudant_short_notm}}, how they are different from relational databases, and how you can define your own `_id`.
151
+
Learn how `_id`s work in {{site.data.keyword.cloudant_short_notm}}, how they are different from relational databases, and how you can define your own `_id`.
@@ -344,7 +344,7 @@ That's the end of this part. The next part is called *HTTP API Basics*.
344
344
## HTTP API Basics video
345
345
{: #http-api-basics-video}
346
346
347
-
Learn how to use the command line to make HTTP requests and to add, edit, and delete documents.
347
+
Learn how to use the command line to make HTTP requests and to add, edit, and delete documents.
348
348
349
349
{: video output="iframe" data-script="#http-api-basics-video-script" id="HTTP API Basics video" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen}
350
350
@@ -497,9 +497,9 @@ That's the end of this part. The next part is called *Accessing {{site.data.keyw
497
497
## Accessing {{site.data.keyword.cloudant_short_notm}} Programmatically video
498
498
{: #accessing-cloudant-programmatically-video}
499
499
500
-
Learn how to access {{site.data.keyword.cloudant_short_notm}} programmatically.
500
+
Learn how to access {{site.data.keyword.cloudant_short_notm}} programmatically.
@@ -562,10 +562,10 @@ This video is part 10 - *Querying*.
562
562
563
563
So far we performed CRUD (create, retrieve, update, and delete) operations from the command line, the dashboard, and from code. These operations use the document's `_id`:
564
564
565
-
- Fetch document by `_id`.
566
-
- Update document whose `_id` = 'x'.
567
-
- Delete document whose `_id` = 'x'.
568
-
- Get documents in the `_id` range 'a' to 'z'.
565
+
- Fetch document by `_id`.
566
+
- Update document whose `_id` = 'x'.
567
+
- Delete document whose `_id` = 'x'.
568
+
- Get documents in the `_id` range 'a' to 'z'.
569
569
570
570
These operations are the building blocks of a database, but they get you only so far. What if you need to return a subset of documents that match on fields within the document? A person's birth date? A book's title? An order's value?
571
571
@@ -585,13 +585,13 @@ If you need to access objects within documents, you can use standard dot notatio
585
585
586
586
We can also add the following parameters:
587
587
588
-
Fields
588
+
Fields
589
589
: Specifies the document attributes that we want returned (the default is the entire document).
590
590
591
-
Sort
591
+
Sort
592
592
: Defines how the data is to be sorted. Sort is an array, allowing the sort to be calculated on multiple attributes.
593
593
594
-
Limit
594
+
Limit
595
595
: The number of documents to return.
596
596
597
597
If you are from a relational database background, this query is the equivalent SQL query to that last {{site.data.keyword.cloudant_short_notm}} query example.
@@ -631,7 +631,7 @@ That's the end of this part. The next part is called *Indexing*.
631
631
## Indexing video
632
632
{: #indexing-video}
633
633
634
-
Learn how indexing can speed up your query process.
634
+
Learn how indexing can speed up your query process.
635
635
636
636
{: video output="iframe" data-script="#indexing-video-script" id="Indexing video" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen}
637
637
@@ -728,13 +728,13 @@ Indexes build asynchronously and cannot be used until they build completely. Onc
728
728
`_count`
729
729
: For counting things.
730
730
731
-
`_sum`
731
+
`_sum`
732
732
: For totalizing values.
733
733
734
-
`_stats`
734
+
`_stats`
735
735
: For providing counts and totals suitable for calculating means, variances, and standard deviations.
736
736
737
-
`_approx_count_distinct`
737
+
`_approx_count_distinct`
738
738
: For approximate counting of unique values of the key.
739
739
740
740
The design document's `MAP` function is passed a `doc` - the function is called once per document in the database. Any key-value pairs that `emit` from the `MAP` function create the index.
@@ -832,7 +832,7 @@ The {{site.data.keyword.cloudant_short_notm}} Sync libraries are native iOS or A
832
832
833
833
Replication is a one-way operation from source to target, which moves all data (deletions, conflicts, attachments, as well as documents) and can be triggered in one of two ways:
834
834
835
-
1. Run until all the data from the source reaches the target and then stop.
835
+
1. Run until all the data from the source reaches the target and then stop.
836
836
2. The same as one, but the replication runs continuously forever, transferring new data from the source to the target as it arrives.
837
837
838
838
Replication can also be resumed from where it last stopped. {{site.data.keyword.cloudant_short_notm}} keeps a note of `checkpoints` between replicating parties to allow the resumption of a pre-existing replication from its last known position.
@@ -843,7 +843,7 @@ A replication can also be given a name, which is handy for tracking which replic
843
843
844
844
Now it's time for a practical exercise.
845
845
846
-
1. Go to the {{site.data.keyword.cloudant_short_notm}} Dashboard.
846
+
1. Go to the {{site.data.keyword.cloudant_short_notm}} Dashboard.
847
847
2. Create a database called `books2`.
848
848
3. Start a continuous replication from `books` to `books2`.
849
849
4. Visit the `books2` database to check that documents from `books` are now in `books2`.
@@ -932,7 +932,7 @@ That's the end of this part. The next part is called *{{site.data.keyword.clouda
932
932
## {{site.data.keyword.cloudant_short_notm}} Search video
933
933
{: #cloudant-search-video}
934
934
935
-
Learn how to use {{site.data.keyword.cloudant_short_notm}} Search, as well as Lucene query language and faceting.
935
+
Learn how to use {{site.data.keyword.cloudant_short_notm}} Search, as well as Lucene query language and faceting.
@@ -984,7 +984,7 @@ That's the end of this part. The next part is called *Under the hood*.
984
984
## Under the hood video
985
985
{: #under-the-hood-video}
986
986
987
-
Learn how the {{site.data.keyword.cloudant_short_notm}} service is organized.
987
+
Learn how the {{site.data.keyword.cloudant_short_notm}} service is organized.
988
988
989
989
{: video output="iframe" data-script="#under-the-hood-video-script" id="Under the hood video" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen}
Copy file name to clipboardExpand all lines: what-is-cloudant.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ subcollection: Cloudant
19
19
20
20
{{site.data.keyword.cloudant_short_notm}} is a close relative of the open-source database [Apache CouchDB](https://couchdb.apache.org/) and is run as a service so that customers don't have to worry about managing servers, networking, load balancing, database upgrades, database tuning or license fees - it is simply consumed over an encrypted HTTP API and charged by usage and data volume.
21
21
22
-
A {{site.data.keyword.cloudant_short_notm}} instance lives in an {{site.data.keyword.cloud_notm}} region and stores JSON documents in collections called databases. Each JSON document in a database is stored in triplicate (across multiple availability zones where supported) to allow {{site.data.keyword.cloudant_short_notm}} to remain available even during availability zone outages.
22
+
An {{site.data.keyword.cloudant_short_notm}} instance lives in an {{site.data.keyword.cloud_notm}} region and stores JSON documents in collections called databases. Each JSON document in a database is stored in triplicate (across multiple availability zones where supported) to allow {{site.data.keyword.cloudant_short_notm}} to remain available even during availability zone outages.
23
23
24
24
Finally, data can be bi-directionally replicated across regions, to
25
25
allow applications to survive regional failures with minimal downtime.
@@ -45,7 +45,7 @@ Unlike a [relational database](https://www.ibm.com/topics/relational-databases),
45
45
### Scalability
46
46
{: #scalability}
47
47
48
-
{{site.data.keyword.cloudant_short_notm}} is designed to scale from very small and zero-cost (on our Lite plan) to very large with linear billing costs proportional to the volume of data stored and the rate of read, write and query API calls made per second. A {{site.data.keyword.cloudant_short_notm}} instance can have hundreds of databases, with the potential for a database to store billions of documents. In total, a {{site.data.keyword.cloudant_short_notm}} instance can store tens of terabytes of data.
48
+
{{site.data.keyword.cloudant_short_notm}} is designed to scale from very small and zero-cost (on our Lite plan) to very large with linear billing costs proportional to the volume of data stored and the rate of read, write and query API calls made per second. An {{site.data.keyword.cloudant_short_notm}} instance can have hundreds of databases, with the potential for a database to store billions of documents. In total, an {{site.data.keyword.cloudant_short_notm}} instance can store tens of terabytes of data.
49
49
50
50
Paid plans can be scaled up and down in the web UI or through our API to meet expected demand or to scale back during quiet times.
51
51
@@ -59,10 +59,10 @@ Paid plans can be scaled up and down in the web UI or through our API to meet ex
59
59
60
60
The {{site.data.keyword.cloudant_short_notm}} service is managed 24/7 by IBM Engineers across the globe. Hardware refreshes, disk drive replacements, operating system upgrades and {{site.data.keyword.cloudant_short_notm}} code releases are all handled with zero downtime.
61
61
62
-
### HTTP API, Dashboard and SDKs
62
+
### HTTP API, Dashboard, and SDKs
63
63
{: #http-api-dashboard-and-sdks}
64
64
65
-
{{site.data.keyword.cloudant_short_notm}} has an [HTTP API](https://cloud.ibm.com/apidocs/cloudant#introduction) and each instance has a [web UI](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-navigate-the-dashboard) to provide easy management of a {{site.data.keyword.cloudant_short_notm}} instance, its databases, indexes and documents.
65
+
{{site.data.keyword.cloudant_short_notm}} has an [HTTP API](https://cloud.ibm.com/apidocs/cloudant#introduction) and each instance has a [web UI](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-navigate-the-dashboard) to provide easy management of an {{site.data.keyword.cloudant_short_notm}} instance, its databases, indexes and documents.
66
66
67
67
{{site.data.keyword.cloudant_short_notm}} provides SDKs to help your application to interact with databases programmatically in [Node.js](https://github.com/IBM/cloudant-node-sdk), [Java](https://github.com/IBM/cloudant-java-sdk), [Python](https://github.com/IBM/cloudant-python-sdk) and [Go](https://github.com/IBM/cloudant-go-sdk).
0 commit comments