Thanks very much for your kind words.

It is great to have guys like Udi explaining the difference between brokers and bus and the separation of concerns and business rules, it really saves you alot of pain and time from implementing the wrong thing as I learned the hard way. Specially when you learn how much pain it is to scale out or change when everything is in one center place(broker) and things do change quickly and then we learn the value of being agile to go with the change.

I think alot of people think of Biztalk or EAI(brokers) as the only way to do things, but we can do it more simple, faster and pragmatic depending on the need for the solution using a bus.

Thanks for asking for more examples as we devs enjoy it more by learning from examples in the real world.

RT

I listened to this the other week. Well done.

Just wanted you to point me to a broker vs. bus online post that you think would be a good source of an example and explanation. I’m currently looking at a solution where brokering is being favored to busing.

Cheers,

Adam

Thanks for the feedback – I did wish that I could have gotten into more detail but I trusted Scott to direct the discussion to what would provide the best value for his audience – and I think that that goal was achieved.

Can you let me in on this “sexy” example which would “make more people sit up and take notice” ?

I have just listened to the show it’s great that you are spreading the word like this.

If I can offer some constructive critism….

When you’re explaining the message bus concepts you often talked in abstract terms, this is good but it helps mere mortals like me understand things with real world examples. You did some classic examples like the sales order system, maybe some sexier examples would make more people sit up and take notice.

The other thing is the benefits that come from using nServiceBus (or any message bus) weren’t clear enough. We have been able to solve problems that were unsolvable without either a massive development effort or using nServiceBus. We send messages from our back office to a service with a cache that can respond to requests in timely fashion without worrying about slow DB lookups. The inspiration for this solution came from your article on how to use nServiceBus to perform high performance user authentication in a web farm.

I did take a lot of useful information from the interview, we are looking to retrofit nServiceBus into our architecture and have adopted the ’starting at the edge’ approach.

Can nServiceBus have any role in a Silverlight application?

Thanks

Dave