Skip to main content

Service Bus - Introduction to Service Bus of Windows Azure

With the last versions of Windows Azure, Service Buss from Windows Azure updated and having a log of new features. I will write a series of posts about Service Buss from the Windows Azure.
I saw that there are a lot of persons that don’t know what Service Buss is. So, let’s try to define what Service Buss means in general.
Service Bus is an architecture model that is used to create applications (or modules) that need to communicate and interact between each other. The way that they are communicating is asynchronous and they are oriented to a design that uses messages. Any kind of communication between components is made using messages. One important feature of Service Buss, it that a specific message is sends to the Service Buss, without specifying a specific receiver. Based on the message the Service Buss can broadcast the message to one, two or 10 listeners.
In the current version of Windows Azure we have three types of Service Bus:
  • Service Bus Queues
  • Service Bus Topics
  • Service Bus Relay
Service Bus Queues use as the name say, use a queue to communicate between the sender and the receiver. In this way the sender (the producer) don’t need to wait the message to be consumed by the receiver and can working. The receivers are able to pull from the queue messages that were send in the same order that the producer added to the Service Buss Queue. This type of communicate support a brokered messaging communication model.
One important think that we need to notify at this type of service bus is the numbers of consumers for each message. A message will be able to be consumed by only one consumer, and only one.
The next type of service bus is Service Bus Topics. From the perspective of the producer it is very similar. The consumer creates a message and sends it to the service buss. The consumer of this messages need to as for the Service Bus Queues register to the service bus. We will be notified each time when a message is available in the service bus. The main difference is the numbers of subscribers that can exist for each message. In the Service Bus Queues we had only one, but in this type of Service Bus we can have multiple subscribers. Each message will be send to each subscriber.
This type of communication is one-to-many and represent the publish/subscribe communication model. When we will talk about this type of service bus will describe how it was implemented.
The last type of service bus is Service Bus Relay. This last type of service bus doesn’t use messages as we expect. He helps us to create WCF services for applications that are hosted on on-premise servers not only in cloud. It offers us a safe method to expose WCF services from our on-premise servers and accessed from cloud or by other clients in a very safe way. It enable us to secure the access to services and offer access to WCF services without creating custom rules on our on-premise network and firewalls. Using this feature we can very easily and safe expose WCF services from our private networks without having security problems.
We saw what kind of Service Bus exists on Windows Azure. In the next series of post we will talk about each of one in details.

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…