Spring Data JPA 4 quietly moved derived queries off the Criteria API onto JPQL strings. Part 2 of the migration series covers the benchmark, getSingleResultOrNull, provider differences (with a real EclipseLink regression), the removed native-query parser, NULLS precedence, and which new JPQL functions are portable.
Part 1 of a 3-part Spring Data JPA 3 to 4 migration series. Covers the platform bump, the hibernate-jpamodelgen to hibernate-processor rename, repository interface compatibility, the JSpecify @NullMarked null-handling shift, and what genuinely doesn't change. Verified against Spring Boot 4.0.6 and Spring Data JPA 4.0.6.
A beginner-to-advanced guide to migrating the repository layer from Spring Data JPA 3 to 4 on Spring Boot 4.1: the hibernate-jpamodelgen → hibernate-processor coordinate swap and the silent metamodel failure it causes, why derived queries now generate JPQL instead of CriteriaQuery (and the getSingleResultOrNull edge case), records as @Embeddable value objects and projection targets, JSpecify nullability, the refined Specification API, and the removed config that breaks your build — all mapped to real code and errors on a Spring Boot 4.1 app.
AI scanners are flooding the Spring ecosystem with patch PRs faster than any team can review. Build an automated remediation pipeline instead: Dependabot or Renovate tuned for Spring Boot parent POMs and BOMs, a Testcontainers regression gate that decides which bumps are safe, and canary deployments for minor framework upgrades.
Of every breaking change in the Spring Boot 2 → 3 era, the removal of WebSecurityConfigurerAdapter generated the most confused stack traces I've debugged — because security configuration is the one place where "it compiles and runs" tells you almost nothing about whether it still protects anything. This guide migrates Spring Security 5 configurations to the 6.x component model (Spring Boot 3.x), covers what tightens further in Spring Security 7 (Spring Boot 4), and flags the places where a mechanical conversion quietly changes your authorization behaviour.
Spring Boot 4 finally forced the issue: RestTemplate, in maintenance mode since Spring 5, is out of the recommended path, and codebases full of getForObject() and exchange() calls need a plan. The good news is that RestClient (introduced in Spring 6.1 / Boot 3.2) was designed as the synchronous successor, so this migration is mostly mechanical — if you know the method-by-method mapping and the three places where behaviour quietly differs. This guide gives you both.
The first time I ported a Zuul gateway to Spring Cloud Gateway, the routes took an afternoon — and the filters took two weeks. That ratio surprises every team that attempts this migration, because the route configuration looks superficially similar while the filter model is a different universe: Zuul 1 is a blocking servlet filter chain, Spring Cloud Gateway runs on Netty with Project Reactor, and a single hidden blocking call in a ported filter can stall your entire gateway. This guide covers the route conversion, the filter-by-filter port, and the blocking-call traps, in that order.
In 2020 I published a dozen tutorials on this site covering Eureka, Hystrix, Zuul, Ribbon, and Feign — the Spring Cloud Netflix stack. They were accurate then. Today, most of that stack is dead: Netflix put Hystrix into maintenance mode back in 2018, Zuul 1 and Ribbon followed, and the Spring team removed them from the Spring Cloud release train entirely. If you are still running any of these libraries on Spring Boot 2.x, this guide maps every Netflix component to its modern replacement and shows you the actual migration steps — including the parts that break.
A practical Spring Boot 3 to 4 migration guide covering the real Java baseline, starter modularization, Jackson 3 as the default JSON library, Spring Security 7 defaults, virtual threads, testing breakage, and production pitfalls that most tutorials skip entirely.
A complete, hands-on guide to HTTP Service Clients in Spring Boot 4 and Spring Framework 7. Learn how to replace RestTemplate and manual WebClient boilerplate with declarative @HttpExchange interfaces, configure service groups via @ImportHttpServices, set per-group timeouts and base URLs with application.properties, test with @RestClientTest, and migrate from OpenFeign — with fully annotated production-grade code and sample output.