ClickHouse vs. MongoDB vs. Percona Server for MySQL

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

If asked by a colleague I would highly recommend MongoDB. MongoDB provides incredible flexibility and is quick and easy to set up. It also provides extensive documentation which is very useful for someone new to the tool. Though I've used it for years and still referenced the docs often. From my experience and the use cases I've worked on, I'd suggest using it anywhere that needs a fast, efficient storage space for non-relational data. If a relational database is needed then another tool would be more apt.

Incentivized

Percona Server for MySQL covers 100% of our requirements in terms of our OLTP traffic and provides the High Availability levels required through a typical primary and 2 replica's using semi-synchronous replication. We're able to scale our writes using sharding, but a true distributed database would be a great option on top of this. In terms of OLAP traffic, we leverage columns stores available, but Percona Server fairs well

• 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

• Being a JSON language optimizes the response time of a query, you can directly build a query logic from the same service
• You can install a local, database-based environment rather than the non-relational real-time bases such a firebase does not allow, the local environment is paramount since you can work without relying on the internet.
• Forming collections in Mango is relatively simple, you do not need to know of query to work with it, since it has a simple graphic environment that allows you to manage databases for those who are not experts in console management.

Incentivized

• Faster than other server solutions
• Installation and configuration process is easy from the user's standpoint
• Easy to learn and good support

Incentivized

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

Incentivized

• An aggregate pipeline can be a bit overwhelming as a newcomer.
• There's still no real concept of joins with references/foreign keys, although the aggregate framework has a feature that is close.
• Database management/dev ops can still be time-consuming if rolling your own deployments. (Thankfully there are plenty of providers like Compose or even MongoDB's own Atlas that helps take care of the nitty-gritty.

Incentivized

• Better documentation
• A better UI

I am looking forward to increasing our SaaS subscriptions such that I get to experience global replica sets, working in reads from secondaries, and what not. Can't wait to be able to exploit some of the power that the "Big Boys" use MongoDB for.

Incentivized

NoSQL database systems such as MongoDB lack graphical interfaces by default and therefore to improve usability it is necessary to install third-party applications to see more visually the schemas and stored documents. In addition, these tools also allow us to visualize the commands to be executed for each operation.

Incentivized

It is easy to install and use. Using it along with Percona Monitoring and Management makes it even easier to use.

Incentivized

Finding support from local companies can be difficult. There were times when the local company could not find a solution and we reached a solution by getting support globally. If a good local company is found, it will overcome all your problems with its global support.

Incentivized

We are using opensource so we have not used customer support.

While the setup and configuration of MongoDB is pretty straight forward, having a vendor that performs automatic backups and scales the cluster automatically is very convenient. If you do not have a system administrator or DBA familiar with MongoDB on hand, it's a very good idea to use a 3rd party vendor that specializes in MongoDB hosting. The value is very well worth it over hosting it yourself since the cost is often reasonable among providers.

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

We have [measured] the speed in reading/write operations in high load and finally select the winner = MongoDBWe have [not] too much data but in case there will be 10 [times] more we need Cassandra. Cassandra's storage engine provides constant-time writes no matter how big your data set grows. For analytics, MongoDB provides a custom map/reduce implementation; Cassandra provides native Hadoop support.

Performance and stability sets Percona Server for MySQL apart from the rest. Percona embraces the upstream version and contributes towards the upstream version making MySQL stronger on two fronts and thus having a much larger community. Many quality contributions have been made by Percona into the base code. Percona provides great tools to support Percona Server for MySQL and this makes the monitoring and management easier

• 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

• Open Source w/ reasonable support costs have a direct, positive impact on the ROI (we moved away from large, monolithic, locked in licensing models)
• You do have to balance the necessary level of HA & DR with the number of servers required to scale up and scale out. Servers cost money - so DR & HR doesn't come for free (even though it's built into the architecture of MongoDB

• At the performance level, it maintains and even improves other open-source databases such as MariaDB or some commercial ones such as Oracle.
• If we compare it with MySQL, we could have up to 50% improvement in performance.
• For some small companies or startups, the price of the complete solution and the support can be a bit high.

Incentivized