Tagged “backend”

1. Java 25 After the Hype: 5 Features That Actually Matter

   felipestanzani@blog ~ ~ cat "Java 25 After the Hype: 5 Fe"~ cat post << 03-04-2026

   

   When a new Java LTS drops, the internet goes through its usual cycle: launch posts, conference talks, YouTube thumbnails screaming “GAME CHANGER,” and LinkedIn hot takes about how everything has changed forever.

   Then reality settles in.

   A few months after the release of Java 25, most teams aren’t rewriting their systems. They’re shipping features, fixing bugs, and trying to keep production stable. That’s when we can finally answer a more interesting question:

   Which Java 25 features are still being discussed and actually used?

   This isn’t a launch recap. This is a “post-hype” filter. Here are five Java 25 features that have proven they’re more than marketing bullets.

   1. Structured Concurrency: Concurrency That Reads Like Logic

   For years, Java concurrency meant juggling ExecutorService, Future, timeouts, and cancellation semantics that were easy to get wrong.

   Structured Concurrency changes the mental model. Instead of spawning detached tasks and hoping everything is cleaned up properly, you treat concurrent tasks as a single logical unit.

   Before

   ExecutorService executor = Executors.newFixedThreadPool(2);
   
   Future<User> userFuture = executor.submit(() -> fetchUser());
   Future<Orders> ordersFuture = executor.submit(() -> fetchOrders());
   
   User user = userFuture.get();
   Orders orders = ordersFuture.get();
   

   Continue reading...

2. Spring Boot 4: Brief Upgrade Guide and Code Comparison

   felipestanzani@blog ~ ~ cat "Spring Boot 4: Brief Upgrade"~ cat post << 01-16-2026

   

   If you’ve been following my blog, you know I love a good migration story. Whether it’s moving to TanStack Start or refining shadcn/ui forms, the goal is always the same: better developer experience and more robust code.

   Today, we’re looking at the big one. Spring Boot 4.0 is officially out, and it’s arguably the most important release since 3.0. It moves the baseline to &Java 17 (with a massive push for Java 25), adopts Jakarta EE 11, and introduces features that finally kill off years of boilerplate.

   Let’s look at exactly what changed and how your code will look before and after the upgrade.

   1. Native API Versioning

   For years, versioning an API in Spring meant custom URL paths, header filters, or complex RequestCondition hacks. Spring Boot 4 brings this into the core framework.

   The Spring Boot 3 Way (Manual Pathing)

   // You had to manually manage the path segments
   @RestController
   @RequestMapping("/api/v1/orders")
   public class OrderControllerV1 { ... }
   
   @RestController
   @RequestMapping("/api/v2/orders")
   public class OrderControllerV2 { ... }
   

   The Spring Boot 4 Way (Native Mapping)

   Now, versioning is a first-class citizen. You can keep the path clean and let Spring handle the routing logic via headers, query params, or path segments.

   Continue reading...

See all tags .