

MarkLogic and Redis compete in the database category, with MarkLogic offering advanced data management features and Redis providing high-speed in-memory data solutions. MarkLogic's advanced capabilities give it the upper hand in feature richness and data handling, while Redis has a clear advantage in performance speed and cost-efficiency for specific use cases.
Features: MarkLogic stands out with its ability to handle both structured and unstructured data, its strong ACID property compliance, and built-in powerful search and indexing capabilities. Redis, on the other hand, excels with its fast in-memory performance and supports various data types, making it suitable for caching and session management.
Room for Improvement: MarkLogic faces challenges with a steep learning curve, expensive licensing, and requires better language support and modern development tools. Redis can improve in memory management, monitoring tools, and enhancing persistence mechanisms for larger datasets.
Ease of Deployment and Customer Service: MarkLogic provides flexible deployment options across various cloud environments and offers responsive customer support. Redis emphasizes simplicity and easy integration, especially in high-performance contexts, but its customer support is not as robust as MarkLogic's.
Pricing and ROI: MarkLogic's high pricing is justified by its enterprise features and efficient integration capabilities, offering a good ROI for complex data needs. Redis offers a cost-effective solution with minimal licensing costs, being open-source and well-suited for organizations focused on optimizing memory and reducing overheads.
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.
It improved API latency from two seconds to 450 milliseconds for P99.
We reduced the database read load by around 30 to 40 percent and improved API response time by 20 to 30 percent, specifically for frequently accessed endpoints.
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.
The documentation and community support for Redis are very strong, making troubleshooting quicker.
Since Redis is quite stable and well-documented, we have not needed much support, but when required, the response has been helpful.
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.
Data migration and changes to application-side configurations are challenging due to the lack of automatic migration tools in a non-clustered legacy system.
I scale Redis horizontally using clustering and sharding, where data is distributed across multiple nodes to handle higher traffic and larger data sets.
With features such as clustering and replication, it can handle high traffic and a large database very effectively.
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.
Redis is fairly stable.
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.
Data persistence and recovery face issues with compatibility across major versions, making upgrades possible but downgrades not active.
Redis itself does not enforce consistency with the primary database, so developers need to carefully design cache invalidation strategies.
One issue is cache invalidation. Keeping cache data consistent with the source of truth can be tricky, especially in distributed systems.
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.
Since we use an open-source version of Redis, we do not experience any setup costs or licensing expenses.
The costs are primarily driven by memory consumption and cluster size, since Redis operates in-memory.
The pricing is reasonable for the performance provided.
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.
It functions similarly to a foundational building block in a larger system, enabling native integration and high functionality in core data processes.
First is its in-memory preference, as Redis is extremely fast, making it ideal for caching and session management where low latency is critical.
Real API latency improved from around two seconds to approximately 450 milliseconds for P99.
| Product | Mindshare (%) |
|---|---|
| Redis | 8.4% |
| MarkLogic | 2.8% |
| Other | 88.8% |

| Company Size | Count |
|---|---|
| Small Business | 5 |
| Midsize Enterprise | 3 |
| Large Enterprise | 11 |
| Company Size | Count |
|---|---|
| Small Business | 12 |
| Midsize Enterprise | 6 |
| Large Enterprise | 10 |
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.
Redis offers high-speed, in-memory storage, renowned for real-time performance. It supports quick data retrieval and is used commonly in applications like analytics and gaming.
Renowned for real-time performance, Redis delivers high-speed in-memory storage, making it a favorite for applications needing quick data retrieval. Its diverse data structures and caching capabilities support a broad array of use cases, including analytics and gaming. Redis ensures robust scalability with master-slave replication and clustering, while its publish/subscribe pattern renders it reliable for event-driven applications. The solution integrates smoothly with existing systems, minimizing performance tuning needs. Although documentation on scalability and security could be improved, Redis remains cost-effective and stable, commonly utilized in cloud environments. Enhancing integration with cloud services like AWS and Google Cloud and refining GUI may improve usability.
What are the key features of Redis?Redis finds application across industries for tasks like caching to improve application performance and speed, minimizing database load. It enables real-time processing for session storage, push notifications, and analytics. As a messaging platform, Redis handles high traffic and supports replication and clustering for cross-platform scalability.
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.