Azure SQL成本与DocumentDB/CosmosDB成本之间的比较 [英] Comparison between Azure SQL cost vs DocumentDB/CosmosDB cost

问题描述

有人在Azure SQL成本与DocumentDB/CosmosDB成本之间进行了比较吗?我不清楚Azure CosmosDB成本中显示的RU.例如，1 TB db中的1个请求不能等于1 GB db中的1个请求.

Did anyone run any comparison between Azure SQL cost vs DocumentDB/CosmosDB cost? The RU that's presented in the Azure CosmosDB cost is not clear to me. E.g., 1 request in 1 TB db cannot be equal with 1 request in 1 GB db.

推荐答案

首先，您不能可靠地归纳关系Azure SQL成本和NoSQL CosmosDB成本之间的成本比较，因为它们是截然不同的东西.它们不可互换，它们将需要不同的数据建模，具体取决于计划的用法和所选的优化点.成本(开发费用+天蓝色账单+未来维护费用)

First, you cannot reliably generalize a comparison of cost between relational Azure SQL cost and NoSQL CosmosDB cost, because they are significantly different things. They are not interchangeable, they would require different data modelling depending on planned usage and chosen optimization points. The cost (development + azure bill + future maintenance) can vary a lot depending on your load and usage.

因此，通常的答案是相当无用的取决于".

查看有关 sql vs noSQL差异的更多信息，以及有关从sql切换到nosql的一些注意事项.

See more about sql vs noSQL differences, also some considerations about switching from sql to nosql.

更好地了解RU是什么的最好方法是通过生成实际数据并检查实际查询并从中推断目标成本进行实验.如果您通过id或选择性索引获得文档(并且永远不要在docDB中进行扫描)，那么RU成本很可能在GB与TB DB之间是相似的.

The best way to get a better understanding of what a RU is, is to experiment by generating realistic data and examining realistic queries and deduce target cost from it. If you get your document by id or from a selective-enough index (and you should never scan in docDB), then most likely the RU cost is similar in GB vs TB DB.

如果您没有时间测试真实的数据/查询，则可以使用 https://www .documentdb.com/capacityplanner .

If you lack the time to test with realistic data/queries, then you could play with https://www.documentdb.com/capacityplanner .

NB！请注意，这两种方法都要求您已经了解如何在NoSQL中布置数据. NoSQL文档不等同于SQL行-或-表.请参阅Ryan CrawCour，David Makogon提出的为NoSQL文档数据库建模数据"的观点了解在为noSQL设计时应考虑的内容.

NB! Please note that both approaches require you already have some idea how you would lay out your data in NoSQL. NoSQL documents are not equivalent to SQL rows -or- tables. See "Modeling Data for NoSQL Document Databases" persentation by Ryan CrawCour, David Makogon for ideas what to consider when designing for noSQL.

这篇关于Azure SQL成本与DocumentDB/CosmosDB成本之间的比较的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！