Updating inverted file index using multi tier

You don't need to change anything to continue running your apps built with Document DB API. If you had a Document DB API account before, you now have a SQL API account, with no change to your billing.

The Azure Document DB service is now a part of the Azure Cosmos DB service and manifests itself in the form of the SQL API.

For more database questions, answers, and instructions for deploying and using this service, see the Azure Cosmos DB documentation page.

Applications built against Azure Document DB will run without any changes against Azure Cosmos DB SQL API.

In addition, Azure Cosmos DB supports the Graph API, Table API, Mongo DB API, and Cassandra API (Preview).

For more information, see the Microsoft Trust Center.

There is no limit to the total amount of data that a container can store in Azure Cosmos DB.

Azure Cosmos DB is a good choice for new web, mobile, gaming, and Io T applications where automatic scale, predictable performance, fast order of millisecond response times, and the ability to query over schema-free data is important.

Azure Cosmos DB lends itself to rapid development and supporting the continuous iteration of application data models.

A 1-RU throughput corresponds to the throughput of the GET of a 1-KB document.

Every operation in Azure Cosmos DB, including reads, writes, SQL queries, and stored procedure executions, has a deterministic RU value that's based on the throughput required to complete the operation.

For applications of any scale, you can benchmark individual requests to measure their RU values, and provision a container to handle the total of request units across all requests.

You can also scale up or scale down your container's throughput as the needs of your application evolve.

The APIs for a subset of models are available right now (SQL, Mongo DB, Table, and Graph APIs) and others specific to additional data models will be available in the future.

Tags: , ,