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

Faiss vs MySQL comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Faiss
Ranking in Open Source Databases
14th
Average Rating
8.0
Number of Reviews
2
Ranking in other categories
Vector Databases (3rd)
MySQL
Ranking in Open Source Databases
1st
Average Rating
8.2
Number of Reviews
147
Ranking in other categories
Relational Databases Tools (4th)
 

Featured Reviews

Vasu Bansal - PeerSpot reviewer
May 7, 2024
Provides quick query search and has a big database
I made some vectors for my data set. I added them and got the embeddings from Hugging Face. I made a query key-value pair for Faiss. When you want to do a query search on it, you call Faiss and send your query within it I used Faiss as a basic database. I didn't know what algorithm was being…
Patryk Golabek - PeerSpot reviewer
Aug 5, 2020
Good beginner base but it should have better support for backups
As for what can be improved, right now we don't use the MySQL cluster. There is a MySQL cluster that you can run in a standalone mode, like a single database or you can do it in a cluster master-slave implementation. The cluster is not the best when it comes to MySQL. That's why we switched to MariaDB. For that simple reason that the cluster there is better. It's more manageable and it's easier to work with. We decide what to use depending on the needs. For example, if we need to mount something in a cluster mode, we use MariaDB, which again, is a Dockerized solution with a Helm chart as well, and it's very easy for us to deploy and manage, and also to scale when you just increase the number of slave versions. So MySQL doesn't have that great support when it comes to clusters. You can definitely use MySQL for that too, both support clustering, but the MariaDB is better. Additional features that I would like to see included in the next release of this solution include better support for backups. Because if you go with the MySQL Percona version, it gives you the tools to back it up securely. The vanilla version of MySQL doesn't have that. It actually does have it, but it is just really poorly executed. I would improve the backup system as well as the encryption. To make it smoother right now takes too much work. It should be a little bit smoother to backup the encrypted data the way you want it and have the ability to push it anywhere you want. That is not part of it right now. Now it is a database, so you don't know what you're going to do with it. It's difficult. You're just going to come up with solutions. But I think you can generalize here and come up with really simple solutions, which we have already in MySQL. That's probably the one thing that I would try and push right now for people to switch. But people are still not biting, because if you go with the managed version, then all the backups are taken care of for you by Amazon or Google or Microsoft. Then you really don't care. But for us, since we're doing it locally, self-hosted, we would like to have better tools for locking up the data. Right now, one aspect that is also linked to backups is running things in a crosscheck with semi-managed solutions. This requires a bit of a context. Since we're running things within the clustered communities, we're kind of pushing the Cloud into the cluster. We also want to push some of the tools for the database into a cluster, as well. So these are what we call Kubernetes operators. And there's MySQL operators that were first developed by the community. Those kind give you the ability to backup data within the cluster. So now you have a fully managed solution running from your cluster. These are called MySQL Kubernetes operators. We are looking into those right now to upgrade our solution, which would mean that we can just execute our backup natively within Kubernetes, not via special scripts. This would make it much easier to actually deal with any kind of MySQL issues within the cluster, because it would be cluster-native. That's what the operators are for. I think Oracle just created a really good one. It surprised me that they have this. It's not because of Oracle, but they got pushed by the community and actually created the MySQL Operator for Kubernetes, and that's what we're moving towards. This is going to give you an ability to have a cloud-managed solution within the cluster. And then you can ask the MySQL Operator for the database. They'll partition the database and give it to you. So it will change the nature from you deploying it to you just asking the cluster to give you a database. It's a fully managed solution right from the cluster. So that's what we're heavily looking into right now. We'll be switching to using Kubernetes MySQL Operators. It's a high-availability cluster running within the Kubernetes cluster. Right now we're pretty good with that. It's working fine. We're trying to find some time to actually release that globally everywhere. That's where I am right now. But in terms of technology, if you give up Oracle, you just go to a MySQL operator. That's the one we're using, what we're actually looking at - to create, operate and scale mySQL and sell it within the cluster. This idea of having a cognitive MySQL becomes much easier to manage within the cluster, as well. So you don't have to go with the cloud solution with AWS or Google cloud or Amazon MySQL or the Microsoft version. The Oracle SuperCluster is the Oracle MySQL operator. That's what we we are looking into a lot right now. Mainly because it does backups on demand - it's so easy to backup. You can just tell Kubernetes to backup and you don't have to run special scripts or special extra software or codes to back it up. You can make the backup as you would do anything else. Send a backup or some other data source or insert an Elasticsearch into it here. Just say "Kubernetes, back it up" and you know Oracle has this adapters within the cluster to back it up for you taking increments or different companies. So that makes it really nice and easy to use and to deploy. With that kind of solution you can ask to class or petition the database how you want. So again, it changed the nature of the kind of push-to-pull second nature system. Are you pushing your containers to a cluster? You just say cluster, "give me a database" and the class gives you the base partition database, creates a database in a secure manner, gives the connection to the database, and you're done. Then you can back it up on a schedule on to any backup switches. It's much easier. So once this goes, it is going to be widely adopted, which it should be. But I think people might not have the tech skills right now. But once it's adaptive, maybe in a few more months, it's going to be the number one solution for everybody. In terms of what I'd like to see in the next release, one thing that's always missing is dash boarding. There's no real BI tool for MySQL, like there is in Yellowfin and all the different tools that you get. They all have MySQL connectors, but there's no specific BI tool for MySQL. Open source projects have sprung up, but they're more general purpose, like Postgress, a MySQL kind of database, a relational database. I don't see any really nice tool like Cabana for elastic searches that I can tell clients to use because it would be too technical for them. They would have to have more technical engagement with writing the course, drag and drop, and creating a graph like in Power BI where you just connect with DIA. So I'd like to see the grab and drag and drop tables, nice beautiful graphics, and pie charts. You don't necessarily have that with MySQL like you have other solutions, which are really cost prohibitive for some clients. It'd be nice to have an open source solution for that. Decent solutions. I mean decent that I can take to clients. It's so technical. They want to drag and drop.

