Remove or adapt the devon4j kafka module

[baumeister25]

Depending on the issue devonfw/devon4j#548 you can completely remove the module or need to adjust it to the leftover requirements

• Keep only topics (if any) that are really bringing a benefit
• Document the benefit for future projects

[hohwille]

@baumeister25 I am happy with this step but we need to...

• consistently rework documentation, etc.
• provide a clear deprecation status
• provide a (simple) "migration guide"
• update sample app(s)

[hohwille]

See also https://github.com/devonfw/devon4j/pull/470 - could you see what is actually left to do here?

[baumeister25]

Thank you @hohwille , In zenhub it looks much better. This issue is a story of an epic which exactly explains and contains your points. Somehow the connection to the epic is not that easily visible here. https://github.com/devonfw/.github/issues/129 The complete epic is in progress by a student team at the moment

[hohwille]

@baumeister25 thanks for the explanation. I still do not get why we need an epic and an issue addressing the same thing as the epic but I fully agree to the goal described in the epic: We should mark the kafka module as deprecated and change the documentation to propose using the spring[-boot] integration and give best-practices on this.

@maihacke are you involved here or can you create some connect so people who actually have experience with Kafka can contribute. If there is something I can tell from the start, it is that documentation like this can only be written by people who collected real-life project experience as otherwise we only waste time...

[maihacke]

Hasn't this already be adressed with https://github.com/devonfw/devon4j/pull/470? What is missing? If you need connect to some Kafka experts, ping me via MS Teams.