# Would hbase + elasticsearch be faster than just elasticsearch in this case?

**URL:** <https://discuss.elastic.co/t/would-hbase-elasticsearch-be-faster-than-just-elasticsearch-in-this-case/5080>\
**Category:** Elasticsearch\
**Created:** [August 8, 2011, 1:50pm UTC](https://discuss.elastic.co/t/would-hbase-elasticsearch-be-faster-than-just-elasticsearch-in-this-case/5080 "2011-08-08T13:50:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![redCashion](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/redcashion/32/2895_2.png) [@redCashion](https://discuss.elastic.co/u/redCashion)\
**Post date:** [August 8, 2011, 1:50pm UTC](https://discuss.elastic.co/t/would-hbase-elasticsearch-be-faster-than-just-elasticsearch-in-this-case/5080/1 "2011-08-08T13:50:31Z")

</div>

I am building a stat aggregator, where the rows are a long string of  
boolean values. I will be doing two types of queries, sequential  
searches for data points for a graph, and aggregation given a range of  
dates. Given that hbase stores things sequentially, would I have  
faster read times by using hbase + elasticsearch, rather than  
elasticsearch alone as my only data store?

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [August 8, 2011, 5:10pm UTC](https://discuss.elastic.co/t/would-hbase-elasticsearch-be-faster-than-just-elasticsearch-in-this-case/5080/2 "2011-08-08T17:10:09Z")

</div>

hbase is really fast for sequential access, as for fast or not, it mostly  
depends if all your different type of aggregation can work in sequential  
access (and you need to implement the aggregation, assuming you compare it  
to facets in elasticsearch).

On Mon, Aug 8, 2011 at 4:50 PM, Jeremy Smith [xperts@gmail.com](mailto:xperts@gmail.com) wrote:

> I am building a stat aggregator, where the rows are a long string of  
> boolean values. I will be doing two types of queries, sequential  
> searches for data points for a graph, and aggregation given a range of  
> dates. Given that hbase stores things sequentially, would I have  
> faster read times by using hbase + elasticsearch, rather than  
> elasticsearch alone as my only data store?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:57am UTC](https://discuss.elastic.co/t/would-hbase-elasticsearch-be-faster-than-just-elasticsearch-in-this-case/5080/3 "2017-07-06T03:57:54Z")

</div>

Closed on July 6, 2017, 3:57am UTC