Shulou(Shulou.com)05/31 Report--

This article is about how to choose elasticsearch and hbase. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

These two should not be compared. Take a look at their introductions:

Elasticsearch is a search server based on Lucene. (wiki:Elasticsearch)

HBase is an open source, non-relational, distributed database modeled after Google'sBigTable and written in Java. (wiki:Apache HBase)

One is a search engine and the other is a database.

In the distributed environment, the two are widely used, but the roles they play are different. How to use and how to cooperate depends on the actual business. But es is not limited to search engines, database is also a good choice, can be well combined with spark to do data analysis.

It is true that the two are similar in terms of basic functions, but depending on the business needs, I think there are several points to consider:

1. Query complexity: HBase supports simple row or range queries, such as checking the row's data for a competitor, or checking this range of data for a begin/end, which is not easy if you want to complete more complex functions. On the other hand, the queries supported by ES are rich, or they all have the flavor of complex computation. For example, if you have a forum, you want to check whether the post contains sensitive words. If you use HBase, it is more troublesome to use HBase. You can save the post and read it out, but if you want to check the contents of the content, you can only filter it bit by bit. ES can help you accomplish this function more conveniently.

two。 Data volume: according to reason, both support massive data, but according to my personal feeling, HBase may be easier to support more data, because it is designed to solve massive problems at the beginning; ES gradually enhanced its storage scalability later; that is to say, HBase scalability is not likely to hinder your use; ES may take a little more effort.

3. The rest are more distant considerations, such as maintainability, HBase is based on Hadoop, there are many components, and the cost of maintenance is not low, while ES has its own system, which is slightly better to maintain; of course, this is relatively, absolutely not easy. For example, the development of new functions, such as cost control and so on.

Personally, I think es still focuses on retrieval, while hbase is good at reading and writing, so you still need to see your application scenario.

Hbase saves more and reads less, so it is not suitable for highly concurrent queries. It is suitable for storing data.

Es is a full-text search, suitable for log analysis, log statistics and so on.

If you mainly do real-time, dynamic counting, ES is recommended.

If you mainly run some monthly reports or something, Hbase is recommended.

Thank you for reading! This is the end of the article on "how to choose elasticsearch and hbase". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.