Skip to main content

Payload Replication - Temporary and Master of data

There are moments in time when you focus on small things and you might miss bigger and more important things.

Working on a solution that is distributed in multiple Azure Regions across the world we had to replicated binary content (files) in all data centers where our solution runs.
The system that push this content is an on-premises system. In this context we decided to use a temporary location where the content is copied first and from where we replicate the content in other regions.

As we can see, the Temp location is used to replicate the content all around the glob. The system is smart enough to balance the load and if multiple replicas are needed in the same Azure Regions, only one copy will be done from the Temp location.
Once the replication is done, the binary content from the Temp location is removed automatically.

Nothing special until this, until in the moment when you ask yourself what is happening if one of the Replicas is corrupted or something happens and you lose data (partially or totally).
In such a case, of course you can go to the master - on-premises system. But when you work with hundreds of terabits, the check and the recovery of the lost  replica will take a while.
There is no way for our replicas to fetch the data from an Azure location, even if there was a time when we had this content (in the moment when we copied in the Temp folder).

There is a clear mistake on this flow. We don't have a location that can play the role of the master (internally in our system). The on-premises system is an external system that push data. We should still have in our own system a master for this data.

A solution that is complex and requires costs at the development and maintenance is to track all the replicas and when there is a fail, to be able to provide a source from another replica. In this way, we don't need the extra space for storage. On the other hand the solution is complex and might be more buggy.
In the same time, if we take into consideration that from this replicas, there will be a lot of download activity, the real cost is not from storage, it will be from download.

The most simple solution is to have in the same location as the Temp location a 'Master' for our payloads. This master can be used situations when one of our replica is our of sync. The Master can be secured easily for unexpected situations if we activate geo-replication

As we can see, in this moment we have a Master for our content that can be used in the case of a out of sync situation with one of our replicas.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP