A Java Geek weekly 116

My case against autowiring

Written in 2013, I still stand by it in 2025!

Goodbye Microservices: From 100s of problem children to 1 superstar

The post mentions that Twilio collapsed their 120 microservices into one. I’d love to know how many teams do they have; if they have less than 120, I’d like to understand their rationale of having a single team create multiple microservices. My assumption is that the reason was technical, whereas it should have been organizational.

The second question I’m dying to ask is how much did they evaluate the cost of using such a convoluted architecture instead of a good old monolith from the beginning.

The Anatomy of a macOS App
anatomyofapp26
The Case Against Microservices

Another post demolishing the microservices hype. Can we finally call it a day?

If your company’s promotion packet requires "scale" or "complexity" to prove your worth as an engineer, the entire software stack will inevitably become overengineered. In turn, the people who get promoted in such a system will defend the status quo and hoard tribal knowledge of how it all works. They become merchants of complexity because the success of their careers depends on it.

Magika 1.0: Smarter, Faster File Detection with Rust and AI

Super handy! Yet, the "installation" method is not optimal.

Introduction to Netflix Hollow

TIL.

Java applications are highly prone to heap space issues while distributing data. Netflix Hollow’s design handles this by efficiently managing memory by offloading large datasets into external storage systems, such as file systems, object stores, or networked solutions.

Boring Technology, Boring Architecture

Microservices were never primarily a technical invention. They were an organisational one.

This should be printed out and handed out before every architecture board meeting.

Why Most GitHub Projects Are a Mess (And How to Fix It)
  • Pull Request Templates
  • Code Owners and Auto-Assignment
  • Security Scanning and Badges
  • Automated Dependency Updates
  • Essential Documentation Files
Next level Kotlin support in Spring Boot 4
  • Idiomatic null-safe APIs with JSpecify
  • Better Kotlin Serialization support
  • DSL-based registration of Spring beans
  • Automatic context propagation with Coroutines
The Impact of Technical Blogging

Lots of good reasons to start your blog in there. Don’t wait!

Vibe Coding

The second type of vibe coding is what I am interested in. It is when you use a coding agent to build towers of complexity that go beyond what you have time to understand in any detail. I am interested in what it means to cede cognitive control to an AI.

Stop Sitting on the Bench! Why AI Resisters Are Getting Kicked Out

It’s hard to argue against it if you put it like this.

Nicolas Fränkel

Nicolas Fränkel

Nicolas Fränkel is a technologist focusing on cloud-native technologies, DevOps, CI/CD pipelines, and system observability. His focus revolves around creating technical content, delivering talks, and engaging with developer communities to promote the adoption of modern software practices. With a strong background in software, he has worked extensively with the JVM, applying his expertise across various industries. In addition to his technical work, he is the author of several books and regularly shares insights through his blog and open-source contributions.

Read More
A Java Geek weekly 116
Share this