Technical Architect at a wholesaler/distributor with 1,001-5,000 employees
Real User
Top 5
Oct 21, 2026
When considering how Microsoft Azure DocumentDB can be improved, I see that there are definitely a couple of things we find out and feel could actually improve Microsoft Azure DocumentDB a little more. Some of the limitations I see that it does not have yet, when compared to MongoDB's ecosystem, is that it is still in an evolving state. Its identity is focused around MongoDB compatibility rather than being an Azure flagship, globally distributed NoSQL workforce, and another point would be that it should validate large scale and in-scale for performance characteristics for the specific workload rather than assuming parity with Cosmos DB NoSQL. Lastly, its actual architecture potentials are still emerging, so we cannot actually judge with already established architectures on MongoDB and others. Regarding the needed improvements around Microsoft Azure DocumentDB's architecture or performance, it is still evolving, and at this point in time, it would be very early to give this feedback. I want to see it after some adaptations. The improvements needed for Microsoft Azure DocumentDB that I have not mentioned yet include my observations that the maturity needs improvement, as it currently has a small community. When it grows to larger communities, real-time testing could happen, which may lead to advancements in real-time use cases and adaptations in Microsoft Azure DocumentDB, which would be great. Large-scale global deployment may require re-engineering for that reason. The enterprise support ecosystem still seems to be in acceleration and evolving situations. These are the couple of things I feel should be addressed for Microsoft Azure DocumentDB to have good support.
All Microsoft applications, whether database or analytics, are a little costlier compared to Google products, and this is a barrier that needs to be crossed so that all its applications become more affordable. For example, startups typically go for free tools. Microsoft should offer these products for free to startups or perhaps free for the first year or two years, so that startups can use these applications, and once they grow bigger and have larger revenue, they can purchase it at a reasonable cost. All Microsoft tools need to cut down on their price and have a better strategy around pricing for the masses. If you sell only to ten customers, your revenue is lesser, but if you give something for free to some customers, two years down the line they will purchase it. Microsoft Azure DocumentDB still needs the ability to connect to other analytics easily without any additional integrator. For example, if I can connect to Google Analytics or other analytics that are not Microsoft tools using this database, that would be a good source of revenue. If I have already purchased Google Analytics in my company and I need a database, and Microsoft Azure DocumentDB can very easily connect or integrate to my Google Analytics, I would not have to think twice. Cross-company application connectivity is something that needs to be worked on.
Cloud Advisor at Digital Cognitive Consultancy Services LLP
Real User
Top 5
Aug 14, 2026
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.
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....
When considering how Microsoft Azure DocumentDB can be improved, I see that there are definitely a couple of things we find out and feel could actually improve Microsoft Azure DocumentDB a little more. Some of the limitations I see that it does not have yet, when compared to MongoDB's ecosystem, is that it is still in an evolving state. Its identity is focused around MongoDB compatibility rather than being an Azure flagship, globally distributed NoSQL workforce, and another point would be that it should validate large scale and in-scale for performance characteristics for the specific workload rather than assuming parity with Cosmos DB NoSQL. Lastly, its actual architecture potentials are still emerging, so we cannot actually judge with already established architectures on MongoDB and others. Regarding the needed improvements around Microsoft Azure DocumentDB's architecture or performance, it is still evolving, and at this point in time, it would be very early to give this feedback. I want to see it after some adaptations. The improvements needed for Microsoft Azure DocumentDB that I have not mentioned yet include my observations that the maturity needs improvement, as it currently has a small community. When it grows to larger communities, real-time testing could happen, which may lead to advancements in real-time use cases and adaptations in Microsoft Azure DocumentDB, which would be great. Large-scale global deployment may require re-engineering for that reason. The enterprise support ecosystem still seems to be in acceleration and evolving situations. These are the couple of things I feel should be addressed for Microsoft Azure DocumentDB to have good support.
All Microsoft applications, whether database or analytics, are a little costlier compared to Google products, and this is a barrier that needs to be crossed so that all its applications become more affordable. For example, startups typically go for free tools. Microsoft should offer these products for free to startups or perhaps free for the first year or two years, so that startups can use these applications, and once they grow bigger and have larger revenue, they can purchase it at a reasonable cost. All Microsoft tools need to cut down on their price and have a better strategy around pricing for the masses. If you sell only to ten customers, your revenue is lesser, but if you give something for free to some customers, two years down the line they will purchase it. Microsoft Azure DocumentDB still needs the ability to connect to other analytics easily without any additional integrator. For example, if I can connect to Google Analytics or other analytics that are not Microsoft tools using this database, that would be a good source of revenue. If I have already purchased Google Analytics in my company and I need a database, and Microsoft Azure DocumentDB can very easily connect or integrate to my Google Analytics, I would not have to think twice. Cross-company application connectivity is something that needs to be worked on.
I think perhaps in some aspects the documentation could be better, as well as the integration with Azure Backup to improve Microsoft Azure DocumentDB.
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.