Skip to main content

Scaling Unit - Why we should not have a master unit

In the last post we talk about the base concept of a Scale Units. In today post we will go further and talk about why we can end up with different types of scale units based on application needs.
Until now we defined a scale unit as a group of resources that are grouped together to server a specific number of clients.
This will work with success for application that can have scale units that are 100% independent and are not managed by an authority.
Let’s imagine the following scenario:
We need to create an application that pushes the same binary content to clients when an administrator decide.

It is pretty simple to define a scale unit that manage a X number of clients. This scale unit will contain the content that needs to be pushed to clients replicated as many as time needs to satisfy the SLA required by each client connected to that scale unit.

But there are some steps that need to be done before a release of a binary content can be done. For example we need to be sure that the binary content was downloaded with success by all scaling units. Also, we need to be able to control from only one point the release of a specific binary content.
If all this are not enough, when a client needs to be registered into the system, he will know an initial registration endpoint that will need to help him to find the scaling unit that will manage him.
Based on this requirement, we can already identify another type of scaling unit that will need to handle this functionality. Let’s call this scaling unit “Global Unit” – GU. The scaling units that handle our clients can be called “Client Unit” – CU.
The Global Unit will be aware all the time about the rest of the Client Units and will need to manage and communicate with each scaling unit.

This approach can be risky, because Global Unit can become a bottle neck. In case something goes wrong on it we will not be able anymore to trigger a global push of a binary content. Scaling a Global Unit is not an easy job, because it is the master controlling unit over the rest of our scaling units. We can have an Active-Active or Active-Passive failover mechanism at Global Unit, but it will be a hard thing to do because we’ll need to replicate content and storage between Active and the Passive (Active) unit (We will talk more about Active-Active and Active-Passive topic in another posts).
This is a risk that we need to accept if we will go on an approach with a Global Unit that manage and control Client Units.
It is important to know that not all the systems needs a Global Unit that control different commands over all Client Units - like a binary content release or redirect clients at the first handshake to their Client Unit. 
In general I would try to make everything that is possible to avoid having a Global Unit.

Our main scope should be to define scaling units that don’t have any kind of contact or shared resources between them or a 'master' unit. In this way scaling, management and control can be made clean and easily.

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(...

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

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.51 EF 6.0.2 VS2013 It see...