Quotes from Members

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

Pros

"I used Faiss as a basic database."
"The product has better performance and stability compared to one of its competitors."
"It has a remote access feature to manage the database from a remote location. This enables in-work collaboration."
"Like other databases, it has a rich set of functions, such as stored procedures and its own procedural language, which is akin to Oracle SQL. It also has trigger and cursor commands you would expect with a good database language."
"We are completely comfortable with the database’s performance and it is a mature product. My organization was looking for an open-source database for our smaller customers like the community edition. For bigger customers, we can scale into commercial and supported editions."
"The relations in the database, the dynamic workflow, and the ability to connect with all columns. It's useful for e-commerce."
"I rate the solution's stability a ten out of ten since it has been running flawlessly."
"The most valuable feature is the ease of use."
"MySQL's clustering features are very strong, and you can automate scripting, so that helps. We wrote a Terraform script and ran it."
"The speed is very good."
 

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 user interface could be more user friendly. Mainly because most of the times we see black and white digital lines. Something like Python."
"We want to continue using MySQL but it merged with Oracle and the scalage changed."
"It could be more secure."
"It should provide better customer experiences."
"Stability needs improvement and the backup needs to be enhanced."
"It could be a little bit simpler to use."
"When working with a cluster wide, I have to use the MySQL cluster version."
"Some problems with big table operations, and a struggle to keep the servers responding in peak situations."
 

Pricing and Cost Advice

"It is an open-source tool."
"Faiss is an open-source solution."
"MySQL is released under an open-source license, so you have nothing to pay to use it."
"For the on-premise version, no license is required."
"I use the open-source free community version."
"I think that MySQL is a premium product."
"​Enterprise editions and support are definitely needed for the heavy users who need direct support. ​"
"The tool is open source."
"I don't pay for a license."
"There is a license needed for this solution."
report
Use our free recommendation engine to learn which Open Source Databases solutions are best for your needs.
815,854 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
20%
Financial Services Firm
13%
Manufacturing Company
9%
Educational Organization
8%
Computer Software Company
16%
Financial Services Firm
11%
Manufacturing Company
7%
Government
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...
Why are MySQL connections encrypted and what is the biggest benefit of this?
MySQL encrypts connections to protect your data and the biggest benefit from this is that nobody can corrupt it. If you move information over a network without encryption, you are endangering it, m...
Considering that there is a free version of MySQL, would you invest in one of the paid editions?
I may be considered a MySQL veteran since I have been using it since before Oracle bought it and created paid versions. So back in my day, it was all free, it was open-source and the best among sim...
What is one thing you would improve with MySQL?
One thing I would improve related to MySQL is not within the product itself, but with the guides to it. Before, when it was free, everyone was on their own, seeking tutorials and how-to videos onli...
 

Comparisons

 

Learn More

Video not available
 

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
Facebook, Tumblr, Scholastic, MTV Networks, Wikipedia, Verizon Wireless, Sage Group, Glassfish Open Message Queue, and RightNow Technologies.
Find out what your peers are saying about Faiss vs. MySQL and other solutions. Updated: October 2024.
815,854 professionals have used our research since 2012.