For the longest time backend Java developers only ran code on web servers. Web servers are the glue between the outside world and your application. They pass incoming network requests to your code to do some work and return a response — like handling REST API calls made by most modern web apps. Web servers are predictable, reliable, but deeply flawed. As traffic increases, you need to manually scale up the number of web servers....
Spring Boot has 50+ libraries available to add to your application. With so much functionality, how do you know you’re not missing critical features that could avoid hours of wasted development? My answer was to spend way too long browsing official docs. But after a few years I did uncover some hidden gems my colleagues never knew existed. Here are my favourites to help you save time and eliminate unnecessary code....
For any keen developer, every time they run the build process they’re itching to get coding again. But slow builds put the brakes on your ability to deliver more features. When the only feedback you get from the build process is its status and duration, how can you even begin to think about optimising it? Well, if you use Gradle to build Java code you’re in luck. There’s a way to profile your build process to get key insights into what’s going on internally—a bit like debugging or JVM profiling tools....
When working with slow tests, parallelising them is the first step towards faster builds.
Don’t waste any more time waiting for tests to run locally by implementing this quick build script fix.
Hans Dockter quotes that’ll open your mind to new ways of building software.
Everyone wants fast, maintainable tests, so how do you best combine the test pyramid model with the realities of your own project?
Streamline your code with new language features in this latest Java LTS release.
Switching your build scripts to Kotlin doesn’t have to be hard with this step-by-step process.