# Is Logstash =\>Redis =\> Elasticsearch required? **URL:** \ **Category:** Elasticsearch\ **Created:** [March 24, 2017, 1:55pm UTC](https://discuss.elastic.co/t/is-logstash-redis-elasticsearch-required/79894 "2017-03-24T13:55:05Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kishorramanan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kishorramanan/32/12823_2.png) [@kishorramanan](https://discuss.elastic.co/u/kishorramanan)\ **Post date:** [March 24, 2017, 1:55pm UTC](https://discuss.elastic.co/t/is-logstash-redis-elasticsearch-required/79894/1 "2017-03-24T13:55:05Z")
This is my current architecture. Logstash =\> Elasticsearch I do not use filebeat/forwarder. Logstash crunches the logs and send it to Elasticsearch Is it necessary to introduce Redis in this? Logstash =\>Redis =\> Elasticsearch ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [March 24, 2017, 2:03pm UTC](https://discuss.elastic.co/t/is-logstash-redis-elasticsearch-required/79894/2 "2017-03-24T14:03:24Z")
If you are reading from files and do not have an overly aggressive rollover layer, there is generally no need to introduce a message queue for buffering, as Logstash can simply stop reading for a while if writing to Elasticsearch is not possible and then catch up once any issue clears. If you however have inputs based on TCP and/or UDP, introducing a buffering layer may make sense. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 21, 2017, 2:03pm UTC](https://discuss.elastic.co/t/is-logstash-redis-elasticsearch-required/79894/3 "2017-04-21T14:03:56Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.