# A case for Redis as broker **URL:** \ **Category:** Elasticsearch\ **Created:** [November 11, 2013, 8:35pm UTC](https://discuss.elastic.co/t/a-case-for-redis-as-broker/14355 "2013-11-11T20:35:38Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Nicholas\_Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nicholas_rios/32/1979_2.png) [@Nicholas\_Rios](https://discuss.elastic.co/u/Nicholas_Rios)\ **Post date:** [November 11, 2013, 8:35pm UTC](https://discuss.elastic.co/t/a-case-for-redis-as-broker/14355/1 "2013-11-11T20:35:38Z")
Hi all, we are building an elasticsearch stack currently but hitting some uncertainty whether to include Redis or not. I am writing up an argument for it's inclusion and hoped to gain additional insight from this experienced community. We are using elasticsearch specifically for indexing various system log files, and may generate as much as 1gb per hour. So far, I have made points regarding improved scalability by segmenting logstash and basically using Redis as a fancy buffer. Also, I have made the point about flexibility should we ever bring ElasticSearch down that we continue to capture logs during any downtime. And the point that we can attach parallel services to either side of Redis. Are there additional advantage or drawbacks that I should be aware of? Thanks so much for any insight, thoughts or pointers to relevant existing conversations on this topic. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Nicholas\_Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nicholas_rios/32/1979_2.png) [@Nicholas\_Rios](https://discuss.elastic.co/u/Nicholas_Rios)\ **Post date:** [November 11, 2013, 8:46pm UTC](https://discuss.elastic.co/t/a-case-for-redis-as-broker/14355/2 "2013-11-11T20:46:31Z")
I really want to better understand what we gain by storing messages in Redis. Is the relief felt by logstash or by elastic search? How so? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 11, 2013, 8:56pm UTC](https://discuss.elastic.co/t/a-case-for-redis-as-broker/14355/3 "2013-11-11T20:56:53Z")
Take a look at this thread [https://groups.google.com/d/topic/elasticsearch/3CaRrizmBcQ/discussion](https://groups.google.com/d/topic/elasticsearch/3CaRrizmBcQ/discussion) Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 12 November 2013 07:46, Nicholas Rios [nicholas.jay.rios@gmail.com](mailto:nicholas.jay.rios@gmail.com)wrote: > I really want to better understand what we gain by storing messages in > Redis. Is the relief felt by logstash or by Elasticsearch? How so? > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Norberto\_Meijome](https://avatars.discourse-cdn.com/v4/letter/n/ed655f/32.png) [@Norberto\_Meijome](https://discuss.elastic.co/u/Norberto_Meijome)\ **Post date:** [November 12, 2013, 12:03am UTC](https://discuss.elastic.co/t/a-case-for-redis-as-broker/14355/4 "2013-11-12T00:03:39Z")
Not sure how much you want to scale....but something like a rabbitmq cluster seems, to me, far more scalable than redis, for this use case, and with better data safety rules... You could of course have multiple redis and hash across the cluster but it is harder to scale up and down as needed. Throughput will likely be higher with redis on a simple implementation... -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:07am UTC](https://discuss.elastic.co/t/a-case-for-redis-as-broker/14355/5 "2017-07-06T02:07:47Z")