Queue persistence - which is the most suitable solution


(Paco) #1

Hi all.
I'm new at Elastic stack, my team is exploring its possibilities in order to develop a centralised logging solution, and one feature we'd like to have by definition in our system is to ensure that messages that are sent are not lost.

So our understanding is that we need some sort of mechanism in order to support message queuing and persistence.

We found out that Logstash allows enabling persistent queues, but I there is so few information about it that I'm not sure how it will scale.

Also found out alternatives such as RabbitMQ or Kafka, which will add a piece to the architecture, but seem to be more broadly accepted and have much more information.

So my question is, in order to scale a solution based on elastic from the begin, which would be the most suitable solution so we can reach millions or daily records?


(system) #2

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