All geek questions in one place

Hbase vs Cassandra: which is better for storing timers data?

I use my API logs to retrieve information, for example:

  • During this time period, many users of my API?
  • Or during this time period, what types of services are called the most?

Almost all the information I retrieve depends on the timestamp. In fact, I'm using MongoDB, and I added the timestamp as an index (for 80 GB, the index size is 12 GB).

I was recommended switching to cassandra or Hbase. And I want to know what is best for my use case:

  • Analysis of time data.
  • Good write and read performance is required.
  • Ability to use hadoop for data analysis.

Thank you for sharing your point of view or your experience.

+6
source share
2 answers

Advantages of Kassandra: Kassandra usually demonstrates better performance (although both are excellent). Cassandra greatly simplifies configuration and management from an operational point of view (although there are tools that will help in any case).

Benefits of HBase: Native to the Haip Ecosystem

HBase will require that you install hadoop anyway, and you get a nice two-for-one. To use Cassandra, you probably need to use DataStax Enterprise, a commercial, non-open source product, or research using Spark for your analytic work that has an open source connector with Cassandra.

+5
source

Chocolate or vanilla ice cream - which is better?

I would suggest that you be the best solution developer. Set up a development environment for each option, and this will tell you much more about operating and configuration issues than I think anyone else can give you. :)

-1
source

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

More articles:


All Articles