intermediateOpenFeign: Declarative REST Clients

Why is an unconfigured Feign client (no timeout set) dangerous under real load?

It ties up the calling thread indefinitely if the downstream service is slow but not crashed — under real concurrent load, this exhausts the caller's own thread pool, turning one slow downstream dependency into a cascading outage of the caller too.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full Spring Ecosystem Mastery library.

Why is an unconfigured Feign client (no timeout set) dangerous under real load?

Next Step

Continue to What's the core difference between what OpenFeign and WebClient return from a call?← Back to all Spring Cloud questions