0

We are in the process of writing a lightweight Kafka microservice that will be responsible for managing the complexities around Kafka integration for an Event-driven Architecture. Other applications will only communicate with this Kafka-microservice over HTTP.

Q1: When comparing the Quarkus SmallRye Kafka Connector and the Kafka Bare APIs, it seems like Quarkus/Smallrye gives clean annotation-based config to get up and running quickly, but we were wondering if it is production-ready, and if it has built-in flexibility to configure Kafka interactions at very granular-level if needed (through mp.messaging.*)?

Q2: Are there any gotchas around going with the SmallRye Kafka Connector?

Thanks

codemasorete
  • 51
  • 3

1 Answers1

0

Q1: The Kafka connector is definitely production-ready. See https://quarkus.io/blog/decathlon-user-story/ as reference.

Q2: The Kafka connector wraps the Apache Kafka client and handles asynchronous processing correctly. However, it wraps the "bare" kafka client. There are a few limitations. For example, it does not handle Kafka transaction at the moment.

Clement
  • 2,817
  • 1
  • 12
  • 11