nservicebus

Is NServiceBus a ESB or lightweight ESB at all? or is it more like WCF with durable/ reliable messaging? It looks to me more like a messaging framework than ESB. just want some pointer as I am just started looking into different ESB products and what they are able to do or not. Chris Bednarski NServiceBus is definitely an ESB. Full Stop. Enterprise Service Bus, a Bus, meaning a thing that allows, by design, for components of a system to be distributed and work independently. The bus itself is also distributed. A failure of one component or service doesn't affect the availability of other

Is there a way to using NServiceBus with Asp.Net MVC 2? I want to send a request message from a Asp.Net MVC2 Application to a Service, which handle the message and reply with a response message. is there a way to do this clearly? Udi Dahan If you really want to do this, here's how: var sync = Bus.Send<SomeMessage>(/*data*/) .Register((AsyncCallback)delegate(IAsyncResult ar) { var result = ar.AsyncState as CompletionResult; // do something with result.Messages }, null ); sync.AsyncWaitHandle.WaitOne(/*timeout*/); Andreas Öhlund There is a reason that NServiceBus only supports registering

Would someone be able to shed some light on the differences between the newly release Windows ServiceBus (on premise, not Azure) and NServiceBus? Looking for a detailed answer what the windows SB may be missing as I'm familiar what NSErviceBus can do: Is it a real service bus and not just a message broker that uses queues? Can it support message polymorphism? (Messages subclassing other messages and handlers supporting this hierarchy Long running processes and correlation Scale out I'm responsible for the Windows Azure ServiceBus support in NServicebus. And in my opinion this new Windows

My ASP.NET MVC3 / NHibernate application has a requirement to fire off and handle a variety of events related to my domain objects. For example, an Order object might have events like OrderStatusChanged or NoteCreatedForOrder . In most cases these events result in an email being sent, so I can't just leave them in the MVC app. I've read through Udi Dahan's Domain Events and dozens of other thoughts on how to do this sort of thing, and I decided on using an NServiceBus-based host that handles event messages. I've done a few proof-of-concept tests and this seems to work well. My question is what

Update: The most current licensing info can be found here: http://particular.net/licensing So, I am reading the license restriction for NServiceBus Community Edition. It says: Production use is limited to a single server with no more than 4 cores. Does that mean that all the subscribers and all the publishers need to be running on a single server? Or does it mean that each server that is either a publisher or a subscriber can have no more than 4 cores? I am hoping it is the later as we had planned to use NServiceBus to allow several applications (and services) running on several different