Microsoft Azure Cosmos DB and ClickHouse compete in the database solutions category. ClickHouse seems to have the upper hand due to its powerful features and performance capabilities.
Features: Microsoft Azure Cosmos DB users find its global distribution, multi-model capabilities, and broad integrations valuable. ClickHouse users value its fast analytical queries, efficient columnar storage, and powerful data processing speed.
Room for Improvement: Microsoft Azure Cosmos DB could improve cost management, query performance, and optimize costs further. ClickHouse could enhance its documentation, provide more connectors, and address usability challenges.
Ease of Deployment and Customer Service: Microsoft Azure Cosmos DB is known for its seamless cloud integration and extensive customer support. ClickHouse users face a steeper learning curve but benefit from robust performance once deployed.
Pricing and ROI: Microsoft Azure Cosmos DB users mention high setup costs but see long-term ROI value. ClickHouse users find higher upfront costs justified by substantial performance returns.
The response was quick.
I would rate customer service and support a nine out of ten.
Our experience with technical support has always been great.
SQL Server is very portable. You can even install it on your machine. That is the number one thing that is missing in Azure Cosmos DB.
The first one is the ability to assign role-based access control through the Azure portal for accounts to have contributor rights.
Complex cross-partition querying, and BI/analytical tasks often necessitate moving data to other solutions like Fabric and Azure AI Search.
Its scalability deserves a ten out of ten.
In cases where it has to automatically scale up to your maximum, that happens very quickly.
With so many improvements to the platform and ways to optimize, in our big enterprise deployments, Microsoft Azure Cosmos DB tends to be one of the least expensive services even though it gets a lot of use.
Microsoft Azure Cosmos DB is highly stable and built for stability and scalability.
The solution is very stable, and I cannot recall a time when Azure Cosmos DB let us down.
After migrating applications from an SQL database to Azure Cosmos DB, the change in the organization is massive.
The most valuable feature of Microsoft Azure Cosmos DB is its ability to handle concurrency and consistency.
While we don't utilize every feature, auto-scaling has been invaluable for optimizing both cost and performance on our platform daily.
ClickHouse is the fastest and most resource efficient open-source database for real-time apps and analytics.
ClickHouse supports all the data sources you need to power your apps and use cases that require exceptional performance.
ClickHouse uses all available system resources to their full potential to process each analytical query as fast as possible.
ClickHouse runs on every environment, whether it’s on your machine or in the cloud.
Azure Cosmos DB is a fully managed NoSQL and vector database service built for AI-powered apps at any scale. It fuels apps with high-performance, distributed computing over massive volumes of NoSQL and vector data. Developers can start small and pay for only what they use with serverless computing, and enhance the solution seamlessly with unlimited dynamic autoscale, SLA-backed 99.999 percent availability and <10ms latency. Azure Cosmos DB lets developers build applications with the languages and frameworks of their choice, such as Python, Node.js, and Java. These unique benefits make Azure Cosmos DB a great fit for responsive, high-performance customer-facing apps that are secure and highly available. Some popular use cases for Azure Cosmos DB are AI assistants, real-time transactional applications, IoT and smart products, personalization and recommendations, as well as SaaS applications.
We monitor all Vector 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.