Skip to main content

Adding extra- complexity to a solution by using too many SaaS of a cloud provider

Context
When you embrace Azure or another cloud provider, you’ll discover an environment that offers out of the box a high variety of options for each type of action that you need.
Let us take computation as an example. If on-premises you would have the option only on top of VMs, where on top of them you would be able to put any other solution that you would like, when you are on Azure, things are looking different.
Beside the classical VMs, on Microsoft Azure you have: Scale Sets, App Services, Functions, AKS (Azure Container Services), Container Instances, Batch, Service Fabric and other Cloud Services (classical Web and Worker role for example).

Problem
Having so many options, selecting the best service for your needs might be tricky. It is not about taking the wrong decision; it is more about selecting the right service for your needs, taking into account your context and expectations.
This is one of the most challenges steps during the initial phases of the project that can ensure the success of failure of a project.

Internal Fight
When you need to decide what are the Azure (cloud) components that will gone be used inside your solutions, in most of the cases there might be a friction between two groups. One of them is trying to go with greatest and latest services and technologies and the other one is trying to go safe, with a classical approach.
A good example is:

  • A solution based on Azure VM Scale Sets, Azure SQL and Azure Storage

vs

  • A solution on top of containers (AKS), with Azure Cosmos DB and Azure MySQL

Both parties are proposing good ways on how you can approach the problem. In the end, you need to draw a risk matrix and see what are the pros and cons of each approach. 

A hidden risk
Having at a click distance an ecosystem with so many services available, the technical teams are driven to use as many services as possible. On one side, this is good, because using SaaS reduce the responsibility of the team, but using to many services adds also extra complexity.
For each service, you need to know the pricing model, behavior, limitations, API, configuration and many more. This might not sounds too much… or not? Because the team will try to use the latest services and create a state-of-the-art solution, you can end-up with 14-16 services mixed up together for a simple solution that could use just one computation solution and a storage.

Example
Let us imagine that we want to develop a system that is processing documents. A classical approach would be:

  1. Azure Storage
  2. Azure SQL
  3. Azure Service Bus
  4. Azure App Services
  5. Azure Batch

Another approach that is good as the first one could contain:

  1. Azure Storage
  2. Azure SQL
  3. Azure Cosmos DB
  4. Azure App Services
  5. Azure Container Services
  6. Azure Functions
  7. Azure Data Factory
  8. Azure Logic Apps

Both solution are correct, there is nothing’s wrong with the first one or with the second one. On the second approach there is an extra complexity layer added by extra services. We need to put this in balancer when we take a look over product requirements and NFRs.

Conclusion
Be careful when you combine too many services from a cloud provider. Each extra service adds extra complexity to the system, making it more complex to manage and develop. There is a thin line between a good solution and over-engineering when you have so many services at a click distance. 

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