Yesterday I finally completed the Starbucks sample for Rhino Service Bus. It is surprising to see how many aspects that little sample required.
There are several of highlights in the sample.
- There are three actors in the application:
- 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.
More posts in "Rhino Service Bus" series:
- (08 Aug 2009) DHT Saga Sate Persisters Options
- (21 Jan 2009) Concurrency Violations are Business Logic
- (19 Jan 2009) Concurrency in a distributed world
- (16 Jan 2009) Saga and State
- (15 Jan 2009) Field Level Security
- (14 Jan 2009) Understanding a Distributed System
- (14 Jan 2009) The Starbucks example
- (14 Jan 2009) Locality and Independence
- (14 Jan 2009) Managing Timeouts