cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Redko <>
Subject Fwd: Hystrix feature?
Date Tue, 24 Feb 2015 12:30:04 GMT
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 (,
into their JAX-RS implementation, I think Hystrix will come soon as well.

Best Regards,
    Andriy Redko

---------- Forwarded message ----------
From: David Karlsen <>
Date: Mon, Feb 23, 2015 at 4:03 AM
Subject: Hystrix feature?


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).



David J. M. Karlsen -

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message