Component dividing key (Cassandra) versus alternating indexes (Accumulo, BigTable) for space-time series

I am working on a project in which every day we import 50k - 100k datapoints, located both temporarily (YYYYMMDDHHHmm) and spatially (lon, lat), which are then dynamically displayed on the maps in accordance with the request parameters set by our users. We use pre-computed clusters below a given scale level.

In this context, and given the fact that we are in the process of choosing a database engine for our storage tier, I am currently evaluating the Cassandra and BigTable options.

In particular, I am trying to understand the difference between using composite partition keys in Cassandra and alternating index keys in BigTable, for example, using one GeoMesa.

As far as I understand, both of these approaches can use COTS hardware and can be configured to reduce the number of access points and maximize space usage.

What logical steps should I follow to distinguish between them? Although I plan to test both approaches in the near future, I would like to hear a more informed and educated approach.

+4
source share
1 answer

GeoMesa BigTable, Accumulo Cassandra. Cassandra . README .

Z2 Z3 ( , -) . BigTable Z3 . - . Cassandra , ( ). - GeoMesa Cassandra , . - , NxN. Z3 . ( ) Z3 ( ). , . .

-1

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


All Articles