- Spring as a Java container abstraction - switching to Undertow
- DRY principle with docker-compose
- Building Docker images with Maven
- Spring Boot 2.0 primer
- Multiple JVM versions on macOS
There are plenty examples of basic Dockerfile based builds out there, but a production application requires a bunch of different things, such as reproducibility, hardening, health checks, static analysis - and ideally still be quick to build.
Using Git on macOS is largely a positive experience, other than (in my opinion) the out of the box experience with merge tools. With my recent merge to Homebrew Cask you can use p4merge with no extra work.
Spring MVC abstracts the Java servlet container implementation away from you almost completely, this allows you to migrate from Tomcat quite easily.
An oft-repeated and sensible principle in software engineering is DRY, or “don’t repeat yourself”. Here we will apply this principle to Docker compose files.
To package our application, we’re going to be using Docker. The natural
build language for Docker images are
Dockerfiles, so we will use
Spotify’s Dockerfile Maven plugin.
Spring Boot is a very popular Java framework for creating standalone, production ready web applications. In this series of blog posts, we are going to walk through using Spring Boot 2.0 to build and deploy a simple CRUD REST application.
It’s pretty common when doing Java development to need mutiple versions installed alongside each other. With Brew and Jenv, switching Java versions between projects becomes easy.
If you’ve ever stayed at Center Parcs, you’ll probably have noticed that the heating is configured to drop down to 14 °C every few hours.