Rhino Service Bus – Starbucks Example Updated

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.

Message/Service Bus – Mass Transit

 

I’ve been reading several blogs about event-driven/event broker/message bus.  I have used the Castle Windsor EventWiringFacility which allows you to setup a component to publisher with subscribers defined either in the xml or through the windsor fluent interface.  I have blogged about that here.

Taking this a step further is the concept of an event ‘broker’ or ‘message bus’ – where messages are published to the broker that then can send these to subscribers (in a publish-subscriber setup) without setting up delegates/events for the publisher.  One such message bus available in .net is ‘Mass Transit’.

MassTransit is lean service bus implementation for building loosely coupled applications using the .NET framework.

The lean implementation is supported by the YAGNI principle. By focusing on a tight set of specific concerns, the touch points between Mass Transit and the application are minimized resulting in a clear and concise set of interfaces.

Mass Transit offers a ‘how to get started’ example that shows how rather easy it is to get this setup.  In this example it uses Castle Windsor.

I’m a tad bias (lol) toward Castle Windsor, as I find it easy to setup and use, and quite powerful.  The community offers several options, in this case, Mass Transit has started with Castle Windsor and provides a good set of examples to get started.  Using an IoC container makes it very easy to register components to be used by the message bus.

The next step will be create a sample with a test to get this rolling…  off I go, to the Mass Transit wiki to get it all set up…

Edit:  a good ‘how to get msmq installed’:

http://msdn.microsoft.com/en-us/library/aa967729.aspx

Then, ‘setting up the ‘standard-services’ for Mass Transit’:

http://masstransit.pbwiki.com/Standard-Services

Also, a ‘Using the host service’  –

The Host service allows the easy configuration of a Windows service for handling messages on the service bus

http://code.google.com/p/masstransit/wiki/UsingTheHostService