Microsoft.NET Service Bus.

Introduction to Microsoft .NET Service Bus.  This  is part of Microsoft  Windows Azure Cloud Operating System.

Microsoft .NET Services bundled with the following  three  components .

1. Service Bus.

2. Access Control service.

3. Workflow Service.

In this blog I am going to write about only  the Service Bus.

Service Bus: 

The Microsoft .NET Service Bus makes it easy to connect applications together over the Internet so it is also called ISB -Internet Service Bus. Services that are registered on the Bus can easily be discovered and accessed, across any network topology. The .NET Service Bus provides  the application pattern which is similar to the  Enterprise Service Bus.

while helping to solve some of the hard issues that arise during implementation of  this pattern across network, security, and organizational boundaries, at Internet-scale.

For example let us say if two different companies wants to do business over the web, this requires  both of the companies need to expose some services which is shared  by each other. The application integration might involve mutual consumption of the services which requires complex net architecture because of the their networks zones. In order to facilitate the process , the  developer needs to build complex layer in their application like NATs , Firewall etc. Now here comes Microsoft .NET Service Bus to rescue from this issues . 

Microsoft .Net Services addresses the above common problem with the help of .NET Service Bus, which provides a communication infrastructure that developers can make use of when developing such complex applications/services. Service Bus hides the complexity of the firewall/router/NAT and enables to host the service in the cloud. The client can then connect to the service through the Service Bus. However, the messages exchanged in a Service Bus are always authenticated and trusted. The Access Control block provides a Security Token Service (STS) which provides Identity and Management Service.

The Microsoft .NET Service Bus built on Windows Communication Foundation -WCF . right now its supports the following  bindings.

1. WebHttpRelayBinding

2. BasicHttpRelayBinding

3. BasicHttpRelayContextBinding

4. WSHttpRelayBinding

5. WS2007HttpRelayBinding

6. WS2007FederationHttpBinding

7. NetTcpRelayBinding

8. NetOnewayRelayBinding

9. NetEventRelayBinding

Here I provided Microsoft.ServiceBus Namespace Explorer view. this shows all binding classes which is listed above.



Here is the list of supported  Transport Client Credential Types.



How to get an Account on  WINDOWS AZURE:

please visit https://connect.microsoft.com/site/sitehome.aspx?SiteID=681 page and apply .

Once you get the Invitation token code from Microsoft Windows Azure Team  you need to have provision (Create) account / solution in Azure.  please click the image below it will take you to  Windows Azure Services Platform and use your key to enter .

 

  Once you create a solution then  you will have access to the following listed  Azure Services.



Now time to download the  SDK and play with it .  so let us point your IE browser  where you can download .NET Service Bus SDK

.NET Service SDK

I have  developed an application which hosts or creates a simple WCF service on  .NET Service Bus.  It is a WPF application with simple WCF  Service Contract defined.

 

In my Next blog I will show how to implement both  Service and Client.

I love  WPF and SL 2.0  this two can  Brings our Imagination into Model.

I have build  the WPF (WCF service hosted)  Application which ask your  Solution name and password once authenticated with .NET Service bus it shows the  image  you see in screen shot.



The below screen shot shows  the WPF Client calling WCF service which is hosted in .NET Service  Bus with  netTcpRelayBinding and response from the .NET  Service Bus.



Thanks

SreenivasaRagavan.