fidzu : programming

Building enterprise Java systems used to mean choosing an app server, deploying a monolith, and scaling vertically until the budget or the database complained. In 2026, modern Java teams are expected to deliver faster releases, better resilience, and elastic cost-performance across unpredictable workloads. That's exactly what cloud-native Java architecture is designed to achieve: systems built for change, not just for uptime.

But "cloud-native" is not a buzzword synonym for "running on Kubernetes." A truly scalable approach combines Java microservices (for domain isolation and independent delivery) with Serverless Java (for bursty or event-driven workloads), backed by Kubernetes for Java as the operational substrate for consistent deployment, resilience, and observability.

20 Mar 2026 2:00pm GMT

This article discusses the differences between a Java microservice architecture (SCS style) using Clean Architecture and a Spring Modulith architecture. It explores their strengths, trade-offs, and when to use each approach.

The architectures are demonstrated using two projects:

18 Mar 2026 8:00pm GMT

So you have a new AI-based idea and need to create an MVP app to test it?

If your AI knowledge is limited to OpenAI, I have bad news for you… it's not going to be free.

18 Mar 2026 7:00pm GMT