I have 2 questions.

1. Can anyone briefly explain about Request units?

2. Is there any option to add or remove request units?

Thanks.

Hi,

Unlike key-value NoSQL stores which offer simple GET and PUT operations, DocumentDB allows for a richer set of database operations including relational and hierarchical queries with UDFs, stored procedures and triggers all operating on the documents within a database collection. The cost associated with each of these operations will vary based on the CPU, IO and memory required to complete the operation. Instead of thinking about and managing hardware resources, you can think of a Request Unit (RU) as a single measure for the resources required to perform various database operations and service an application request. Each collection comes with a defined amount of Request Units of throughput. If your application requires a higher level of throughput, you can purchase additional collections.

You can scale up or scale down the number of collections in your database by using the slider in the DocumentDB blade of the Azure Portal or through one of the Azure DocumentDB SDKs.

For more information, refer this link:
http://azure.microsoft.com/en-in/pricing/details/documentdb/

Regards,
Azam khan

Hi,

Unlike key-value NoSQL stores which offer simple GET and PUT operations, DocumentDB allows for a richer set of database operations including relational and hierarchical queries with UDFs, stored procedures and triggers all operating on the documents within a database collection. The cost associated with each of these operations will vary based on the CPU, IO and memory required to complete the operation. Instead of thinking about and managing hardware resources, you can think of a Request Unit (RU) as a single measure for the resources required to perform various database operations and service an application request. Each collection comes with a defined amount of Request Units of throughput. If your application requires a higher level of throughput, you can purchase additional collections.

You can scale up or scale down the number of collections in your database by using the slider in the DocumentDB blade of the Azure Portal or through one of the Azure DocumentDB SDKs.

For more information, refer this link:
http://azure.microsoft.com/en-in/pricing/details/documentdb/

Regards,
Azam khan

• Marked as answer by Richetbracy 15 hours 5 minutes ago

Hi,

Unlike key-value NoSQL stores which offer simple GET and PUT operations, DocumentDB allows for a richer set of database operations including relational and hierarchical queries with UDFs, stored procedures and triggers all operating on the documents within a database collection. The cost associated with each of these operations will vary based on the CPU, IO and memory required to complete the operation. Instead of thinking about and managing hardware resources, you can think of a Request Unit (RU) as a single measure for the resources required to perform various database operations and service an application request. Each collection comes with a defined amount of Request Units of throughput. If your application requires a higher level of throughput, you can purchase additional collections.

You can scale up or scale down the number of collections in your database by using the slider in the DocumentDB blade of the Azure Portal or through one of the Azure DocumentDB SDKs.

For more information, refer this link:
http://azure.microsoft.com/en-in/pricing/details/documentdb/

Regards,
Azam khan

• Marked as answer by Richetbracy Monday, July 06, 2015 4:12 PM