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
Copy file name to clipboardExpand all lines: docs-ref-services/preview/cosmos-readme.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ Refer to [javadocs][api_documentation] for more details on the package
69
69
### Prerequisites
70
70
71
71
-[Java Development Kit (JDK) with version 8 or above][jdk]
72
-
- An active Azure account. If you don't have one, you can sign up for a [free account][azure_subscription]. Alternatively, you can use the [Azure Cosmos DB Emulator](https://azure.microsoft.com/documentation/articles/documentdb-nosql-local-emulator) for development and testing. As emulator https certificate is self signed, you need to import its certificate to java trusted cert store as [explained here](/azure/cosmos-db/local-emulator-export-ssl-certificates)
72
+
- An active Azure account. If you don't have one, you can sign up for a [free account][azure_subscription]. Alternatively, you can use the [Azure Cosmos DB Emulator](https://azure.microsoft.com/documentation/articles/documentdb-nosql-local-emulator) for development and testing. As emulator https certificate is self signed, you need to import its certificate to java trusted cert store as [explained here](https://docs.microsoft.com/azure/cosmos-db/local-emulator-export-ssl-certificates)
73
73
- (Optional) SLF4J is a logging facade.
74
74
- (Optional) [SLF4J binding](https://www.slf4j.org/manual.html) is used to associate a specific logging framework with SLF4J.
75
75
- (Optional) [Maven][maven]
@@ -106,32 +106,32 @@ CosmosClient cosmosClient = new CosmosClientBuilder()
106
106
107
107
Azure Cosmos DB Java SDK provides client-side logical representation to access the Azure Cosmos DB SQL API.
108
108
A Cosmos DB account contains zero or more databases, a database (DB) contains zero or more containers, and a container contains zero or more items.
109
-
You may read more about databases, containers and items [here](/azure/cosmos-db/databases-containers-items).
109
+
You may read more about databases, containers and items [here](https://docs.microsoft.com/azure/cosmos-db/databases-containers-items).
110
110
A few important properties defined at the level of the container, among them are provisioned throughput and partition key.
111
111
112
112
### Global Distribution
113
113
- Azure Cosmos DB is a globally distributed database service that's designed to provide low latency, elastic scalability of throughput, well-defined semantics for data consistency, and high availability.
114
114
In short, if your application needs guaranteed fast response time anywhere in the world, if it's required to be always online, and needs unlimited and elastic scalability of throughput and storage, you should build your application on Azure Cosmos DB.
115
-
You may read more about global distribution [here](/azure/cosmos-db/distribute-data-globally).
115
+
You may read more about global distribution [here](https://docs.microsoft.com/azure/cosmos-db/distribute-data-globally).
116
116
117
117
### Throughput Provisioning
118
118
- Azure Cosmos DB allows you to set provisioned throughput on your databases and containers.
119
119
There are two types of provisioned throughput, standard (manual) or autoscale. Provisioned throughput can be selected at per-container granularity or per-database granularity, however container-level throughput specification is typically preferred.
120
-
You may read more about throughput provisioning [here](/azure/cosmos-db/set-throughput).
120
+
You may read more about throughput provisioning [here](https://docs.microsoft.com/azure/cosmos-db/set-throughput).
121
121
122
122
### Request Units (RUs)
123
123
- Azure Cosmos DB supports many APIs, such as SQL, MongoDB, Cassandra, Gremlin, and Table.
124
124
Each API has its own set of database operations. These operations range from simple point reads and writes to complex queries.
125
125
Each database operation consumes system resources based on the complexity of the operation. The cost of all database operations is normalized by Azure Cosmos DB and is expressed by Request Units (or RUs, for short).
126
126
You can think of RUs per second as the currency for throughput. RUs per second is a rate-based currency. It abstracts the system resources such as CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB.
127
-
You may read more about request units [here](/azure/cosmos-db/request-units).
127
+
You may read more about request units [here](https://docs.microsoft.com/azure/cosmos-db/request-units).
128
128
129
129
### Partitioning
130
130
- As items are inserted into a Cosmos DB container, the database grows horizontally by adding more storage and compute to handle requests.
131
131
Storage and compute capacity are added in discrete units known as partitions, and you must choose one field in your documents to be the partition key which maps each document to a partition.
132
132
The way partitions are managed is that each partition is assigned a roughly equal slice out of the range of partition key values; therefore you are advised to choose a partition key which is relatively random or evenly-distributed.
133
133
Otherwise, some partitions will see substantially more requests (hot partition) while other partitions see substantially fewer requests (cold partition), and this is to be avoided.
134
-
You may learn more about partitioning [here](/azure/cosmos-db/partitioning-overview).
134
+
You may learn more about partitioning [here](https://docs.microsoft.com/azure/cosmos-db/partitioning-overview).
135
135
136
136
## Examples
137
137
@@ -299,10 +299,10 @@ or contact [[email protected]][coc_contact] with any additional questions o
0 commit comments