Java Web Development (JSP/Servlets) Services

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. 

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:

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.

This article is part of the series “Stranger things in Java,” dedicated to language deep dives that will help us master even the strangest scenarios that can arise when we program. All articles are inspired by content from the book “Java for Aliens” (in English), the book “Il nuovo Java”, and the book “Programmazione Java.”

This article is a short tutorial on enumeration types, also called enumerations or enums. They are one of the fundamental constructs of the Java language, alongside classes, interfaces, annotations, and records. They are particularly useful to represent sets of known and unchangeable values, such as the days of the week or the cardinal directions.

When designing a Java library, extensibility is often a key requirement, especially in the later phases of a project. Library authors want to allow users to add custom behavior or provide their own implementations without modifying the core codebase. Java addresses this need with the Service Loader API, a built-in mechanism for discovering and loading implementations of a given interface at runtime.

Service Loader enables a clean separation between the Application Programming Interface (API) and its implementation, making it a solid choice for plugin-like architectures and Service Provider Interfaces (SPI). In this post, we’ll look at how Service Loader can be used in practice, along with its advantages and limitations when building extensible Java libraries.