Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing MySQL vs LocustDB, the Slant community recommends MySQL for most people. In the question“What are the best analytics databases? ” MySQL is ranked 2nd while LocustDB is ranked 4th. 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 Lightning fast
When running a simple count query on a database of 1.46 billion taxi rides, LocustDB completed the query in 0.25 seconds, beating out both Clickhouse and KDB+ (both leading analytics services) which came in at 0.89s and 0.84s respectively.
During testing a number of other queries were run, including average, count by 2/3, sparse filter, top N, reducible cardinality, irreducible cardinality, and dictionary encoding. LocustDB came out on top throughout nearly all of these tests.
Pro Simple to install and run
Using LocustDB is as simple as installing Rust, cloning the repository, pointing it to your database, and pressing go.
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 Current support for certain types of data is lacking
LocustDB, as of the time of writing this, does not support floating point numbers, finding averages, or grouping by clause.
