

MarkLogic and Microsoft Azure Cosmos DB compete in the database solutions market. MarkLogic has an upper hand in data integration with its search and indexing capabilities, whereas Cosmos DB excels in global distribution and serverless architecture.
Features: MarkLogic offers built-in search and indexing, handles both structured and unstructured data, and provides a flexible document model that doesn't require predefined schemas. Cosmos DB provides multi-model support, auto-scaling, and easy integration within the Microsoft ecosystem.
Room for Improvement: MarkLogic needs to address its steep learning curve, enhance modern development tools, and improve cloud-native capabilities. Users desire broader language support and better tools for beginners. Cosmos DB requires improved cost management, documentation clarity on request units, and enhanced cross-compatibility and query capabilities.
Ease of Deployment and Customer Service: MarkLogic allows deployment across public, private, and hybrid clouds with strong customer support though complex setups are primarily resolved internally. Cosmos DB primarily operates in the public cloud, integrating smoothly with Azure services, with customer service benefiting from Microsoft's vast resources.
Pricing and ROI: MarkLogic's pricing reflects its enterprise-grade capabilities, offering significant ROI by reducing development and infrastructure costs. In contrast, Cosmos DB's pricing model can be complex. However, with careful management of request units and leveraging of Azure services, users find it flexible and potentially cost-effective, especially for scalable, serverless applications.
For example, by using MarkLogic to handle semi-structured data directly, I have reduced ETL prep and transformation time by roughly 30 to 40 percent, freeing up engineers to focus on more value-added tasks instead of manual data cleaning.
This led to roughly a thirty to forty percent reduction in backend development effort.
In metrics, I think they save three or four hours now daily because we have really enabled them to have the data in real time instead of waiting for another day.
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.
I would rate customer support 10 out of 10.
Customer support for MarkLogic provides strong enterprise-level assistance through direct interactions.
MarkLogic support has enterprise-grade support, including ticketing systems and dedicated support channels for customers.
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.
Overall, it scales well, but getting the best performance depends on how well you design and configure it.
In production, when you get to know that your data is increasing and you need to add one more node, that is not easy and not straightforward.
MarkLogic is highly scalable and supports horizontal scaling through its clustered architecture.
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.
It supports ACID transactions, which ensure data consistency and reliability.
The built-in replication and failover features also help maintain uptime, ensuring the system stays operational even during maintenance or updates.
It can be used in different environments and is designed for enterprise use cases involving large volumes of data and complex queries.
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.
You do not need to worry about maintaining your own servers or provisioning your own servers. You simply log in and tell MarkLogic you want a certain number of clusters or nodes in a cluster and what cloud provider you want to use, then click okay, and they will build it for you.
There is a steep learning curve for this technology; XQuery and internal concepts such as indexing and CTS queries take time to learn compared to more common databases such as MongoDB.
Cost and licensing can be a consideration, especially for smaller teams or startups compared to open-source alternatives.
We must ensure data security remains the top priority.
You have to monitor the Request Units.
The dashboard could include more detailed RU descriptions, IOPS, and compute metrics.
The initial setup cost is moderate to high, mainly due to infrastructure provisioning, licensing costs, and initial configuration and onboarding efforts.
MarkLogic is quite costly, and they are looking to move away in the longer run for that reason.
MarkLogic follows a licensing model that can be relatively higher compared to open-source databases, making cost an important factor for smaller teams.
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.
It has a very rich search and cts APIs to build search engines on large datasets.
I personally appreciate the built-in search feature because it indexes all data immediately upon ingestion for rapid searching, so we can perform full-text, phrase, or geospatial searches.
MarkLogic provides a Google search-like capability, including full-text search, partial matching, and relevance scoring.
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.
| Product | Mindshare (%) |
|---|---|
| Microsoft Azure Cosmos DB | 6.2% |
| MarkLogic | 2.8% |
| Other | 91.0% |

| Company Size | Count |
|---|---|
| Small Business | 5 |
| Midsize Enterprise | 3 |
| Large Enterprise | 11 |
| Company Size | Count |
|---|---|
| Small Business | 33 |
| Midsize Enterprise | 22 |
| Large Enterprise | 58 |
MarkLogic offers robust capabilities for data storage and retrieval, supporting multiple formats like XML and JSON. Its built-in search and indexing facilitate rapid data querying, making it efficient for industries demanding quick data management solutions.
Boasting flexibility in data management, MarkLogic supports XML and JSON formats without strict schemas, integrating storage and search within a single platform to reduce complexity. This configuration enhances data handling, performance, and development speed. Industries like publishing, insurance, and healthcare benefit from its real-time processing, enabling tasks that range from creating PDFs to complex backend services. While users appreciate these capabilities, suggestions include interface modernization and better integration with tools like VS Code and IntelliJ.
What are MarkLogic's standout features?MarkLogic sees extensive use in publishing, insurance, and healthcare, where it aids in real-time processing, querying, and transformation of data. Its indexing and search capabilities allow efficient management of semi-structured data, smoothing tasks from document creation to backend solutions, without necessitating extensive migrations.
Microsoft Azure Cosmos DB offers scalable, geo-replicated, multi-model support with high performance and low latency. It provides seamless Microsoft service integration, benefiting those needing flexible NoSQL, real-time analytics, and automatic scaling for diverse data types and quick global access.
Azure Cosmos DB is designed to store, manage, and query large volumes of both unstructured and structured data. Its NoSQL capabilities and global distribution are leveraged by organizations to support activities like IoT data management, business intelligence, and backend databases for web and mobile applications. While its robust security measures and availability are strengths, there are areas for improvement such as query complexity, integration with services like Databricks and MongoDB, documentation clarity, and performance issues. Enhancements in real-time analytics, API compatibility, cross-container joins, and indexing capabilities are sought after. Cost management, optimization tools, and better support for local development also require attention, as do improvements in user interface and advanced AI integration.
What are the key features of Azure Cosmos DB?Industries use Azure Cosmos DB to support business intelligence and IoT data management, using its capabilities for backend databases in web and mobile applications. The platform's scalability and real-time analytics benefit sectors like finance, healthcare, and retail, where managing diverse datasets efficiently is critical.
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.