Speaker

Gradle has a lot of performance advantages in comparison to Maven.

However there can be different blockers to migrate from Maven to Gradle (like release management or CI/CD pipelines), also in a large organization it'll require to teach a lot of engineers the new tooling and there can be pitfalls.

The good news is that Maven has a lot of potential to speed up the builds.

In this session we'll talk about possible ways to optimize it, starting with trivial things like choosing proper JDK, upgrading to Kotlin 2.0 K2, stop building and deploying redundant artifacts. Also we'll talk about Apache Build Cache and Develocity extensions, extracting code generation to jar dependency and how it will boost the experience in the IDE.

Then we'll dig deeper to how the Maven Reactor works under the hood and how it builds multi-module projects, what's the main problem of scalability/parallelization there.

In this section it will be explained why modularization is a key factor, how to find build bottlenecks and how to modularize the build.

Eventually you may make a decision to switch to Gradle if all these optimizations are not enough. But in any case these advices are complementary and will have positive effect for Gradle projects as well.