Hi Andriy
But please, do reply to David K and work with him - IMHO CXF won't have
to ship Hystrix - but making sure various CXF (client) Failover
interfaces can be extended to accommodate a Hystrix feature would be a
good idea IMHO. We can then start with adding a Hystrix failover system
test.
Thanks, Sergey
On 24/02/15 13:00, Sergey Beryozkin wrote:
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* <davidkarl...@gmail.com
<mailto:davidkarl...@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
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
