I've started looking into the API issues and I believe that most of these API issues can be solved if we change the approach being taken. Most of this library is a refactor of core feign concepts using functional style and paradigms. The reactive areas are limited to executing the Request, which we can simplify by wrapping the existing synchronous implementation in a Reactive wrapper.

I've started working on that in my fork and you can see what I have here:

https://github.com/kdavisk6/feign-reactive/tree/reactive-core/feign-reactive-core/src/main/java/feign

From my perspective, this should be sufficient for us to get an initial release out. Since this approach extends from feign directly, it will allow this library to support everything regular feign does, including logging, encoding, decoding, OkHttp, ApacheHTTP, Jackson, GSON, etc... solving all of our API issues.

With regards to Spring Cloud, all that should be necessary is a new Targeter, as my approach is extremely close to HystrixFeign. Please take a look at my fork and let me know what you all think. @spencergibb and @ryanjbaxter I would appreciate if you could check my assumptions and provide us with your perspective on this problem.

@velo and @kptfh I would appreciate if you could look at my fork and let me know your thoughts.

Consider releasing artifact #15

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions