Elasticsearch vs. MySQL

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Elasticsearch
Score 8.3 out of 10
N/A
Elasticsearch is an enterprise search tool from Elastic in Mountain View, California.
$16
per month
MySQL
Score 8.3 out of 10
N/A
MySQL is a popular open-source relational and embedded database, now owned by Oracle.N/A
Pricing
ElasticsearchMySQL
Editions & Modules
Standard
$16.00
per month
Gold
$19.00
per month
Platinum
$22.00
per month
Enterprise
Contact Sales
No answers on this topic
Offerings
Pricing Offerings
ElasticsearchMySQL
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
ElasticsearchMySQL
Considered Both Products
Elasticsearch
Chose Elasticsearch
Even when sphinx base code is on c++ and they obtain a great performance from it, even when they have a set of plugins that allow to integrate with common database systems like MySQL, Elasticsearch is on top of license and all their experience on search. It also provides a long …
Chose Elasticsearch
When we first evaluated Elasticsearch, we compared it with alternatives like traditional RDBMS products (Postgres, MySQL) as well as other noSQL solutions like Cassandra & MongoDB. For our use case, Elasticsearch delivered on two fronts. First, we got a world-class search …
Chose Elasticsearch
All database systems have things they are good at, and things they aren't as good at. Riak/SOLR is great as a K/V store, but SOLR cannot handle requests as fast as ElasticSearch. In fact, SOLR is the reason we had to migrate to ElasticSearch.
Redis is great at SET operations …
Chose Elasticsearch
We found Elasticsearch to be the fastest in querying text based data, allowing us to significantly speed up our APIs.
Chose Elasticsearch
Solr is the only other alternative product I've used. Elasticsearch in comparison is a much better product. The query language in elasticsearch along with the cluster management and sharding makes Elasticsearch a clear winner.
Chose Elasticsearch
Even though Lucene is very powerful it is not easy to implement Lucene as a search provider. Lucene is the core of Elasticsearch and they made implementation very easy.
Chose Elasticsearch
Ability to support JSON queries, Percolator, ease to set up and custom routing were some of the reasons why we decided to use Elasticsearch instead of Solr.
MySQL

No answer on this topic

Top Pros
Top Cons
Best Alternatives
ElasticsearchMySQL
Small Businesses
Algolia
Algolia
Score 8.7 out of 10
Redis™*
Redis™*
Score 9.0 out of 10
Medium-sized Companies
Guru
Guru
Score 8.9 out of 10
Redis™*
Redis™*
Score 9.0 out of 10
Enterprises
Guru
Guru
Score 8.9 out of 10
Redis™*
Redis™*
Score 9.0 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
ElasticsearchMySQL
Likelihood to Recommend
9.0
(46 ratings)
8.3
(134 ratings)
Likelihood to Renew
10.0
(1 ratings)
9.9
(4 ratings)
Usability
10.0
(1 ratings)
10.0
(6 ratings)
Support Rating
7.8
(9 ratings)
8.6
(2 ratings)
Implementation Rating
9.0
(1 ratings)
8.0
(1 ratings)
User Testimonials
ElasticsearchMySQL
Likelihood to Recommend
Elastic
Elasticsearch is a really scalable solution that can fit a lot of needs, but the bigger and/or those needs become, the more understanding & infrastructure you will need for your instance to be running correctly. Elasticsearch is not problem-free - you can get yourself in a lot of trouble if you are not following good practices and/or if are not managing the cluster correctly. Licensing is a big decision point here as Elasticsearch is a middleware component - be sure to read the licensing agreement of the version you want to try before you commit to it. Same goes for long-term support - be sure to keep yourself in the know for this aspect you may end up stuck with an unpatched version for years.
Read full review
Oracle
From my own perspective and the tasks that I perform on a daily basis, MySQL is perfect. It has a reasonable footprint, is fast enough and offers the security and flexibility I need. Everyone has their preferred applications and, no doubt, for larger data warehouses or more intensive applications, MySQL may have its limits, but for the area that I operate in, it's a great match.
Read full review
Pros
Elastic
  • As I mentioned before, Elasticsearch's flexible data model is unparalleled. You can nest fields as deeply as you want, have as many fields as you want, but whatever you want in those fields (as long as it stays the same type), and all of it will be searchable and you don't need to even declare a schema beforehand!
  • Elastic, the company behind Elasticsearch, is super strong financially and they have a great team of devs and product managers working on Elasticsearch. When I first started using ES 3 years ago, I was 90% impressed and knew it would be a good fit. 3 years later, I am 200% impressed and blown away by how far it has come and gotten even better. If there are features that are missing or you don't think it's fast enough right now, I bet it'll be suitable next year because the team behind it is so dang fast!
  • Elasticsearch is really, really stable. It takes a lot to bring down a cluster. It's self-balancing algorithms, leader-election system, self-healing properties are state of the art. We've never seen network failures or hard-drive corruption or CPU bugs bring down an ES cluster.
