Apache Cassandra vs. MySQL

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Cassandra
Score 9.0 out of 10
N/A
Cassandra is a no-SQL database from Apache.N/A
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
Apache CassandraMySQL
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
CassandraMySQL
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
Apache CassandraMySQL
Considered Both Products
Cassandra
Chose Cassandra
It was packaged with the vendor product we bought. Also, it’s good for high performance transactional systems. I'm part of our NoSQL team and Cassandra quickly became a favorite for developers with agile teams.
Chose Cassandra
DynamoDB is good and is also a truly global database as a service on AWS. However, if your organization is not using AWS, then Cassandra will provide a highly scalable and tuneable, consistent database.
Cassandra is also fault-tolerant and good for replication across multiple …
Chose Cassandra
Cassandra has its own use case. It performs very well as a data store. Data can be written to it at a high rate. It cannot be compared to traditional RDBMS like Oracle, because they all have their own usage. Even MongoDB, which is somewhat similar, cannot be stacked up against …
Chose Cassandra
We evaluated MongoDB also, but don't like the single point failure possibility. The HBase coupled us too tightly to the Hadoop world while we prefer more technical flexibility. Also HBase is designed for "cold"/old historical data lake use cases and is not typically used for …
Chose Cassandra
Technology selection should be done based on the need and not based on buzz words in the market (google searching). If your data need flat file approach and more searchable based on index and partition keys, then it's better to go for Cassandra. Cassandra is a better choice …
Chose Cassandra
Cassandra is the only NoSQL database I have extensive experience with. In terms of other open source database solutions, I can say that I like Cassandra as much or equally as traditional Oracle MySql, and a lot more than PostgresSQL. The decision to use Cassandra was driven by …
Chose Cassandra
Against HBASE, writes were faster. Reads not so much. Also ability to store in other formats would be good (such as objects). Compared to aerospike, does not compare. Aerospike blows it out of water.
Chose Cassandra
Cassandra does one thing very well. It's able to collect any type of metrics and analytics and store them at very fast speeds. But when it comes to reading the data, there are minor performance issues. That's when other databases such as couchdb or couchbase come in. They can …
Chose Cassandra

These are the features which makes Cassandra different from others:

  • Cassandra is a distributed datastore, with a built-in coordinator. This means that requests are intelligently forwarded to the correct node.
  • It is generally very fast, and especially shines with write heavy …
