# Replacing redis with elasticsearch (GET query speed, counters and lists)? **URL:** \ **Category:** Elasticsearch\ **Created:** [October 16, 2011, 9:20pm UTC](https://discuss.elastic.co/t/replacing-redis-with-elasticsearch-get-query-speed-counters-and-lists/5609 "2011-10-16T21:20:50Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![karmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/karmi/32/44951_2.png) [@karmi](https://discuss.elastic.co/u/karmi)\ **Post date:** [October 17, 2011, 6:08am UTC](https://discuss.elastic.co/t/replacing-redis-with-elasticsearch-get-query-speed-counters-and-lists/5609/2 "2011-10-17T06:08:19Z")
In all three points you mention: GET, INCRBY, atomic LPOP, I'd consider Redis superior to Elasticsearch. I wouldn't get rid of Redis just to "simplify the stack". There's always something where Redis fits as a glove. (And I love Elasticsearch as much as Redis, possible more 🙂 Karel On Oct 16, 11:20 pm, datadev [n...@adinfocenter.com](mailto:n...@adinfocenter.com) wrote: > I am currently considering replacing redis with elasticsearch to > simplify the stack and have run into the following 3 use cases: > > 1. I am currently using redis for caching. Redis is benchmarked at > around 100,000 GETs per second when querying by key ([http://redis.io/](http://redis.io/) > topics/benchmarks). How does ES stack in terms simple GET by \_id > performance (assuming real-time get)? > > 2. I am currently using redis to store counters (EG: 'foo = foo + > 1280' types of commands). Is there any way to implement the concept of > counters in ES with support atomic updates (maybe using the script > command)? > > 3. I am currently using redis to store lists for queuing use cases (in > which items are added to a list and then popped off). Can something > like that be effectively implemented in ES? > > Thanks and keep up the great work! --- _[View the full topic](https://discuss.elastic.co/t/replacing-redis-with-elasticsearch-get-query-speed-counters-and-lists/5609)._