Welcome to my newsletter #70!
Yesterday, JDK 20 reached general availability and comes with preview and incubator features related to Virtual Threads, Pattern Matching, and others, and the typical updates on security, Unicode, and time zones. Maybe you want to update your JDK/JRE installation to stay up-to-date. I usually like to build and run my personal projects with the latest Java release, though I typically only use features that are released, not in preview.
In April, I’ll hold a virtual, interactive workshop on effective Quarkus development and testing (Apr 17th & 18th). We’ll cover everything on modern application development and testing with Quarkus; the most important concepts, topics, and technologies to be able to develop with Quarkus. There are still spaces left and it would be nice to see you there.
Quarkus Native or JVM Mode
If you’ve seen or tried Quarkus, you know that you can compile your applications to native executables. But is that the best approach for enterprise projects?
I get asked this question a lot, and I’ve recorded a video in which I’m showing my perspective of what I think the most important features of Quarkus are, and whether we should favor the Quarkus native or JVM mode, in an enterprise project. I explain some background of enterprise Java technologies typically work, how Quarkus is different, what the benefits and drawbacks of native compilations are, and what to choose for a modern cloud-native project.
How to Structure Modern Enterprise Java Projects
A question that also arises very often and one that any Java developer sooner or later runs into, is how to structure ones' projects. Especially in the enterprise world, there are countless examples of over-engineered project structures, with build modules, technical layering, complex packaging, and the like.
I’ve recorded a video, in which I want to answer the question what I think an effective structure and approach looks like for modern, cloud-native Java projects. We’ll also have a look at build/JDK modules, technical versus horizontal layering, package structures, screaming architecture, Boundary Control Entity, and test project structures.
Why You Want to Code With Quarkus
And some more enterprise and Quarkus content: I’ve recorded my top reasons as to why I think that Quarkus is a great choice for Enterprise Java, and why developers and projects should give it a try.
Spoiler: The ability to go native is not on the list :)
Thanks a lot for reading and see you next time!
Did you like the content? You can subscribe to the newsletter for free: