Reconsidering module-kafka: Evaluating the need for its deprecation

[destitutor]

No description provided.

[oereo]

• Limitations of using a Config Class or Abstract Class for common settings when separated as a kafka-module:

  • When creating a separate kafka-module, using a single Config Class or Abstract Class for common settings might not be the most suitable approach.
  • The reason is that such an approach may lack flexibility and might not be adaptable to different environments or configurations where the kafka-module is used.

• Challenges in separating functionalities as a common module due to varying Retry policies and configuration values specific to the service implementing Kafka:

  • Different services that use Kafka might have varying Retry policies and configuration values specific to their needs.
  • Trying to abstract and standardize these diverse functionalities into a single common module becomes challenging due to the service-specific characteristics.
  • As a result, it may become difficult to create a one-size-fits-all common module that accommodates all the different needs of various services.