Hi John, I'm working on a hosting orchestration application. Ruote is the core of this "glueing" system. A fundamental business requirement is to make sure the whole system is resilient. Any and every part of it can fail at any given time, we need to be able to recover it somehow ... Also we need to scale out the bottleneck parts easily too ... hence there goes my setup ... Is it an overkill or not? I honestly don't know, but you know what objective I'm aiming at now! (I actually am considering if a federation messaging architecture is needed to truly achieve system resilient)
Yeah, it's about 39 days of banging my head against the wall :) I didn't ask many questions, I guess because I was so focused on getting the architecture out with a proof of concept workflow run. I'm sure I will bug you more often once I need to dig into the details more! As for the deep_merge, you could see my hacky commit from my fork of ruote. It's nothing but change your 2.3 union merge impl from using ruby merge! to active_support's deep_merge! Take it anytime! I'm however happy to discuss with you whether it's needed at all at the first place though! On Feb 29, 3:39 pm, John Mettraux <[email protected]> wrote: > On Tue, Feb 28, 2012 at 02:37:49PM -0800, marsbomber wrote: > > > Nicola, hope this helps you in some ways. Unfortunately what I'm > > building is close sourced, I cannot disclose > > anymore details. > > Hello Mars, > > can you tell us for which domain you developed your solution? > > > As something for myself, John, does what I describe make sense to you > > at all? Am I over-complicating things? > > Or there are aspects from Ruote, which I simply missed, that could > > simplify things a little? > > This "RabbitMQ between ruote and the hard-working participants" pattern seems > to be used by lots of people. > > I sometimes wonder if a simpler queue, like a Redis queue wouldn't be > sufficient, but I guess people are used to deploy and manage RabbitMQ and > they like to have fancy topologies so it makes a lot of sense. > > I also wonder if a 0mq setting might not be nice. We could also use 0mq > inside of a ruote storage (might be very fun). > > I have to say I'm impressed, we first talked 39 days ago (according to my > Twitter client) and since, you built such a nice system, barely asking any > questions. > > BTW, we should discuss if your deep-merge is a good candidate for the master > branch. > > Keep up the great work! > > -- > John Mettraux -http://lambda.io/processi -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
