ClickHouse vs. MariaDB Platform

The most important thing when using ClickHouse is to be clear that the scenarios in which you want to use it really are the right ones. Many users think that when a database is very fast for a specific use case, it can be extrapolated to other contexts (most of the time different) in which a previous analysis has not been carried out.

ClickHouse is an analytical database, as such, it should be used for such purposes, where the information is stored correctly, the data volumes are really large and the queries to be performed are not the typical traditional queries on several columns with multiple aggregations. ClickHouse is not the solution for this.

On the other hand, if your case is not one of the above, it is quite possible that ClickHouse can help you. Where ClickHouse shines is when you are looking for aggregation over a particular column in large volumes of data.

Incentivized

• Applications where the users need [to] execute many short queries.
• With new storage engines such as Aria, which allows to replace MyISAM with some improvements, and XtraDB, which evolves InnoDB.
• To fuse the legacy features with the features available in NoSQL databases.
• Connection management, which allows multiplying the number of concurrent accesses.
• New clustering engines, such as Galera, which allow interesting possibilities for Cloud adoption.

Incentivized

• Their MergeTree table engine provide impressive performance for data insert in bulk
• Not only data insert but also the way MergeTree engine uses Primary Keys to sort the data and perform data skipping based on the granules its also their secret for ridiculous fast queries
• Data compression its also great
• They provide especial table engines that allow you to read data directly from other sources like S3
• Since its written with C++ you have very granular data types and especial ones like enum, LowCardinality and etc, they save you a lot of storage since are stored as integer values
• ClickHouse functions besides the ones that respect ANSI Standards are also awesome and useful

Incentivized

• Simpler learning curve. MariaDB is a cleaner, simpler system that is (IMO) easier to learn and easier to manage effectively than many other database systems.
• Lower hardware requirements. After migrating to MariaDB from another database software system, we find that our hardware needs have substantially decreased.
• MariaDB support is very responsive. It's like they actually care. On the few occasions we've run into technical issues, support has always come through with what we needed. Once it was showing me a relatively new feature the server supported that I wasn't aware of, that, once I was able to properly make use of it helped me resolve a serious production performance issue.
• Architectural flexibility. As an example, the ready availability of synchronous (Galera) versus asynchronous replication schemes without being locked into one of the other by enormous technical complexity or punitive licensing, allows the customer to find what really works best for their needs.

Incentivized

• Avro data manipulation
• Kafka consistency
• DDL operations errors (by replica configuration)

Incentivized

• Driver Support - Some third party applications use database drivers that cause unexplained slowness with MariaDB. This can be worked around by using the MySQL drivers, but it's not clear what causes the problem in the first place.
• Support - While online communities are helpful in diagnosing problems, there isn't as much professional documentation/support available for MariaDB as some of the other major database options.
• Data Visualization - It would be helpful if there were more built in options for analyzing statistics and generating reports.

Incentivized

MariaDB is very usable and stable to be used in production settings as an alternative to MySQL. The shortcomings of SQL are present but well understood in the community, and if the decision were to be made again, I would choose MariaDB over MySQL on future projects.

Incentivized

We have launched several inquiries to MariaDB support and they have always responded very quickly and have not been tutoring for the duration of the incident/problem.

Likewise, they want to hold constant meetings with the client to get their opinion as well as how they can help.

I see a very human support and concerned about the customer.

Incentivized

ClickHouse outperforms, especially in costs, since its compression/indexing engines are so smart, and even with very low computing power, you can already perform huge analyses of the data.

Incentivized

MariaDB stacks up the the competition just fine. Due to is ture open source nature we do not have to worry about licencing and spending money on nothing. Moreover, MariaDB does everything that we need to get done. We can run data that is a million rows or many smaller projects on the same environment with little overhead. One of the best features that MariaDB has is the ability of backup or dump data to standard text sql statements. That was one of the reasons why we choose MariaDb because it makes backups or transferring data a snap

Incentivized

• Queries that used to take more than 2 minutes now take less than 1 second
• Possibility to analyze use cases in real time (before was impossible)
• The applications are more complete and the users decisions are better

Incentivized

• Low CAPEX if you have a team that use open source software day by day
• Medium OPEX if you have a team that use open source software day by day
• Perfect to use in academic ambient to support researchers and students

Incentivized