Try our new research platform with insights from 80,000+ expert users

Faiss vs InfluxDB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 23, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Faiss
Ranking in Open Source Databases
13th
Average Rating
8.0
Reviews Sentiment
8.8
Number of Reviews
2
Ranking in other categories
Vector Databases (5th)
InfluxDB
Ranking in Open Source Databases
12th
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
10
Ranking in other categories
Non-Relational Databases (3rd), Network Monitoring Software (53rd), IT Infrastructure Monitoring (46th), NoSQL Databases (5th)
 

Mindshare comparison

As of May 2025, in the Open Source Databases category, the mindshare of Faiss is 4.2%, up from 2.6% compared to the previous year. The mindshare of InfluxDB is 3.8%, up from 3.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Open Source Databases
 

Featured Reviews

Vasu Bansal - PeerSpot reviewer
Provides quick query search and has a big database
I did not face any issues integrating Faiss with other tools. I would recommend the solution to other users. Faiss has facilitated my AI-driven project very well. I recommend that other users use it for their AI projects because it provides quick query search and has a big database. Overall, I rate the solution nine and a half out of ten.
PedroCampos - PeerSpot reviewer
A powerful, lightweight time series database with a simple query language and easy setup
Influx has TICK Stack, which contains multiple services and multiple products that work together. InfluxDB is just a time series database, and it works really well. I haven't yet had the time to look into the new stack based on Influx 2.0, but currently, as a time series database, InfluxDB is working the way it is supposed to work. 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. I would also like to have high availability features, such as replication, active-active, etc. If they can put an extra plugin or service on top of it, it would be something interesting. I am not sure if they have high availability to make it data center-aware for clustering. For example, I am not sure whether you can have it at different locations with big clusters that are location-aware. Even in their documentation or presentation, they talk too little about high availability and extended clusters with different locations. They might already have it in the newer versions. We have Influx 1.8 in our production in the stage and internal workloads environments. The other products in their ecosystem, such as Chronograf, can be improved. Chronograf is a dashboarding or visualization layer product, and that, for sure, can be improved.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The product has better performance and stability compared to one of its competitors."
"I used Faiss as a basic database."
"The platform operates very quickly. It is easy to configure, connect, and query and integrates seamlessly with Grafana."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"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 are aggregating the data and integration with Graphana for monitoring."
"While I would rate InfluxDB a ten on a scale of one to ten, users should be thoughtful about matching the engine to their specific needs."
"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."
 

Cons

"It would be beneficial if I could set a parameter and see different query mechanisms being run."
"It could be more accessible for handling larger data sets."
"The solution's UI can be more user-friendly."
"The error logging capability can be improved because the logs are not very informative."
"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."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"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."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
 

Pricing and Cost Advice

"Faiss is an open-source solution."
"It is an open-source tool."
"We are using the open-source version of InfluxDB."
"InfluxDB recently increased its price. It is very expensive now."
"The tool is an open-source product."
"InfluxDB is open-source, but there are additional costs for scaling."
report
Use our free recommendation engine to learn which Open Source Databases solutions are best for your needs.
850,028 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
19%
Financial Services Firm
13%
Manufacturing Company
9%
Educational Organization
8%
Financial Services Firm
15%
Computer Software Company
13%
Manufacturing Company
9%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Faiss?
I used Faiss as a basic database.
What needs improvement with Faiss?
I didn't know what algorithm was being learned to fetch my query. It would be beneficial if I could set a parameter and see different query mechanisms being run. I can then compare the results to s...
What do you like most about InfluxDB?
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 ...
What needs improvement with InfluxDB?
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 coll...
What is your primary use case for InfluxDB?
I use the solution to store and manage data from various sensors in a production environment. I have developed a system where data from these sensors is communicated through an OPC UA receiver and ...
 

Comparisons

 

Overview

 

Sample Customers

1. Facebook 2. Airbnb 3. Pinterest 4. Twitter 5. Microsoft 6. Uber 7. LinkedIn 8. Netflix 9. Spotify 10. Adobe 11. eBay 12. Dropbox 13. Yelp 14. Salesforce 15. IBM 16. Intel 17. Nvidia 18. Qualcomm 19. Samsung 20. Sony 21. Tencent 22. Alibaba 23. Baidu 24. JD.com 25. Rakuten 26. Zillow 27. Booking.com 28. Expedia 29. TripAdvisor 30. Rakuten 31. Rakuten Viber 32. Rakuten Ichiba
ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
Find out what your peers are saying about Faiss vs. InfluxDB and other solutions. Updated: April 2025.
850,028 professionals have used our research since 2012.