Chose Cassandra
Apache Cassandra has the best of both worlds, it is a Java based NoSQL, linearly scalable, best in class tunable performance across different workloads, fault tolerant, distributed, masterless, time series database. We have used both Apache HBase and MongoDB for some use cases …
Chose Cassandra
Four years ago, I needed to choose a web-scale database. Having used relational databases for years (PostgreSQL is my favorite), I needed something that could perform well at scale with no downtime. I considered VoltDB for its in-memory speed, but it's limited in scale. I …
Chose Cassandra
I tried to evaluate Cassandra against Voldemort and found Cassandra more efficient when writing scalable applications.
Chose Cassandra
We also evaluated mySQL and mongoDB. Both of them have their strengths and weaknesses but they are less suited for storing massive amounts of time series data. In addition, they are not elastic by nature and we required a "future-proof" solution as it was difficult to estimate …
Chose Cassandra
Cassandra is well suited to more complex networks like multiple data centers. The underlying distributed systems logic is fundamentally sound.
MySQL
Chose MySQL
Is not a drop-in replacement for any of the things listed above. MySQL has it's purpose and use-cases, same as those. It's a low-cost solution for high read/low write applications and works very well when used in the right circumstances. Support can be purchased from various …
Chose MySQL
MySQL was the first option due to the existing knowledge, and after using other databases, it also appeared to be the most predictable in terms of costs
Chose MySQL
I like the structured nature of MySQL over MongoDB.
Chose MySQL
Each of the products has its own merits and demerits. however since MySQL is a very good documentation and global community its easy to learn and apply in different stages for analytics work. compare to other data bases its simple for setup and work on it. MySQL is cost …
Chose MySQL
Rest all the big brand databases incure high licensing cost giving almost the same value that MySQL is giving being an open source database. Other databases like Oracle, MS SQL servers need extensive resource along with a huge team to manage those databases. However, thats not …
Chose MySQL
Selection of MySQL or Oracle SQL developer depends on various factors like timelines, requirements, features and data volumes. We are using both MySQL and Oracle SQL developer in our organization. MySQL is more suited for small applications with few thousand TPS and less users. …
Chose MySQL
In terms of capabilities, Microsoft SQL Server is one of the leaders in the database market. It provides a lot of features for high availability, disaster recovery, performance and security. The primary reason why MySQL 8 was chosen was due to the open source nature of the …
Chose MySQL
We chose MySQL because of its open-source nature and its compatibility with various systems, languages, and databases. It is easy to use and fast. Additionally, it has been in the market for more than 30 years now which makes it a reliable option when compared to its …
Chose MySQL
Our original implementation of MySQL was to replace an Access database that had unfortunately been able to grow beyond its abilities and scope. MySQL seemed to offer all the benefits of Access (easy to set up, use and administer) with none of the downsides (reliability, …
Chose MySQL
As I have been commenting in our company, we have solved our performance problems and responses obtaining speed in the queries occupies less disk space, in addition to its price and all the tools of great Scope it possesses.
Chose MySQL
We let go SQL server as We don't want to use Windows server and bare the cost of Windows licensing.
Chose MySQL
The primary reason we use MySQL instead of MongoDB is because we are in a large, legacy enterprise environment. MySQL works well and has all the necessary integrations with the various other software tools in our company's suite. Additionally, MySQL is a relational database …
Chose MySQL
It was quite challenging to choose between these as they both have their pros and cons. But as far as we were concerned the decision to adopt the MYSQL database for our production was because it is an open-source language. This makes it very compatible with our needs and was …
Chose MySQL
MySQL is open source and reduces development costs drastically.
Chose MySQL
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 …
Chose MySQL
MySQL works properly, it gives us the most efficient data and the organization of the data yields an unsurpassed result in performance. And in the same way, in our case as a company, we have users from different offices that are in the same line of work since they can share and …
Chose MySQL
I have evaluated MySQL Heatwave for some ETL pulls in our database to generate reports for stakeholders. It helped me to do so.
Chose MySQL
Microsoft SQL and SQLite i have used for different scenarios. SQLite is very small database which is more easy to work with low profile devices like mobiles. MySQL is not suitable for that level and MSSQL mainly comparable with MYSQL. MSSQL has complex installations and …
Chose MySQL
So the main reason i would stack up Mysql from rest of the others is that it is open source which can be helpful for doing any POC on the products and learning new technologies and it is also compatible with all other softwares like Microsoft SQL serve and Postgre Sql
Chose MySQL
it is cost effective solution and that time we were looking the good RDMS which can support the GIS based datatypes.

Its community edition is fantastic
Chose MySQL
Having used both PostgreSQL and Microsoft SQL Server, I can tell that MySQL performs admirably in a Linux setting. When compared to Microsoft SQL Server, the extra benefit is the minimal or nonexistent licence fee. We find that MySQL's programming interface is particularly …
Features
Apache CassandraMySQL
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Apache Cassandra
8.0
Ratings
MySQL
-
Ratings
Performance8.50 Ratings00 Ratings
Availability8.80 Ratings00 Ratings
Concurrency7.60 Ratings00 Ratings
Security8.00 Ratings00 Ratings
Scalability9.50 Ratings00 Ratings
Data model flexibility6.70 Ratings00 Ratings
Deployment model flexibility7.00 Ratings00 Ratings
Best Alternatives
Apache CassandraMySQL
Small Businesses

No answers on this topic

InfluxDB
InfluxDB
Score 9.0 out of 10
Medium-sized Companies
Azure Cosmos DB
Azure Cosmos DB
Score 9.0 out of 10
SQLite
SQLite
Score 8.0 out of 10
Enterprises
Azure Cosmos DB
Azure Cosmos DB
Score 9.0 out of 10
SQLite
SQLite
Score 8.0 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache CassandraMySQL
Likelihood to Recommend
6.0
(0 ratings)
8.5
(0 ratings)
Likelihood to Renew
8.6
(0 ratings)
9.0
(0 ratings)
Usability
7.0
(0 ratings)
7.9
(0 ratings)
Support Rating
7.0
(0 ratings)
9.0
(0 ratings)
Implementation Rating
7.0
(0 ratings)
8.0
(0 ratings)
User Testimonials
Apache CassandraMySQL
Likelihood to Recommend
Cassandra excels in a broad range of applications -- especially if you understand its data model and write your applications accordingly. It's an excellent choice for time-series data, and a poor choice for application queues. It performs the best if you can simply record history and compute from it, rather than going back and editing or deleting things a lot.
Read full review
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
  • High Availability - we utilize the data replication features of Cassandra. This enables us to access our data even when several nodes have gone down
  • Data Locality - our architecture combines Cassandra storage nodes and computation nodes in the same machine. This enables us to utilize data locality and limit expensive network IO to read data.
  • Elasticity - Cassandra is a shared nothing architecture. Nodes can be added very easily and they discover the network topology. As soon as a node has joined the Cassandra ring, the data is redistributed among the existing nodes and streamed to it automatically.
Read full review
  • 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
  • No Ad-Hoc Queries: Cassandra data storage layer is basically a key-value storage system. This means that you must "model" your data around the queries you want to surface, rather than around the structure of the data itself.
  • There are no aggregations queries available in Cassandra.
  • Not fit for transactional data.
Read full review
  • 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
I would recommend Cassandra DB to those who know their use case very well, as well as know how they are going to store and retrieve data. If you need a guarantee in data storage and retrieval, and a DB that can be linearly grown by adding nodes across availability zones and regions, then this is the database you should choose.
Read full review
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
It’s great tool but it can be complicated when it comes administration and maintenance.
Read full review
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
Sometimes instead giving straight answer, we ‘re getting transfered to talk professional service.
Read full review
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
No answers on this topic
1. Estimate your data size. 2. Test, test, and test.
Read full review
Alternatives Considered
Apache Cassandra has the best of both worlds, it is a Java based NoSQL, linearly scalable, best in class
tunable performance across different workloads, fault tolerant, distributed, masterless, time series database. We have used both Apache HBase and MongoDB for some use cases which were within hadoop setup and JSON (JavaScript Object Notation) document store respectively, but given the overall factors favoring Apache Cassandra, it is a technology choice for multiple platforms!
Read full review
Each of the products has its own merits and demerits. however since MySQL is a very good documentation and global community its easy to learn and apply in different stages for analytics work. compare to other data bases its simple for setup and work on it. MySQL is cost effective and low risk choice for start up organization makes it more suitable for small to medium enterprises.
Read full review
Return on Investment
  • The open source version of Cassandra is only suggested for learning the basic concepts and play with its core features. Unless you really want to invest a lot in your developers and architects knowing every detail of Cassandra, I prefer the DataStax enterprise version. Although the license cost is relatively high, I think they it is worth it. I'm thinking about the support, the monitoring tool OpsCenter, and the integration of Solr and Spark (for data analysis).
  • Cassandra didn't fully replace our old and traditional relation database Oracle. In addition, it opens another door for us to deal with some special business use cases that NoSQL database can do better in a more feasible and efficient way.
Read full review
  • 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