[KAFKA-14524] Modularize `core` monolith

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Ismael Juma
• Created: 17/Dec/22 21:20
• Updated: 25/Nov/23 16:13

Description

The `core` module has grown too large and it's time to split it into multiple modules.  The `core` module will be deleted once it's empty (a KIP will be required for this).

Evidence of `core` growing too large is that it takes 1m10s to compile the main code and tests and it takes hours to run all the tests sequentially.

As part of this effort, we should rewrite the Scala code in Java to reduce developer friction, reduce compilation time and simplify deployment (i.e. we can remove the scala version suffix from the module name). Scala may have a number of advantages over Java 8 (minimum version we support now) and Java 11 (minimum version we will support in Kafka 4.0), but a mixture of Scala and Java (as we have now) is more complex than just Java.

Another benefit is that code dependencies will be strictly enforced, which will hopefully help ensure better abstractions.

This pattern was started with the `tools` (but not completed), `metadata` and `raft` modules and we have (when this ticket was filed) a couple more in progress: `group-coordinator` and `storage`.

This is an umbrella ticket and it will link to each ticket related to this goal.

Issue Links

• is blocked by: KAFKA-14470 Move log layer to storage module
• is blocked by: KAFKA-14525 Move CLI tools from `core` to `tools` module
• is blocked by: KAFKA-15852 Move server code from `core` to `server` module
• is blocked by: KAFKA-14048 The Next Generation of the Consumer Rebalance Protocol
• is blocked by: KAFKA-14526 Move `kafka.network` from `core` to separate module
• is blocked by: KAFKA-14527 Move `kafka.security` from `core` to separate module
• is blocked by: KAFKA-14528 Move replication code from `core` to separate module
• links to: GitHub Pull Request #13067