Re: Stuart Sierra's Component: retries & restarts in production

Josh Tilles, how did you manage connection failure with Langhor and component, I thought there were an automatic connection recovery by default. Le lundi 7 septembre 2015 01:57:30 UTC+2, Josh Tilles a écrit : > > Thanks a ton for writing all of this up. I'm actually using Langohr & > RabbitMQ

Re: Stuart Sierra's Component: retries & restarts in production

On Thursday, September 3, 2015 at 9:15:54 AM UTC-4, Andy- wrote: > > Only to answer the "retry on error" part of you question: You might like > hara/event: > http://docs.caudate.me/hara/hara-event.html > Thanks for the tip! I've been meaning to check out hara anyway. If I end up using it I'll

Re: Stuart Sierra's Component: retries & restarts in production

Thanks a ton for writing all of this up. I'm actually using Langohr & RabbitMQ as well, so I have the sense that you've solved problems that I might encounter down the road. On Friday, September 4, 2015 at 7:57:21 AM UTC-4, Dave Tenny wrote: > > I'm using components to encapsulate

Re: Stuart Sierra's Component: retries & restarts in production

I'm using components to encapsulate Langohr/RabbitMQ interactions in cases where Langohr auto-recovery wasn't happy with what was going on. I make sure the Lifecycle methods are idempotent, built the component stack in the correct order. To make sure that I can deal with the exceptions that

Re: Stuart Sierra's Component: retries & restarts in production

Caveat: my approach may have been all wrong. It's the first time I tried stuartsierra components. Frankly I'd have been happier with some CLOS objects and before and after methods, I'm still getting the hang of this clojure stuff. On Fri, Sep 4, 2015 at 7:57 AM, Dave Tenny

Re: Stuart Sierra's Component: retries & restarts in production

We make sure the components we build know how to restart themselves. This avoids the use of start/stop. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members

Re: Stuart Sierra's Component: retries & restarts in production

I just found the other resources from the Component wiki —it may be that something linked from there addresses exactly my situation. On Wednesday, September 2, 2015 at 8:44:07 PM UTC-4, jo...@signafire.com wrote: > > TLDR: how do you

Re: Stuart Sierra's Component: retries & restarts in production

On 3 September 2015 at 00:03, wrote: > > The HTTP connection may be closed at any time by the server; if that > happens, the app should persistently attempt to reconnect using an > exponential back-off pattern. In addition, if the app goes thirty seconds > without receiving

Re: Stuart Sierra's Component: retries & restarts in production

Another way I can think of decomposing this is to buffer/queue communication between your two components, i.e a core.async channel. This will decouple the two components allowing your MessageQueue to manage it's own reconnection. Interesting question about whether `start` calling `stop` is

Re: Stuart Sierra's Component: retries & restarts in production

Only to answer the "retry on error" part of you question: You might like hara/event: http://docs.caudate.me/hara/hara-event.html HTH On Wednesday, September 2, 2015 at 8:44:07 PM UTC-4, jo...@signafire.com wrote: > > TLDR: how do you use Component when the application logic involves >