Read full review
Oracle
  • Security: is embedded at each level in MySQL. Authentication mechanisms are in place for configuring user access and even service account access to applications. MySQL is secure enough under the hood to store your sensitive information. Also, additional plugins are available that sit on top of MySQL for even tighter security.
  • Widely adopted: MySQL is used across the industry and is trusted the most. Therefore, if you face any problems, simply Google it and you shall land in plenty of forums. This is a great relief as when you are in a need of help, you can find it right in your browser.
  • Lightweight application: MySQL is not a heavy application. However, the data you store in the database can get heavy with time, but as in the configuration and MySql application files, those are not very heavy and can easily be installed on legacy systems as well.
Read full review
Cons
Elastic
  • Joining data requires duplicate de-normalized documents that make parent child relationships. It is hard and requires a lot of synchronizations
  • Tracking errors in the data in the logs can be hard, and sometimes recurring errors blow up the error logs
  • Schema changes require complete reindexing of an index
Read full review
Oracle
  • Although you can add the data you require as more and more data is added, the fixity of it becomes more critical.
  • As the demand, size, and use of the system increase, you may also need to change or acquire more equipment on your servers, although this is an internal inconvenience for the company.
Read full review
Likelihood to Renew
Elastic
We're pretty heavily invested in ElasticSearch at this point, and there aren't any obvious negatives that would make us reconsider this decision.
Read full review
Oracle
For teaching Databases and SQL, I would definitely continue to use MySQL. It provides a good, solid foundation to learn about databases. Also to learn about the SQL language and how it works with the creation, insertion, deletion, updating, and manipulation of data, tables, and databases. This SQL language is a foundation and can be used to learn many other database related concepts.
Read full review
Usability
Elastic
To get started with Elasticsearch, you don't have to get very involved in configuring what really is an incredibly complex system under the hood. You simply install the package, run the service, and you're immediately able to begin using it. You don't need to learn any sort of query language to add data to Elasticsearch or perform some basic searching. If you're used to any sort of RESTful API, getting started with Elasticsearch is a breeze. If you've never interacted with a RESTful API directly, the journey may be a little more bumpy. Overall, though, it's incredibly simple to use for what it's doing under the covers.
Read full review
Oracle
I give MySQL a 9/10 overall because I really like it but I feel like there are a lot of tech people who would hate it if I gave it a 10/10. I've never had any problems with it or reached any of its limitations but I know a few people who have so I can't give it a 10/10 based on those complaints.
Read full review
Support Rating
Elastic
We've only used it as an opensource tooling. We did not purchase any additional support to roll out the elasticsearch software. When rolling out the application on our platform we've used the documentation which was available online. During our test phases we did not experience any bugs or issues so we did not rely on support at all.
Read full review
Oracle
The support staff is friendly, knowledgeable, and efficient. I only had to get part way through my explanations before they had a solution. They will walk you through a fix or actually connect in and fix the problem for you--or would if you can allow it. I've done it both ways with them. They are always forthcoming with 'how to do this if it happens again' information. I love working with MySQL support.
Read full review
Implementation Rating
Elastic
Do not mix data and master roles. Dedicate at least 3 nodes just for Master
Read full review
Oracle
1. Estimate your data size. 2. Test, test, and test.
Read full review
Alternatives Considered
Elastic
As far as we are concerned, Elasticsearch is the gold standard and we have barely evaluated any alternatives. You could consider it an alternative to a relational or NoSQL database, so in cases where those suffice, you don't need Elasticsearch. But if you want powerful text-based search capabilities across large data sets, Elasticsearch is the way to go.
Read full review
Oracle
MongoDB has a dynamic schema for how data is stored in 'documents' whereas MySQL is more structured with tables, columns, and rows. MongoDB was built for high availability whereas MySQL can be a challenge when it comes to replication of the data and making everything redundant in the event of a DR or outage.
Read full review
Return on Investment
Elastic
  • We have had great luck with implementing Elasticsearch for our search and analytics use cases.
  • While the operational burden is not minimal, operating a cluster of servers, using a custom query language, writing Elasticsearch-specific bulk insert code, the performance and the relative operational ease of Elasticsearch are unparalleled.
  • We've easily saved hundreds of thousands of dollars implementing Elasticsearch vs. RDBMS vs. other no-SQL solutions for our specific set of problems.
Read full review
Oracle
  • As it is an open source solution through community solution, we can use it in a multitude of projects without cost license
  • The acquisition by Oracle makes you need to contract support for the enterprise version
  • If you have knowledge about oracle databases, you can get more out of the enterprise version
Read full review
ScreenShots