Microsoft Azure DocumentDB is a scalable, fully managed NoSQL database service designed to handle demanding workloads through a schema-free document data model.
It is tailor-made for applications requiring scale and performance, supporting JSON documents with rich querying capabilities. The service integrates easily with Azure's ecosystem, offering automatic indexing and multi-region replication, which may be appealing for businesses focused on global reach and real-time analytics. DocumentDB shifts the focus from infrastructure management to application development, highlighting its value for developers.
What are the key features of Microsoft Azure DocumentDB?Microsoft Azure DocumentDB is implemented in industries requiring high-throughput workloads and reliable data handling, such as finance, e-commerce, and IoT. By enabling consistent performance and secure data processing, it can meet market demands efficiently. In retail, DocumentDB handles real-time inventory management, while in finance, it supports transaction monitoring, reflecting its versatility across different sectors.
| Author info | Rating | Review Summary |
|---|---|---|
| Cloud Advisor at Digital Cognitive | 4.0 | I recommend Azure DocumentDB for medium companies due to its superior performance, speed, and elastic scaling, improving transactions and queries. Setup is easy, but it is expensive. I'd like columnar indexing and better analytics features. |
| Cloud Architect at a tech vendor with 10,001+ employees | 4.0 | I migrated from MongoDB to Azure DocumentDB for cloud modernization, finding it highly compatible, performant, and scalable, leading to a 30% cost saving. It's a stable solution, though documentation could improve. |
I usually recommend Microsoft Azure DocumentDB for medium-sized companies with a PC scale of less than 1,000 PCs, so it works pretty well with them.
It might be a little bit expensive for smaller companies; the tradeoff is between performance and cost, as a higher performance system can deliver what they want in a few seconds rather than a few minutes, which makes sense.
The impact of ACID transactions on my operations is that we have seen about 20 to 30% improvement in transactions from moving from PostgreSQL to Microsoft Azure DocumentDB.
The automated indexing of JSON data in Microsoft Azure DocumentDB has improved our query performance by almost 50%.
In Microsoft Azure DocumentDB, the features I find most valuable are its speed and performance.
I use its ACID transactions for data consistency.
One of the most appreciated aspects of Microsoft Azure DocumentDB is the elastic scaling feature. It has significantly helped manage business growth for two customers who have employed it, experiencing a dramatic rise in improvement.
Additionally, the automated indexing of JSON data improves query performance. Despite the cost issue associated with this feature, the advantages in speed and performance cannot be ignored.
To make Microsoft Azure DocumentDB closer to 10, I would like to see a columnar index as an additional feature.
I would also like to improve the analytics aspect of Microsoft Azure DocumentDB because it does not provide a lot of analytics; if that were available, it would be useful.
From a marketing perspective, one thing competitors could learn is the importance of incorporating a columnar index, as that would really help us.
I have been dealing with the tool for about three years now.
So far, I have not seen any issues with Microsoft Azure DocumentDB, although there are some issues with the SDK as REST APIs sometimes return an error, but I think that is more because of Azure than Microsoft Azure DocumentDB.
The elastic scaling feature in Microsoft Azure DocumentDB has helped manage business growth for two customers who have employed it, and they found a dramatic rise in improvement, but the cost is a big issue.
It is a bit expensive, especially concerning the elastic scale.
I used to work with Azure Database for PostgreSQL previously.
I switched purely because of performance.
The initial setup for Microsoft Azure DocumentDB is pretty straightforward.
It usually takes a few minutes.
If Microsoft Azure DocumentDB does not fit the budget, I would recommend PostgreSQL as the ultimate solution, but it does not really work as much as Microsoft Azure DocumentDB does; Microsoft Azure DocumentDB is very performant and does the work we want at a much lower cost, though elastic scale is the challenge.
We switched a few years ago because one of our customers recommended it, and we tried it out; we found it is working far better from a performance perspective.
About 80% of our customers have shifted to Microsoft Azure DocumentDB, while some are still using Azure Database for PostgreSQL.
I would not say that Microsoft Azure DocumentDB is the best option on the market now, but it is a choice for medium enterprises.
We have not integrated Microsoft Azure DocumentDB with Azure Analytics services, but that is a plan.
I have not done an assessment of the multi-region replication feature for maintaining high availability.
I would rate this review as an 8.
My main use case for Microsoft Azure DocumentDB is when we modernize applications that use MongoDB on-premise and move them to Azure using DocumentDB.
By doing this migration to Microsoft Azure DocumentDB, we avoid having to maintain servers, we have greater resilience in terms of the database and higher performance, where we can scale infinitely and have very good cost control and management.
Microsoft Azure DocumentDB allows us to scale quickly during peak load times, without having to provision the servers to the maximum peak as was done previously with on-premise servers.
The migration from MongoDB has not been complicated; it just needs a small adjustment.
I would highlight the very high compatibility with MongoDB, the high performance, the flexibility it offers, and the security as the best features offered by Microsoft Azure DocumentDB.
In fact, the software has been kept exactly as it was, almost 100% with no specific functionality that I found especially useful or any process that was simplified thanks to the compatibility with MongoDB.
Performing backups and restores with Microsoft Azure DocumentDB is very convenient.
Microsoft Azure DocumentDB has positively impacted my organization by allowing us to reduce database costs by 30%. I achieved that saving due to the scalability possibilities, which allow us not to have the maximum peak provisioned, but to always have it at the minimum necessary computing needs, scaling according to the load that the application is receiving.
I think perhaps in some aspects the documentation could be better, as well as the integration with Azure Backup to improve Microsoft Azure DocumentDB.
I have been using Microsoft Azure DocumentDB for about four years.
I consider Microsoft Azure DocumentDB a stable solution.
Microsoft Azure DocumentDB has responded well to my organization's growth needs in terms of scalability.
My experience with customer support for Microsoft Azure DocumentDB has been fine; I have not had any relevant experience with support.
I was previously using MongoDB before Microsoft Azure DocumentDB, and we decided to change because we wanted to migrate to the cloud that application which was on-premise.
We considered MongoDB Atlas before choosing Microsoft Azure DocumentDB.
I would advise others considering using Microsoft Azure DocumentDB that they consider it a good alternative to MongoDB.
I have seen a return on investment with Microsoft Azure DocumentDB, specifically a 30% saving in database costs.
My experience with the pricing, implementation cost, and licensing of Microsoft Azure DocumentDB is good overall.
I would rate this product an 8 out of 10.
