We’re not going to compare two popular open-source log management tools that can be used to reduce the burden of managing logs like how more powerful fluentd (written in CRuby) than logstash (written in JRuby), or even splunk, etc. But in this section, we should have an idea that there is always an alternative technology or method to achieve any goal in any case.
In case the difference between fluentd and logstash, i always be the one who think there is no differentiator that states which one of them is better than the other part. Even if the fact that logstash consumes more memory compared to fluentd or fluentd is the leader in the number of plugins available compared to the logstash or bla…bla. or bla…bla..bla.
Just take it or leave it. Take it if we are building a complex solution then the fluentd make us more convenient with it, or still using the other with consideration that the algorithmic statements on ‘route events’ make you look like so programmer 🙂 and it is good for procedural programmers. Both fluentd and logstash are suitable for certain requirements.
But the most important and best point is both can co-exist in same environment and can be used for specific use cases, for monolithic applications and microservices. Something just like we could use the shell script combined with php, or shell script with java for more powerful tools. Indeed, ELK-EFK hybrid could be the way to get the best out of both.
