We performed a comparison between InfluxDB and Vertica based on real PeerSpot user reviews.
Find out in this report how the two NoSQL Databases solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."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."
"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."
"Its analytics has enabled Pythian's clients to get the business insights as quick as they wanted. Its lower maintenance has also improved the ROI."
"The feature I like best is performance. We use Red Tool and Red Job for the data warehouse and reporting. It's perfect. Performance is good, and it can return ad hoc queries very quickly. Of course, it's a cluster, so it's easy to scale."
"The solution has great capabilities. The tool that instructs the internal database forward is easy to use and is very powerful."
"DBAs don’t need to add a partition every month/quarter like with other DBs."
"Vertica is easy to use and provides really high performance, stability, and scalability."
"Vertica is a great product because customers can compress and code data. The infrastructure that data warehouse solutions need is a commodity server so that customers don't have to invest in infrastructure."
"Its projections and encoding are excellent tools for tuning large volumes."
"I enjoy the cybersecurity and backup features."
"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 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."
"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."
"The error logging capability can be improved because the logs are not very informative."
"The solution's UI can be more user-friendly."
"One feature, which has really benefited us, is the scalability offered by Vertica as it has enabled Pythian's clients to manage data with agility."
"Documentation has become much better, but can always use some improvement."
"Very bad support, I would rate it two out of 10."
"They could improve on customer service."
"Monitoring tools need to be lightweight. They should not take up heavy resources of the main server."
"The geospatial functionality could be designed better."
"I believe the installation process could be streamlined."
"I think they need an easy client so that you can write queries easily, but it's not necessarily a weak point. I think some users would need them."
InfluxDB is ranked 3rd in NoSQL Databases with 8 reviews while Vertica is ranked 4th in Data Warehouse with 83 reviews. InfluxDB is rated 7.6, while Vertica 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 Vertica writes " A user-friendly tool that needs to improve its documentation part". InfluxDB is most compared with MongoDB, Cassandra, Netdata, ScyllaDB and Cloudera Distribution for Hadoop, whereas Vertica is most compared with Snowflake, SQL Server, Amazon Redshift, Teradata and Oracle Exadata. See our InfluxDB vs. Vertica 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.