Spring Framework 6 Ships a Native Declarative HTTP Client That Outperforms Feign by 40%
Teams that adopt @HttpExchange shed a Spring Cloud dependency, gain native reactive support, and get a 40% throughput improvement at high concurrency without changing their annotation-driven programming model. For greenfield services or WebFlux stacks, it removes the friction of bolting a blocking client onto a reactive runtime.
@HttpExchange is a Spring Framework 6 core feature that provides declarative HTTP clients through annotated interfaces, backed by RestClient or WebClient. Unlike Feign, it requires no Spring Cloud starter, no @EnableFeignClients annotation, and automatically selects synchronous or asynchronous execution based on the method's return type. Under 1000 concurrent requests, measured throughput is roughly 40% higher than OpenFeign, with memory consumption down about 35%.
Feign remains a blocking-only proxy built on JDK dynamic proxies and tied to the Spring Cloud release cycle. @HttpExchange separates interface definition from transport, using an adapter pattern that routes calls to RestClient for plain return types and WebClient for CompletableFuture, Mono, or Flux. Spring Framework 7 will add an HTTP Service Registry to reduce the boilerplate of manually creating HttpServiceProxyFactory instances.
Migration makes sense for new projects, teams adopting WebFlux, or anyone who wants a lighter dependency footprint. Existing Spring Cloud projects with many Feign interfaces can stay put; the two can coexist while new endpoints move to @HttpExchange gradually.
Spring is absorbing a capability that was previously outsourced to the Cloud portfolio into the core Framework, which signals that declarative HTTP is now considered a fundamental primitive, not a microservice-specific concern.
The adapter pattern underneath @HttpExchange means the same interface definition can flip between blocking and reactive transports just by changing the return type, a design that Feign's hard-wired proxy cannot replicate without a rewrite.
Performance gains come from removing the Netflix/Spring Cloud abstraction layer and letting the Framework's own RestClient/WebClient handle the call stack directly, which also simplifies debugging and stack traces.
Feign's dominance was partly accidental — it was the only mature option in the ecosystem for years. @HttpExchange shows that the bar for a built-in solution is now higher: it must serve both servlet and reactive stacks equally well.
The discussion is thin. One comment asks for compatibility with existing Spring MVC annotations, while another simply notes a plan to try the new client in a monolith project, having previously relied on Feign.
See top comments, translated →