

InfluxDB and MarkLogic compete in the database space. InfluxDB appears to have the upper hand for time-series data management with effective tools for monitoring and alerting, while MarkLogic demonstrates strength in handling unstructured data and enterprise integration.
Features: InfluxDB excels with high-write loads, real-time analytics, and open-source integrations, making it ideal for time-series data. MarkLogic stands out for its capabilities in data integration, ACID transactions, and semantic search, suitable for businesses requiring comprehensive analytics in complex environments.
Ease of Deployment and Customer Service: InfluxDB provides a straightforward deployment process, particularly in cloud environments, with strong community support. MarkLogic, while requiring more specialized knowledge, offers robust enterprise support, underscoring its suitability for large-scale deployments.
Pricing and ROI: InfluxDB offers a cost-effective solution, appealing to startups and mid-sized companies with low initial costs and quick ROI for time-series applications. MarkLogic's higher price reflects its extensive features, offering long-term ROI for large enterprises needing complex data integrations.
These improvements translated into both cost savings and better service reliability, directly impacting business outcomes.
It simplifies processes and reduces the need for additional employees.
It has reduced a lot of time in terms of troubleshooting because the way it produces the data on a time-series basis allows me to collect and store the data for future reference.
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.
They get on a call, resolve issues, and handle everything efficiently.
The InfluxDB support team was knowledgeable and helped us troubleshoot complex problems efficiently.
Obtaining that quantity of data directly from InfluxDB is quite challenging, and that is why we ask for help from the InfluxDB team to retrieve the data to avoid timeouts and those kinds of issues.
I would rate customer support 10 out of 10.
I would rate MarkLogic's customer support an eight due to its responsiveness, especially for higher priority issues.
Once the system was set up, it was quite stable, and most issues could be handled internally.
The main challenge with InfluxDB, which is common with all databases, was handling very high throughput systems and high throughput message flow.
It can handle large volumes of time-series data and with high ingestion rates, making it suitable for enterprise-scale deployments.
We’ve scaled on volume with seven years of continuous data without performance degradation.
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.
The system handles this increase in XML workloads well, and flexible indexing helps maintain query performance even as datasets expand.
It serves as the backbone of our application, and its stability is crucial.
We have used it to support mission-critical systems with continuous data ingestion and real-time analytics.
It is very stable, with no reliability or downtime in InfluxDB.
The built-in replication and failover features also help maintain uptime, ensuring the system stays operational even during maintenance or updates.
We used to have production issues, mainly due to MarkLogic failures.
InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying.
Having a SQL abstraction in InfluxDB could be beneficial, making it more accessible for teams that prefer querying with SQL-style syntax.
It could include automated backup and a monitoring solution for InfluxDB or a script developed by a REST API.
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.
Tooling and ecosystem support do not feel as rich as mainstream databases such as Hive or SQL servers in terms of connectors and integration or community resources.
A better UI with more features on it, something user-friendly, would be beneficial.
We use the open-source version of InfluxDB, so it is free.
I find the cloud version pricing of InfluxDB reasonable, and for the on-premises solution we use in our service, we need to purchase licenses.
Pricing is based on data volume, retention, and features, which really makes it scalable but requires careful planning to avoid unexpected costs.
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.
I believe the pricing and licensing are definitely on the higher side compared to open-source alternatives.
The most important feature for us is low latency, which is crucial in building a high-performance engine for day trading.
InfluxDB’s core functionality is crucial as it allows us to store our data and execute queries with excellent response times.
It helps me maintain my solution easily because it is very reliable, so we didn't face any performance issues or crashes regarding our queries; we can get the results very fast.
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.
Its flexible schema and indexing capabilities allow me to index anything, including nested elements, which speeds up queries and reduces the need for custom code.
| Product | Mindshare (%) |
|---|---|
| InfluxDB | 5.2% |
| MarkLogic | 2.9% |
| Other | 91.9% |

| Company Size | Count |
|---|---|
| Small Business | 9 |
| Midsize Enterprise | 5 |
| Large Enterprise | 9 |
| Company Size | Count |
|---|---|
| Small Business | 5 |
| Midsize Enterprise | 3 |
| Large Enterprise | 11 |
InfluxDB offers efficient time series data handling with fast writes, optimized storage, and seamless Grafana integration, making it ideal for high-volume applications like crypto trading and real-time monitoring. Its SQL-like query language and cloud-based options enhance user experience and system scalability.
InfluxDB stands out with its ability to handle high-volume time series data efficiently, thanks to fast data writes and efficient compression. It is highly scalable, providing clustering features for improved performance management. Integration with Grafana enhances visualization, making it easier to analyze complex data through a user-friendly SQL-like query language. Real-time monitoring, historical data access, and proactive alerts enhance system reliability. Its cloud offering simplifies maintenance and operations, making it attractive for users seeking an efficient time series database.
What are the key features of InfluxDB?InfluxDB is applied extensively in industries handling high-volume data needs. For sensor data storage in production environments, it offers reliable performance. Its role in server management metrics and performance monitoring is crucial for maintaining optimal operations. In crypto market data collection, it supports fast-paced trading environments. Industries use it for real-time tracking, like maritime vessel monitoring, leveraging its rapid data handling and visualization capabilities. Its applications also extend to IoT environments, API performance tracking, HVAC systems, and log aggregation, often integrating with Prometheus, Docker, and AWS to enhance system capabilities.
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.
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.