# When to use kafka or redis

**URL:** <https://discuss.elastic.co/t/when-to-use-kafka-or-redis/100378>\
**Category:** Elasticsearch\
**Created:** [September 13, 2017, 3:22pm UTC](https://discuss.elastic.co/t/when-to-use-kafka-or-redis/100378 "2017-09-13T15:22:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rob\_Davidson](https://avatars.discourse-cdn.com/v4/letter/r/d6d6ee/32.png) [@Rob\_Davidson](https://discuss.elastic.co/u/Rob_Davidson)\
**Post date:** [September 13, 2017, 3:22pm UTC](https://discuss.elastic.co/t/when-to-use-kafka-or-redis/100378/1 "2017-09-13T15:22:22Z")

</div>

My current setup looks like this

> springbootApp -\> log.json -\> filebeat -\>logstash -\>elastic -\>kibana

I am seeing examples where people use Kafka or Redis. When should I be considering using kafka and when is it not necessary? I am looking to see what tradeoffs and potential pitfalls I have with my current setup?

---

<div class="post-metadata">

**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:** [September 13, 2017, 8:54pm UTC](https://discuss.elastic.co/t/when-to-use-kafka-or-redis/100378/2 "2017-09-13T20:54:56Z")

</div>

Usually, if you want an ability to separate ingest and processing and allow for extended buffering while also guaranteeing that data is moved off the source host ASAP.

---

<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:** [October 11, 2017, 9:08pm UTC](https://discuss.elastic.co/t/when-to-use-kafka-or-redis/100378/3 "2017-10-11T21:08:29Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.