Session: Micrsoft .NET Service Bus

by mheydt 29. October 2008 15:56 >

This used to be Biztalk services. Good to see that it has evolved into something more useful.

There is a diagram of the Internet Service Bus. Need to get this. Cant find it easy online.

Naming

DNS has some practical constraints: latency, pollution, hosts not services, limited write
Service Bus Naming System: r/w with access control, updates instantly, endpoints not machines
Global naming structure: scheme://solution.servicebus.windows.net/name/...

Service Registry

For service endpoints, not a general directory
solution in name is a root of a hierarchy of feeds
Looks like this also has an rss feed; nice!
Interfaces by WCF ServiceRegistrySettings class
Publishing is done with rest requests to access control, create WCF endpoint, then an Atom feed describing the endpoint (through an endpoint), and then publish. Again, nice!
For the CTP, these are ephemeral. You need to recreate them all the time. Will be sticky later.

Messaging

WCF is the primary programming model (but you can do Java too)
All kinds of bindings
Supports, SOAP 1.1, 1.2, all WS-*, SSL, RM, Streaming, Full extensibility model, WebGet/WebInvoke, Metadata exchange
Not supported: atomic transaction flow, protocol level transport authentication, webscripting behavior, direct tcp modes with RM of WS-* Sec.

Notes on bindings:

NetOnewayRelayBinding is the most used. Requires outbound port 828, although there are workarounds. Routes from client to server one way through the fabric. Just showed a nice demo of a laptop connect just on t-mobile edge receiving messages from a client on the local wifi; very nice.
NetEventRelayBinding. Similar to oneway, but allows two receivers. Topic based model, eventing with multi-cast.
NetTcpRelayBinding: should use for everything. Highest throughput. Introduces an intermediary. Basically, this uses the bus to find the other node, and then direct connections between nodes are established through the relay.
Hybrid mode of the previous. Direct connect without relay, even with firewalls. Predication algorithms used to determine which ports will next be open on NATs. This is pretty cool as it will move between relayed and direct.
WS|Basic|Web|HttpRelayBinding: Uses Http instead of sockets. Connections are pooled.

Some links:

http://msdn.microsoft.com/en-us/library/bb906065.aspx
http://vasters.com/clemensv/PermaLink,guid,92d78bee-2cfd-4a29-95ab-c5abb9b905e7.aspx
http://www.microsoft.com/azure/servicebus.mspx

Some pictures I found: