When to choose Cassandra over a SQL / Semantic Store solution?

I have 30-40 GB of data and 3 development machines (Core Duo i4, 3 GB). Data is a set of graphical structures, and I have queries that intersect graphs. Is there a guide that could help me decide to use Cassandra or a classic solution like SQL or the Semantic Store? My current plan is to configure Cassandra and see how it works, but I would like to know more before starting the installation.

+3
source share
1 answer

I would not use Cassandra for any graph level structure. It has been about 6 months since I learned something like this, so maybe Cassandra has progressed since then, but I found that it was fundamentally limited by the fact that it only has row level indexes.

For a graph-based structure (assuming a simplified one arc per line layout) you really need column indices, since if you want to go through the graph you want to start with a specific node Aand find all the arcs that come from that node (assuming an oriented Graph ), then you will have to scan the rows of the entire data set, since there are no built-in functions to tell me the rows that have Ain a particular column.

Cassandra, . , , , - , . slides , , , .

, , RDF - Graph. NoSQL, , , - , , , .

+1

Source: https://habr.com/ru/post/1785147/


All Articles