parallel-consumer VS Hermes

Hi everyone, my name is Daniel and I run a website called Rock the JVM [1]. It's a popular site and blog for Scala, and we've recently started to create guides and materials for other libraries and languages. This video is about - maximizing producer throughput - minimizing producer latency - running multiple consumers vs number of partitions, analyzing parallelism - parallel consumers [2] for 1000x perf increase vs 1x single-threaded consumer I also have written forms of all videos as long-form blog posts, and you can find the written guide here [3]. I hope you like it - let me know if you need anything or have any questions! [1] https://rockthejvm.com [2] https://github.com/confluentinc/parallel-consumer [3] https://blog.rockthejvm.com/optimizing-kafka-clients-a-hands-on-guide/

So we want to maximize parallelism while keeping DLQ style error handling and stability. We want to send messages to DLQs if any error happens and we don't want any message to be unprocessed and still be committed. I know there are Confluent Parallel Consumer, Greyhound and an article about Multi-Threaded Messaging with Kafka. But I'm not sure if they are ready for production.

I haven’t used Faust, but it should be fine for your use case if you decide not to use the http sink connector. If you are open to Java, the parallel consumer library will have MUCH better performance because the http requests won’t block. It even aims to provide automatic dead letter queue handling sometime in the future, which you mentioned you need.

Interesting. I think your use case might be well suited for the parallel consumer — https://github.com/confluentinc/parallel-consumer

Take a look at Confluent's Parallel Consumer library, it will handle this sort of scenario for you: https://github.com/confluentinc/parallel-consumer (disclaimer: I'm the author)

Let's draw some parallels in the Kafka ecosystem, in which there are Confluent REST Proxy and Hermes by Allegro. You could say that since Kafka uses a binary protocol over TCP, both of these projects are "moot and useless". Despite that, Allegro aka the Poland's Amazon still maintains that project and uses it in production as a means of HTTP-based communication between their 700+ microservices arguing that it makes their development process easier, since it allows them to abstract away the intricacies of Kafka and use plain HTTP instead.

well, there is https://github.com/allegro/hermes