Hi,
I am re-engineering a system to use a new platform, including Silverlight and an HTTP-push notification mechanism (which has a servicebus-like interface). I've seen examples of sagas and I think they would be of benefit to our project. But I have a dilemma, do I:
i) implement saga-like functionality on top of our existing lightweight servicebus
ii) use a servicebus that already supports sagas and integrate our HTTP transport
Now I know that Udi and the NSB crowd would say do ii). But we don't need all the features of something like NSB, especially when the existing transport does 80% of what we need. And I don't want to duplicate someone else's code (and problems), but we don't even need all the behaviour of sagas. The main appeal of sagas (for us) is not long-running requests but the coordination of several messages, so persistence is non-essential.
Has anyone else had a similar problem?
How would you approach this?
Thanks!
M