Java 9 was the first release making the JPMS available for general use. For many developers the impact of JPMS might not be clear, since its not a mandatory thing and the benefits are often overlooked. Why JPMS was desperately needed One might think - Java strict coupling of the package to filesystem structure allows to neatly organize the code. For dependency management of other packages/modules there are proven tools available like maven or gradle....
Gradle incremental builds allow for continuous testing, which is awesome. While appreciating a feature rich IDE, for continuous testing I prefer to keep it simple and run tests directly on the console: gradle test --continuous Continuous testing should answer below questions as quickly as possible Has something failed? Why has it failed? Having many tests in the continuous run is spilling out lots of unhelpful logs for tests that completed successfully....
The Quarkus framework is a Kubernetes native java stack, incredible quick start up times and build on strong standards like the Micro Profile. You might wanna give it a try if you use java for small footprint services running on Kubernetes, Openshift or similar. Comparison with traditional frameworks “Java is slow and a memory hog”. That reputation makes java often seen as inferiour choice when it comes to small services running on the cloud....