Likelihood to Recommend 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.
Read full review Neo4J is great for creating network graphs or illustrating how things are related. It is also good for finding individuals or things that have greater influence than others in a system. It is not appropriate if you have standard data sets that can be analyzed using conventional methods or visualized using
Tableau , for example.
Read full review Pros 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 Read full review Mature Query language, I found Cypher QL to be mature in handling all sorts of problems we throw at it. Its expressive enough to be intuitive while providing rich features for various scenarios. Native support for REST API, that makes interacting with Neo4J intuitive and easy. Support for Procedures in Java, procedures are custom code that could be added to the Neo4J to write custom querying of data. The best part about the procedures is it could be invoked using the REST API. This allows us to overcome any shortcomings from their Cypher query language. Nice UI and interface for executing the Query and visualizing the response. UI access controlled by User credentials allows for neat access controls. Awesome free community edition for small-scale projects. Read full review Cons Avro data manipulation Kafka consistency DDL operations errors (by replica configuration) Read full review One of the hardest challenges that Neo4j had to solve was the horizontal scaling problem. I am not updated on recent developments, but at the time of my use, I couldn't find a viable solution. Neo4j does not play with other open source APIs like Blueprint. You have to use the native Neo4j API. There wasn't a visual tool to see your data. Of course, third party tools are always available, but I would have loved something which came with the Neo4j bundle. I love that Docker comes bundled with Kitematic, so it's not wrong to hope that Neo4j could also ship with some default visualization software. Read full review Usability [Based on] Query Language, Performance on small and large data sets, integration and deployment, analysis, API support, Interactive UI.
Read full review Alternatives Considered 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.
Read full review Neo4j is a graph store and has different use cases compared to another NoSQL Document store like
MongoDB .
MongoDB is a bad choice when joins are common as existing operators for joining two documents (similar to tables in a relational store) as Mongo 3.5 use SQL like join algorithms which are expensive.
MongoDB is a great choice when distributed schemaless rich document structures are important requirements. Cross document transaction support is not native to
MongoDB yet, whereas Neo4J is ACID complaint with all its operations.
Read full review Return on Investment 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 Read full review Positive: Less complex queries on graph structures, than in relational databases. Negative: maintenance is a huge deal, things doesn't work and break, requiring lengthy restore operations. Read full review ScreenShots