# Elastic Search with Kafka

**URL:** <https://discuss.elastic.co/t/elastic-search-with-kafka/114310>\
**Category:** Elasticsearch\
**Created:** [January 5, 2018, 4:35pm UTC](https://discuss.elastic.co/t/elastic-search-with-kafka/114310 "2018-01-05T16:35:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![senthil.nathanm](https://avatars.discourse-cdn.com/v4/letter/s/f475e1/32.png) [@senthil.nathanm](https://discuss.elastic.co/u/senthil.nathanm)\
**Post date:** [January 5, 2018, 4:35pm UTC](https://discuss.elastic.co/t/elastic-search-with-kafka/114310/1 "2018-01-05T16:35:23Z")

</div>

Hi Team

We are deliberating the feasibility of adding Confluent Kafka as a message broker to our Elastic Search instance.

Now that logstash comes with its own persistence and dead letter queues, I have some questions in this regard.

(1) Having a message queue layer like Kafka decouples the beat and logstash services which allows for handling work load bursts. How does the built-in queues of logstash handle this ?  
(2) Is there any negative impact on Elastic Search performance with adding a message queue layer ?

Regards  
Senthil Nathan M

---

<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:** [February 2, 2018, 4:35pm UTC](https://discuss.elastic.co/t/elastic-search-with-kafka/114310/2 "2018-02-02T16:35:25Z")

</div>

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