Replacing redis with elasticsearch (GET query speed, counters and lists)?

Elastic Stack Elasticsearch
2

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 :slight_smile:

Karel

On Oct 16, 11:20 pm, datadev 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/
    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!