I want to use a NoSQL database on Windows Azure and the data volume will be very large. Whether a Azure Table storage or a MongoDB database running using a Worker role can offer better performance and scalability? Has anyone used MongoDB on Azure using a Worker role? Please share your thoughts on using MongoDB on Azure over the Azure table storage.
相关问题
- MongoDB can not create unique sparse index (duplic
- running headless chrome in an microsoft azure web
- Docker task in Azure devops won't accept "$(pw
- Spring Data MongoDB - lazy access to some fields
- Register MicroServices in Azure Active Directory (
相关文章
- mongodb有没有什么办法禁止读取数据的时候进行缓存
- mongodb-aggregate聚合查询分组后如何获得多字段
- mongodb error: how do I make sure that your journa
- How to track MongoDB requests from a console appli
- MongoError: cannot infer query fields to set, path
- SQL Azure Reset autoincrement
- Pymongo $in Query Not Working
- How to cast Azure DocumentDB Document class to my
I have used both.
Azure Tables : dead simple, fast, really hard to write even simple queries.
Mongo : runs nicely, lots of querying capabilities, requires several instances to be reliable.
In a nutshell, if your queries are really simple (key->value), you must run a cost comparison (mainly number of transactions against the storage versus cost of hosting Mongo on Azure). I would rather go to table storage for that one. If you need more elaborate queries and don't want to go to SQL Azure, Mongo is likely your best bet.