We compared MongoDB and InfluxDB based on our user's reviews in several parameters.
MongoDB offers flexibility, scalability, and robust replication capabilities, while customer service and support are highly praised. InfluxDB excels in handling large volumes of data and real-time monitoring, with a focus on query performance and storage optimization. Both products receive positive feedback on pricing, setup costs, and ROI, with InfluxDB offering competitive pricing options and transparent licensing terms. The key differences lie in MongoDB's document-oriented data model and powerful query language, contrasted with InfluxDB's emphasis on time series data management and integration options.
Features: The valuable features of MongoDB include flexibility, scalability, efficient handling of large data, document-oriented data model, support for multiple data structures, powerful query language, and robust replication and high availability capabilities. In contrast, InfluxDB stands out for its ability to handle large volumes of data, real-time monitoring capabilities, ease of use and scalability. It offers efficient data storage and querying capabilities, supports different data types, continuous queries, and provides robust platform and integration options for time series data management.
Pricing and ROI: The setup cost for MongoDB has received feedback, while InfluxDB is praised for its reasonable setup costs and transparent pricing. Users have found the setup cost for InfluxDB to be straightforward, simplifying the overall process. InfluxDB's licensing terms are also appreciated for their flexibility and ease of use., MongoDB provided a positive ROI based on user feedback. InfluxDB had a highly positive ROI, praised for its fast data storage, scalability, and ease of use.
Room for Improvement: MongoDB users have highlighted areas for improvement, including performance optimization, data replication, query language flexibility, and user-friendly database management tools. InfluxDB users seek improvements in query performance, data storage optimization, documentation, scalability, and support services.
Deployment and customer support: Based on user feedback, MongoDB users mentioned varying durations for implementation, with some indicating separate timeframes for deployment and setup. InfluxDB users also mentioned separate timeframes, but it is important to consider the context of usage for accurate evaluation., MongoDB's customer service is highly valued for its timely assistance and knowledgeable responses, while InfluxDB's support is praised for its promptness and reliability. Both products have received positive reviews for their customer service.
The summary above is based on 34 interviews we conducted recently with MongoDB and InfluxDB users. To access the review's full transcripts, download our report.
"InfluxDB is a database where you can insert data. However, it would be best if you had different components for alerting, data sending, and visualization. You need to install tools to collect data from servers. It must be installed on Windows or Linux servers. During installation, ensure that the configuration file is correct to prevent issues. Once data is collected, it can be sent to InfluxDB. For visualization, you can use open-source tools like Grafana."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"InfluxDB's best feature is that it's a cloud offering. Other good features include its time-series DB, fast time-bulk queries, and window operations."
"In our case, it started with a necessity to fill the gap that we had in monitoring. We had very reactive monitoring without trend analysis and without some advanced features. We were able to implement them by using a time series database. We are able to have all the data from applications, logs, and systems, and we can use a simple query language to correlate all the data and make things happen, especially with monitoring. We could more proactively monitor our systems and our players' trends."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"The solution is very powerful."
"The user interface is well-designed and easy to use. It provides a clear overview of the data, making it simple to understand the information at hand."
"The most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"It is convenient to use because we can do manipulations with the JSON data that we get. There are also a lot of joins and associations with MongoDB, which makes it easy to use for us."
"The most valuable feature is that you can store unstructured data, which is helpful when you don't know what the best structure should be and you cannot use a relational database because of that."
"The Dynamic Application is a valuable feature."
"It's easy to add and remove things in MongoDB. You can alter the tables. MongoDB is faster at reading, slower at writings."
"Easier to maintain the data with its document-based storage."
"We haven't had any issues with stability."
"One of the first things I noticed when I had my first experience with MongoDB was how easy it was to use. I was expecting more difficulties or at least some challenges, but it was very, very easy to use. It's great technology, performs well, and is very convenient."
"It is very easy to create a MongoDB cluster. You can deploy three nodes in one hour. You can do small configurations to enable routing. It is easy to implement."
"The solution doesn't have much of a user interface."
"InfluxDB cannot be used for high-cardinality data. It's also difficult and time-consuming to write queries, and there are some issues with bulk API."
"InfluxDB is generally stable, but we've encountered issues with the configuration file in our ticket stack. For instance, a mistake in one of the metrics out of a hundred KPIs can disrupt data collection for all KPIs. This happens because the agent stops working if there's an issue with any configuration part. To address this, it is essential to ensure that all configurations are part of the agent's EXE file when provided. This makes it easier to package the agent for server installation and ensures all KPIs are available from the server. Additionally, the agent cannot encrypt and decrypt passwords for authentication, which can be problematic when monitoring URLs or requiring authentication tokens. This requires additional scripting and can prolong service restart times."
"The solution's UI can be more user-friendly."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"InfluxDB can improve by including new metrics on other technologies. They had some changes recently to pool data from endpoints but the functionality is not good enough in the industry."
"The error logging capability can be improved because the logs are not very informative."
"In terms of features that I would like to see or have, in the community version, some features are not available. I would like to have clustering and authentication in the community version."
"The user interface is not as friendly as Oracle, which is something that can be improved."
"It would help if MongoDB offered a light solution for small projects."
"A normal Oracle or database tester will take some time to gear up to MongoDB because the way of writing queries is different in MongoDB. There should be some kind of midway where a person who is coming from an Oracle background can write a query and get a response by using something like a select * statement or other such things. There should be some way for MongoDB to interpret these commands rather than making a person learn MongoDB commands and writing them. I struggled while writing these MongoDB commands. I had not seen such queries before. It was pretty difficult to get them. This is one of the areas where it would help from the improvement standpoint."
"I suppose it could be a little more secure."
"We find it difficult to incorporate MongoDB in some projects."
"It has certain limitations when it comes to handling hierarchical data, enforcing relationships, and performing complex joins, which should be taken into account when designing databases for applications with intricate data requirements."
"They could improve the UI and the analytics part."
"I think it would be good to have more search options such as an index resource. This will provide more options and resources to do advance searches."
InfluxDB is ranked 3rd in NoSQL Databases with 8 reviews while MongoDB is ranked 1st in NoSQL Databases with 70 reviews. InfluxDB is rated 7.6, while MongoDB is rated 8.2. The top reviewer of InfluxDB writes "A powerful, lightweight time series database with a simple query language and easy setup". On the other hand, the top reviewer of MongoDB writes "Lightweight with good flexibility and very fast performance for searching data". InfluxDB is most compared with Cassandra, Netdata, ScyllaDB, Cloudera Distribution for Hadoop and SingleStore, whereas MongoDB is most compared with Couchbase, ScyllaDB, Cassandra, Oracle NoSQL and Oracle Berkeley DB. See our InfluxDB vs. MongoDB report.
See our list of best NoSQL Databases vendors.
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.