;>>>
>>>>>>> I think for CB we need a new EIP, and not LB and a component. Hystrix
>>>>>>> can be an implementation of the EIP. And it might be better if the
>>>>>>> caching, request collapsing concepts are not mixed with the CB EI
Cheers,
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 6 April 2016 at 07:43, Claus Ibsen wrote:
>>>>>>> There is some pros with being an endpoint configuration only,
>>> On 6 April 2016 at 07:43, Claus Ibsen wrote:
>>>>>> There is some pros with being an endpoint configuration only, as it
>>>>>> can make it easy for tooling and some developers to use it (when they
>>>>>> are used to configure uris, and just use from -> to -> to etc). I
>>>&
;>>>> You could also have CB as a kind of error handler, aka onException,
>>>>> but have it as onCircuitBreaker, where you can setup those breaker
>>>>> configs and fallback routes / endpoint etc. And whether to use a
>>>>> fallback or re
er, where you can setup those breaker
>>>> configs and fallback routes / endpoint etc. And whether to use a
>>>> fallback or reject or whatnot.
>>>>
>>>> Just a quick pseudo code / braindump
>>>>
>>>>
>>>>IOEx
ption
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Apr 4, 2016 at 6:07 PM, Preben.Asmussen wrote:
>>>> Hi bibryam
>>>>
>>>> At first glance it looks a bit intrusive when the usual endpoints are
>>>> 'wrapped' in the hystrix endpoint.
>&g
oints are
>>> 'wrapped' in the hystrix endpoint.
>>>
>>> Could it be something like -> psudo code
>>>
>>> >> xmlns="http://camel.apache.org/schema/blueprint";>
>>>
>>>
>>>
>>>
t;> > xmlns="http://camel.apache.org/schema/blueprint";>
>>
>>
>>
>> .. other options
>>
>>
>>
>> > uri="timer://local?fixedRate=true&period=50&repeatCount=5"
>
>
>
>
>
> /Preben
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/New-camel-hystrix-component-tp5770955p5780454.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
t first glance it looks a bit intrusive when the usual endpoints are
>> 'wrapped' in the hystrix endpoint.
>>
>> Could it be something like -> psudo code
>>
>> > xmlns="http://camel.apache.org/schema/blueprint";>
>>
>>
>>
>> .....
:-)
Maybe the xml dsl could have it's own namespace like cxf.
Then you can import it and declare the hystrix stuff outside of the camel
context.
Wouldn't this solve having hystrix dependencies in camel core.
Cheers
--
View this message in context:
http://camel.465427.n5.nabble.com
50&repeatCount=5"/>
>
>
>
>
>
>
>
>
> /Preben
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/New-camel-hystrix-component-tp5770955p5780454.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
... other options
/Preben
--
View this message in context:
http://camel.465427.n5.nabble.com/New-camel-hystrix-component-tp5770955p5780454.html
Sent from the Camel Development mailing list archive at Nabble.com.
FYI,
I've pushed the camel-hystrix component to master.
Currently it doesn't support request collapsing and the threading
aspects needs more testing and possibly improving.
Here is a small example how the new component can be used:
https://github.com/bibryam/camel-hystrix-demo/blob/master/src/ma
Thanks Raul, I will go further and merge my implementation to master.
Before that I will see what ideas I can take from your branch.
Going forward, we may have to consdier what new versions of Java is
bringing to the table for Camel Java DSL in general anyway.
Cheers,
On 28 January 2016 at 14:12
Hi
Good to hear that you guys will pickup this and work on a
camel-hystrix component.
I agree with Bilgin that the component should be similar to how you
use all the other components using the endpoints and how they are
configured.
PS: Another cool component would be a Apache Storm component.
O
On Thu, Jan 28, 2016 at 2:20 PM, David Karlsen
wrote:
> Just a fyi. I think archaius is gone in Hystrix 1.5 (configuration is an
> interface with default imp with archaius). There is a RC out of Hystrix 1.5
>
Cool, thanks for the heads-up, David!
*Raúl Kripalani*
PMC & Committer @ Apache Ignite
Just a fyi. I think archaius is gone in Hystrix 1.5 (configuration is an
interface with default imp with archaius). There is a RC out of Hystrix 1.5
28. jan. 2016 15:12 skrev "Raul Kripalani" :
> Hey Bilgin,
>
> I agree with you. My implementation started as a experiment, to be honest.
>
> My visi
Hey Bilgin,
I agree with you. My implementation started as a experiment, to be honest.
My vision was deep and fluent integration between Camel and Hystrix, that's
why I started experimenting with a fluent DSL. To me, Hystrix is not just
an external thing to integrate in Camel, but it should play
Hi Raul,
More or less the same time you published the first email about
camel-hystrix component, I also created camel-hystrix component [1]
(it is not finished yet!). But I took the typical (boring ;-))
approach where the hystix support can be used as a regular component
through URI configuration.
Hi team,
Hystrix [1] is a powerful toolbox framework based on RxJava for building
JVM-based fault-tolerant distributed systems, made OSS by Netflix.
Due to the nature of Camel, our users inherently deal with distributed
systems and therefore I thought integrating this framework into Camel would
b
21 matches
Mail list logo
