Skip to main content

Communication Strategies on top of message base communication for outages or disasters protection

In the last post, we identified different location inside and outside a micro-service architecture where messaging base communication could be used with success. Beside this we identified that to be able to have a high-performance system, we need to use reliable messaging communication channels.
If we decide to run our micro-service solution inside Kubernetes on top of Azure Kubernetes Services (AKS), we need to take into consideration messaging and event bases communication channels like Azure Service Bus or Azure Event Hub.
Even so, this is not enough to be fully protected of any outages or disasters. Another layer of protection that we should define is at the application level. In this post, we will discuss some communication strategies that can increase our protection against outages and disasters.
The below solutions can be used in combination with any messaging system, but in this case, we will present them in combination with Azure Service Bus.

Passive Replication
This strategy is based on two instances of messaging service instances that run in parallel. In one moment in time, the sender is using only one to send messages – so called the active one. When the sender is not able to communicate with the active instance, it will automatically switch to the second one (called passive), that will be marked as active. Basically, it is a switch between active and passive instance. An active instance remains active until a communication problem occurs.
The consumer needs to listen and consume messages from both messaging service instances – active and passive. Because there is a risk to receive the same message on both channels (active and passive) the consumer needs to have a mechanism to identify messages that were already processed.
There are cases when business is not effective is a message is processed twice. If your business or performance it is not affected by processing the same message twice, then you should not handle this scenario.
If the message order it is important for you, please take into consideration that there are cases when by default the message order might not be respected. For example, if the sender sends message A to the active instance that becomes unavailable for a few seconds and sender send messages B and C over passive instance (that becomes active), the receiver might receive message B and C before message A. Based on what kind of messaging solution you used, you might have a mechanism that protects you for scenarios like this. Azure Service Bus allows us to put a group together multiple messages under the same session, protecting us from this kind of scenarios.
Another case is when a message is pushed to the active instance and the send confirmation is not received anymore because the active channels go down. In this case, the message will be sent on the second channel also. For this situation, the receiver needs to be able to detect duplicate messages and decide how to handle them.

Active Replication
This approach involves using two instances of messaging services (like to different instances of Azure Service Bus namespaces) to send messages between sender and receiver. The sender sends the same message twice on both message instances.
Each message needs to have a unique ID that it is used by the receiver to detect the message duplication and suppress the second one. When you are using Azure Service Bus, you can use custom property tag, the Label properties of the message or even the BrokeredMessage.MessageId to set the ID used to detect the message duplication.
From a cost perspective, Active Replication is more expensive than the passive replication because you send the same message twice, but increase the protection to disasters or outages. Considering your business needs and NFR you should decide what approach suits best your needs.

In the next post you'll be able to find a comparison between messages vs event base communication system.


Popular posts from this blog

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 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 …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.