Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (nike.apache.org: domain of sberyozkin@gmail.com designates
 209.85.215.46 as permitted sender)
Message-ID: <54EC75F0.6060503@gmail.com>
Date: Tue, 24 Feb 2015 13:00:32 +0000
From: Sergey Beryozkin <sberyozkin@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Andrey Redko <drreta@gmail.com>
CC: Daniel Kulp <dev@cxf.apache.org>
Subject: Re: Fwd: Hystrix feature?
References: 
 <CAGO7Ob2_G7hNzQL9FbV2HR0k=6fm5B8UW0yA2oRF6U2n4EWm7w@mail.gmail.com>
 <CAGAo6aNqaew8jf+xiPzOLLg=VFm+wFx+OrZHjXTeRC+Y_VW7jg@mail.gmail.com>
In-Reply-To: 
 <CAGAo6aNqaew8jf+xiPzOLLg=VFm+wFx+OrZHjXTeRC+Y_VW7jg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Andriy,

David Karlsen is def not proposing to start supporting reactive client 
API, it is more about about some advanced fault-tolerance support - we 
should actually reply to him I guess.

Thanks for sharing a link though. We will have to implement it as part 
of JAX-RS 2.1 work, and we'd need to have a Java 8 trunk opened for it.

It does appear Jersey is already full steam into a Java 8 based 2.1 
development (note: no spec api proposals have been made - but I expect 
them coming soon enough once they have finished experimenting). Dan,

IMHO it would be right to have a Java 8 trunk opened in the last quarter 
of the year to give CXF a better chance of catching up sooner than later 
with Jersey. I'm not trying to extend the dev discussion here though - 
more or less what I said there :-)

Cheers, Sergey


On 24/02/15 12:30, Andrey Redko wrote:
> Hi Sergey,
>
> What do you think about looking into this feature? I do have some
> knowledge about Hystrix and it
> has gained some traction in the community. I am not sure though what
> exactly this guy has
> in mind BUT if you don't mind, I can work with him to outline his design
> / intentions and make sure
> it would make sense for the CXF project (I can reply to him and work
> with him directly).
>
> What do you think?
>
> PS: FYI, Jersey has started to integrate Netflix projects
> (http://blog.dejavu.sk/2015/01/07/reactive-jersey-client-part-1-motivation/),
> into their JAX-RS implementation, I think Hystrix will come soon as well.
>
> Best Regards,
>      Andriy Redko
>
> ---------- Forwarded message ----------
> From: *David Karlsen* <davidkarlsen@gmail.com
> <mailto:davidkarlsen@gmail.com>>
> Date: Mon, Feb 23, 2015 at 4:03 AM
> Subject: Hystrix feature?
> To: dev@cxf.apache.org <mailto:dev@cxf.apache.org>
>
>
> Hi.
>
> I'm wondering about creating an Interceptor for outgoing requests
> (isRequestor()==true) to wrap these (synchronously) in a Hystrix [1]
> executable [2].
>
> Instead of having this as an inhouse custom component, I wonder about
> creating a branch of cxf and adding a features/hystrix component (like for
> the clustering support). Is this a component you would accept and be
> willing to merge into master? I'm asking upfront so I don't end in a
> dead-end with it and have to port it back to an inhouse-component.
> I thought I'd use the serviceQname as commandGroup (namespace) and key
> (localname). I also thought I'd add a protected method resolveTenant
> (returning null for default) so that multitenant solutions are well
> supported (e.g. the same service may be ok for one tenant and failing for
> another, so be able to differenciate config).
>
> [1] https://github.com/Netflix/Hystrix
> [2]
> https://netflix.github.io/Hystrix/javadoc/com/netflix/hystrix/HystrixCommand.html
>
>
> WDYT?
>
> --
> --
> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
>