On Wed, Feb 29, 2012 at 02:52:16AM -0800, marsbomber wrote:
>
> Yes, I see that as the true advantage of taking Ruote into an SOA
> environment. Ruote dictates the workflow (my understanding is that's
> what Ruote is designed for, but John, you'll have a bigger say, coz
> you're the author :p), everything true processing unit just worry
> about their own discrete task.
Yes, ruote orchestrates.
> I actually get a bit confused about your work on ruote-swf. I'm not
> sure where swf fits in the puzzle now ... My guess is if that one
> single job step/expression/participant is doing a hell lot and need to
> break down the sub task into sub-sub tasks, that's when you need swf?
OK, staying off-topic with you.
SWF is a simple workflow framework. Ruote-swf is a "storage" implementation
for ruote.
You do something like:
storage = Ruote::Swf::Storage.new(
SWF_ACCESS_KEY_ID,
SWF_SECRET_ACCESS_KEY,
'swf_domain' => 'xyz')
Ruote::Dashboard.new(
Ruote::Swf::DecisionWorker.new(
Ruote::Swf::ActivityWorker.new(
storage)))
And you then run your usual ruote workflows, but the back-end is SWF.
The Amazon engineers do the maintainance of whatever iron and soft run SWF.
Not you.
It's not as fast as a local Redis ruote storage, it doesn't support a process
listening to the activity of another, but apart from that, it's vanilla
ruote.
I'm waiting from my employer's green light for switching the repository from
private to public.
That's it, kind regards,
--
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
