Posts

AWS Cost Optimization for Microservices: ECS vs EKS vs Lambda

The runtime question usually arrives disguised as a cost question: “our AWS bill is too high, should we move to serverless?” Almost always the honest answer is that the runtime is not the biggest line on the invoice — but the runtime decision does determine which levers you get to pull later, so it is worth making deliberately. This is the decision framework I use for Java services, and the levers that have moved real bills.

Monday, August 17, 2026 | 6 minutes Read

Kubernetes Deployments for Java Microservices: Rolling, Blue/Green, and Canary

Not every change carries the same risk. A copy fix and a rewrite of the pricing logic do not need the same rollout mechanics, and treating them the same means you either move too slowly or find out about a regression from your users. This is how I pick between rolling updates, blue/green and canary for Java services — and the JVM-specific details that make all three behave differently than the tutorials suggest.

Monday, August 17, 2026 | 6 minutes Read

Spring Boot Production-Ready Checklist (2026)

Shipping a Spring Boot service is easy. Keeping it fast, secure and operable at three in the morning is the hard part. This is the checklist I walk through before a rollout — condensed from services I have taken to production on Kubernetes over the last few years, currently on Spring Boot 4 and Java 25. It is deliberately not a list of everything you could do. It is the set of things whose absence has cost me, or a team I worked with, an incident.

Monday, August 17, 2026 | 7 minutes Read

Generating data with Mockneat

At some point every developer reaches the point where they need larger amounts of data. One open-source library I like to use is Mockneat. The Mockneat library offers an easy-to-read API to generate JSON, XML, CSV, SQL and whole POJOs. The nice thing about it is that you can generate valid data with little effort. Just a foretaste of what Mockneat can generate without much effort: If something is still missing, I can fall back on a regular expression:

Friday, January 3, 2020 | 1 minute Read

Spock Testing-Framework

First of all, Spock and JUnit are both great test frameworks, and JUnit is usually one of the standard tools I reach for in a project. In my last project a colleague suggested Spock, and we decided to try it out in one of our microservices and roll it out everywhere if we liked it — which we finally did. You can find all examples here on GitHub, of course.

Sunday, October 20, 2019 | 3 minutes Read

Licecap for better bug tickets

How to record screen videos with LICEcap and create better bug tickets. LICEcap is a tool for recording screen captures, which are then converted into animated GIFs and can easily be posted to a ticket tool such as Jira. LICEcap is very simple because it has only two buttons. One to start the recording and one to stop it. A colleague showed me a similar tool in a sprint review today, and I will use LICEcap for bug tickets from now on, because a video is often much more meaningful than text on its own.

Friday, September 20, 2019 | 1 minute Read

Node.js and NPM behind an enterprise proxy

For those who, like me, sometimes have to access the internet via a proxy, using Node’s package manager, npm, can be a real struggle. At first I thought that the proxy can be configured as usual in the Linux world via the environment variables HTTP_PROXY and HTTPS_PROXY. Unfortunately I thought wrong… This is how NPM needs to be configured: npm config set proxy http://proxy.de:8080 npm config set https-proxy http://proxy.de:8080

Wednesday, October 25, 2017 | 1 minute Read

Gitlab CI Debugging

I would like to show you how to debug a CI process locally using GitLab CI. I often see a barrage of failed GitLab CI jobs when new projects are set up, even though it is very easy to test the CI process locally before pushing it to the repository. First of all, this requires Docker to be installed, which you can find here. You also need a Git project and the corresponding .

Tuesday, August 29, 2017 | 2 minutes Read

Impressum

Angaben gemäß § 5 TMG Marc Nützel Bruchstr. 81 45468 Mülheim an der Ruhr Kontakt E-Mail: me[at]marc-nuetzel.de Streitschlichtung Die Europäische Kommission stellt eine Plattform zur Online-Streitbeilegung (OS) bereit: https://ec.europa.eu/consumers/odr. Unsere E-Mail-Adresse finden Sie oben im Impressum. Wir sind nicht bereit oder verpflichtet, an Streitbeilegungsverfahren vor einer Verbraucherschlichtungsstelle teilzunehmen. Haftung für Inhalte Als Diensteanbieter sind wir gemäß § 7 Abs.1 TMG für eigene Inhalte auf diesen Seiten nach den allgemeinen Gesetzen verantwortlich.

Saturday, June 26, 2010 | 2 minutes Read