Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing MySQL vs Apache Cassandra, the Slant community recommends MySQL for most people. In the question“What are the best databases to use for Node.js applications?” MySQL is ranked 6th while Apache Cassandra is ranked 13th. The most important reason people chose MySQL is:
MySQL is made to handle a lot of data and to be used in large applications. This makes it extremely scalable and fast, even under a lot of workload.
Specs
Question Ranking
Pros
Pro Scalable
MySQL is made to handle a lot of data and to be used in large applications. This makes it extremely scalable and fast, even under a lot of workload.
Pro Multiple third-party tools that help working with MySQL
Since MySQL is one of the most popular relational databases, maybe the most popular, there exist many third-party tools and applications that help developers to use MySQL in their development.
Pro Easy to start working with
Because of it's popularity there are a lot of tutorials and guides out there that help developers install and work with MySQL. The installation process itself is not very hard and there are multiple powerful GUI tools that make it extremely easy to work with MySQL for a beginner.
Pro Highly available cluster
Once setup database is set up, it becomes highly available without any downtime.
Pro Highly scalable
Cassandra is very scalable and achieves the highest throughput for the maximum number of nodes compared to other alternatives. Unfortunately this also brings rather high write and read latencies.
Pro Familiar to developers used to SQL
The query language that Cassandra uses (CQL) is similar to SQL even though it's a NoSQL database.
Pro Rapid writing and lightning-fast reading
After measuring the read/write performance values on one server, you can simply calculate how many more servers you should add to the cluster to reach the required performance levels, and scale easily.
Cons
Con Error messages usually are not very detailed
When you are trying to do something in MySQL and something goes wrong it will simply give you an error message with an error code. Which does not say much about what went wrong unless you look it up online. This can be a little cumbersome during development.
Con No JOINS
Cassandra has no support for JOINS.
