Cloudera Distribution for Hadoop and Microsoft Azure Cosmos DB compete in the realm of big data and cloud services. Based on the analysis, Cosmos DB seems to have the upper hand in deployment and accessibility, whereas Cloudera excels in security and management capabilities.
Features: Cloudera Distribution for Hadoop provides features like comprehensive cluster management, robust enterprise security, and seamless integration with Hadoop ecosystem tools such as Cloudera Manager, Impala, and Sentry. In contrast, Microsoft Azure Cosmos DB is acclaimed for its stability and ease of use in cloud environments, showcasing features like TTL, geo-replication, and multi-model support.
Room for Improvement: Cloudera Distribution for Hadoop users express challenges with HBase stability, Spark integration, and licensing complexity. There's also a noted need for better documentation and support for external integrations. Microsoft Azure Cosmos DB, on the other hand, faces critique over its complex pricing model, limitations in cross-container queries, and calls for improved analytics capabilities.
Ease of Deployment and Customer Service: Cloudera Distribution for Hadoop targets primarily on-premises deployments, requiring manual setup and specialized skills, with mixed reviews on customer service. Microsoft Azure Cosmos DB is optimized for the cloud, facilitating easier deployment and scalability, and generally receives positive feedback on customer service despite some issues with complex queries.
Pricing and ROI: Cloudera Distribution for Hadoop faces criticism for its high licensing costs, making it more suitable for large enterprises, while smaller companies find it expensive. Microsoft Azure Cosmos DB utilizes a pay-as-you-go model, offering flexible pricing that can become costly with heavy usage. This model demands careful cost management for effective ROI.
Getting an MVP of that project would have taken six to eight months, but because we had an active choice of using Azure Cosmos DB and other related cloud-native services of Azure, we were able to get to an MVP stage in a matter of weeks, which is six weeks.
You can react quickly and trim down the specs, memory, RAM, storage size, etc. It can save about 20% of the costs.
When I have done comparisons or cost calculations, I have sometimes personally seen as much as 25% to 30% savings.
The technical support is quite good and better than IBM.
Premier Support has deteriorated compared to what it used to be, especially for small to medium-sized customers like ours.
The response was quick.
I would rate customer service and support a nine out of ten.
The system scales up capacity when needed and scales down when not in use, preventing unnecessary expenses.
We like that it can auto-scale to demand, ensuring we only pay for what we use.
We have had no issues with its ability to search through large amounts of data.
We have multiple availability zones, so nothing goes down.
Azure Cosmos DB would be a good choice if you have to deploy your application in a limited time frame and you want to auto-scale the database across different applications.
I would rate it a ten out of ten in terms of availability and latency.
Integrating with Active Directory, managing security, and configuration are the main concerns.
We must ensure data security remains the top priority.
You have to monitor the Request Units.
The first one is the ability to assign role-based access control through the Azure portal for accounts to have contributor rights.
It can be deployed on-premises, unlike competitors' cloud-only solutions.
Initially, it seemed like an expensive way to manage a NoSQL data store, but so many improvements that have been made to the platform have made it cost-effective.
Cosmos DB is expensive, and the RU-based pricing model is confusing.
Cosmos DB is great compared to other databases because we can reduce the cost while doing the same things.
This is the only solution that is possible to install on-premise.
The most valuable feature of Microsoft Azure Cosmos DB is its real-time analytics capabilities, which allow for turnaround times in milliseconds.
Performance and security are valuable features, particularly when using Cosmos DB for MongoDB emulation and NoSQL.
The performance and scaling capabilities of Cosmos DB are excellent, allowing it to handle large workloads compared to other services such as Azure AI Search.
Microsoft Azure Cosmos DB is a globally distributed, multi-model database service providing scalability, user-friendliness, and seamless integration, suitable for managing large volumes of structured and unstructured data across diverse applications.
Azure Cosmos DB is renowned for its scalability, stability, and ease of integration, offering robust support for multiple data models and APIs. Its capacity for handling unstructured data efficiently and providing real-time analytics makes it ideal for applications requiring high performance and global distribution. With features like automatic failover and integration with Microsoft products, users benefit from cost optimization and secure data handling. Enhancement opportunities include simplifying queries, improving documentation, and expanding backup and analytics functionalities.
What are the most important features of Microsoft Azure Cosmos DB?Azure Cosmos DB is frequently used in sectors like web, mobile, IoT, and analytics. It supports applications as a key-value store, processes real-time data, and enables global scalability with low-latency access. Its big data management capabilities and integration with Azure services enhance its utility across industries.
We monitor all NoSQL Databases reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
