NServiceBus could be seen as similar to JMS at some level I suppose, but the programming model ensures things like message ownership that are missing from JMS and matter a lot at larger scales.

People have actually started asking for a Java version of NServiceBus as they find its programming model quite attractive.

I think the NServiceBus (NSB) counterpart in the Java world is the JMS API, this API also enables the Pub/Sub and Point-to-Point communication style. However the programming model is a bit different.

The NSB is more closely related to the distributed systems concept of an Message Oriented Middleware is like a high-level abstraction of the concept.

can you recommand some books about soa?

thx

Until I heard about NServiceBus ( a few week ago), I didn’t even know there was something like that for .NET (and no, Biztalk is not an ESB). In the “Java” world there are plenty of ESB products, some “native” and some pure Java. IBM has 3 “ESB” products alone.

Ultimately the transformation feature set belongs to the domain of brokers and application integration – which is exactly where BizTalk works great. While many ESB products tout similar abilities, that is more a function of their broker history than of the Bus Architectural Style.

Have you seen the page describing the combination of NServiceBus and BizTalk where each of their strengths amplifies the others:

http://www.nservicebus.com/InsteadOfBizTalk.aspx

How Biztalk/ESB 2.0 fits this division? ESB 2.0 per se focuses on the connectivity / interop / message shapes issues. So if you see it as a different offering than Biztalk and its orchestration capabilities I think it has similarities to the Java separation.