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 of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"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 solution is very powerful."
"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."
"The most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"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."
"One of the most valuable features is the ability to Text Search can be used anywhere and anytime."
"The aggregation framework is really good, allowing a developer to build very complex queries."
"Scalability seems good. I've never been even close to finding the limits. I've run a couple of notes of redundancy but I've never had any problems with scalability."
"The most valuable feature is the geometric information done with GeoJSON."
"It stores historical data with ease. For example, if you are a healthcare member, then you will have multiple records of visits to the doctors. To store such data in Oracle Database, you have to create many records. You might also have duplication problems because your records are going in again and again, because of which the data warehouse and the maintenance cost will be huge. MongoDB is comparatively lightweight. It is a JSON extract. Once you define a schema and extract it, you can push all the relationships in any way you want. It is easier to define and get different types of transactions into MongoDB. It is also easier to set it up as compared to other solutions. MongoDB is a NoSQL database, which means it is a document DB in which you can store documents that you created in BSON. It is pretty fast in response. It is faster than relational databases because it does not define any primary keys, secondary keys, tertiary keys, and all those kinds of things."
"Its flexibility, and cost. It is reasonably priced."
"It is very fast - faster than an SQL or MySQL Server."
"I find the integration with other tools very easy."
"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 solution doesn't have much of a user interface."
"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."
"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 solution's UI can be more user-friendly."
"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."
"The dashboard is an area of concern in the solution where improvements are required."
"It would help if MongoDB offered a light solution for small projects."
"I don't see a lot of areas that need improvement."
"It could be more stable. It would be better if it were more user-friendly like Oracle, which is very easy. For example, creating an index is simple in Oracle. In MongoDB, it's quite challenging to do that. Performance could be better. It's fast and good, but you cannot put every application that you would like to in MongoDB."
"There are some problems with bugs appearing in sharding when the data is too high."
"The transaction could use improvement. From MySQL, for example, you cannot create a transaction if you are reading and writing a document at the same time."
"It should have GUI for managing clusters. MongoDB needs a more powerful GUI to manage clusters and make switchovers. Currently, there is no good, free tool to check the replication to find out if there is a gap."
"Data encryption is possible using third-party tools but they should have their own encryption capability built-in to this solution."
InfluxDB is ranked 3rd in NoSQL Databases with 8 reviews while MongoDB is ranked 1st in NoSQL Databases with 68 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 Couchbase, whereas MongoDB is most compared with Couchbase, ScyllaDB, Oracle NoSQL, Cassandra 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.
