Ayende has done it again Now, he has a Service Bus in place â€“ with an example in the repository, the â€˜starbucks exampleâ€™
From his post:
There is zero setup necessary, Rhino Service Bus will create the queues if they donâ€™t already exists. Again, the idea of reducing moving parts. All three actors are running in the same process â€“ but each is running in a different AppDomain.
Note that this is a common deployment choice for development, but not one that I would use for production.
The idea is that this make it significantly easier to debug & develop a distributed application.
There is very little configuration whatsoever. And a lot of conventions about how to figure out what consumers to use and how to build it. The use of sagas & conversations is demoed. The entire buying process is a single conversation composed of several sagas. The customer actor is showing how we can create instance & temporary subscriptions.
I really appreciate the setup of Rhino Service Bus, fantastically done! This is a good â€˜simpleâ€™ service bus implementation. Ayende discusses why he created this with NServiceBus/MassTransit around â€“ mostly because he didnâ€™t need all the features of these full blow engines, as well as easier setup, etcâ€¦ which is where I think most my needs fall as well.
Ayende has blogged about this service bus, here is the Rhino Service Bus rss feed for more information.