What problems does Spring Kafka have with virtual streams? Or are there no problems at all?

Spring Kafka is currently not fully optimized for working with virtual threads from Project Loom, and there are several potential issues:

• Blocking operations: Spring Kafka and the Kafka client use blocking I/O calls, which do not always work well with virtual threads, as they are optimized for non-blocking code.

• Thread pool: Kafka consumer typically uses its own thread pool for message processing. When using virtual threads, careful configuration of interaction with this pool is necessary to avoid losing the benefits of virtual threads.

• Library compatibility: not all dependencies and libraries used in Spring Kafka may work correctly with virtual threads, which can lead to unexpected blocking or performance issues.

• Lack of official support: as of 2024, Spring Kafka has not officially announced full support for virtual threads, so using them together requires thorough testing.

Overall, issues may arise, especially regarding blocking operations and thread interaction. It is recommended to carefully test the application and possibly use virtual threads only where justified, or wait for Spring Kafka updates with full Loom support.