I don't totally follow your argument, or agree with what I do follow.

Even if the kafka client needs it's own specific configuration, and multiple clients are required for multiple data types, meaning different configs are required per client, that doesn't mean that there aren't other parts of blueflood-kafka that have their own configuration. For example the config settings in kafka.conf that start with 'blueflood'.

That should follow the same pattern as `HttpConfig`.

To digress a bit: I sort of understand what you are trying to do with supporting multiple serializers or event types by running the blueflood-kafka module multiple times with different configs. This implies a 1:1 mapping of blueflood-kafka module instance to kafka client instance. I do not think this is the way to go. I think the way to move forward is for the blueflood-kafka module to support multiple instances of the kafka client by having a registry of event type that contains a kafka-client, the serializer, the specific configuration options for that event type, etc.