Skip to main content

HOW MUCH WOULD COST ME TO BUILD A SYSTEM TO RUN ON TWO CLOUD VENDORS SIDE-BY-SIDE?

 One common question that I hear lately is: 

HOW MUCH WOULD COST ME TO BUILD A SYSTEM TO RUN ON TWO CLOUD VENDORS SIDE-BY-SIDE?

It is a simple question that a business person has. Nevertheless, the response is not simple. Without running a workshop and invest time to understand the business requirements, the current technology stack and expected quality attributes, providing a cost of building the same solution on another CSP (Cloud Service Provider) is hard.

There are tools on the market that provide the mechanism to assess costs on each CSP or what would be the cost of running the same on-premises payloads inside a CSP. Analogies and mapping between different CSP services can be made, making running cost estimation an easy job.

Useful tools:

The challenge is not the running cost! It is THE EFFORT COST to make a system run on another CSP. It is possible? How much ($100k, $1M, 10% of the initial effort)? 

The complexity of building such a system is higher and, in most cases, can be compared with migration from one cloud vendor to another. Trade-offs like using fewer SaaS services and cloud features of a CSP to provide that cloud interoperability level can impact the quality of the final product. Still, they help us to keep costs under control. All the juice that is provided by a specific CSP is diluted when you use less CSP specific features.

When you want to run a solution side-by-side on two CSP, additional effort is required on:

  1. Architecture
  2. DevOps and Automation
  3. Application Development
  4. Operational and Management
  5. Infrastructure
  6. Testing
The main affected layers of a system are:

  1. Application
  2. Database
  3. Infrastructure
  4. Communication
The actual cost of a side-by-side solution
I had the opportunity to discuss directly or indirectly with 51 cloud experts with solid experience with the cloud (Azure, AWS and GCP). Each of them provided input related to the additional cost of building a system that side-by-side VS a system that runs only on one CSP.

The additional effort per layer:
  • 30% for the Application layer
  • 25% for the DB layer 
  • 10% for the Communication layer
  • 15% for the Infrastructure layer
The additional work per work type:
  • 30% for the Architecture
  • 20% for the DevOps using Terraform
  • 70% for the DevOps with cloud-native solutions (e.g. ARM, CloudFormation)
  • 50% for the Operational and Management
  • 10% for the Testing
  • 30% for the Development
  • 25% for the Database
The monthly running cost of a solution side-by-side is not 2 x 100% because tradeoffs need to be done. Taking this into account, the running costs are:
  • 215% for the cloud running costs in the best case
  • 250% for the cloud running costs on average
  • 300% for the cloud running costs when you don't use SaaS and PaaS services anymore, and you need to use only IaaS services

The discussion and estimations were built for the following type of system: A standard business application, built using Kubernetes and Docker, using an RDMS DB, where an ESB and REST API endpoints are used for external communication. In front of the system, an API Gateway and a Load Balancer is required. A VPN connection exists between the cloud and the on-premise office together with basic cloud-native monitoring tools. 

Conclusion
Taking all the previous effort estimations into consideration and the effort required to develop a cloud solution, we expect that to develop a side-by-side system that runs on AWS and Azure would require:
  • 35% additional effort to build and design the solution
  • 50% additional effort cost for Operational and Management
  • 215% additional cost to run the solution on AWS and Azure, side-by-side

Comments

Popular posts from this blog

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

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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