Skip to main content

Azure Price estimation - what you need to take into account

Calculating the cost consumption for a solution that runs in cloud can be sometimes challenging. First of all you need do a forecast of how many resources are required and secondly you need to put on the paper all things that are billable by the cloud provider.

Azure Price Calculator
The pricing calculator offered by Microsoft for Azure is a nice tool, that helps you to take into account all the items. It is able to persist the cost even if you close the tab and when you are done you can export it to an excel file. For basic estimations is good, but I expect that you'll end up pretty fast with a complex excel.

Excel Calculator
In the last few years, I was involved at least 2 time per month in Azure consumption estimations for different projects - from the small one that consume a few hundreds of euros per month to big ones where you end up with a bill that has six or seven figures per year. 
You'll find different templates on the internet that you can use and don't be surprise if you end up creating your own template.

Tips and Tricks
I have a list of items that I take into account when I do price estimations for Azure. It doesn't covers everything, some things I ignore and other I consider them by default added them to the cost estimations. It's only a checklist for me, that I decided to share with others.

Things to consider
  1. Special support from Azure (premier support)
  2. In general computation is the main driver cost, but don't be surprised is traffic will also be around 20-30% of your cost, especially in IoT era
  3. Development, integration, testing environment also cost money, deallocate them when you don't use them
  4. Development, integration, testing environment don't need to run at full capacity
  5.  Select the right tire - to big is just waste of money
  6. Change the tier based on your needs (not only VMs, also SQL tier)
  1. VMs disk are not included in VM price and needs to be included in estimations. You pay only what you use
  2. Outbound traffic from VM
  3. The minimal number of VMs of computation units is 2, never 1
  4. Scale down when you don't need all the power

  1. Outbound traffic for Azure Storage (blobs, Azure Table)
  2. Outbound traffic when you do a sync between two different Azure Regions (storage, DB, ...)
  3. Storage cost for backups
  4. Cost of transactions, especially on Azure Tables
  5. Size of the logs
  6. Use CDNs as much as possible
  7. Non-critical use cases can implement a back-off mechanism for cost optimization (reduce number of transactions)
  1. Storage cost of SQL Azure backup
  1. Outbound traffic for Service Bus, Event Hub and other messaging system
  2. Number of events price for Event Hub
  3. Number of messages for Service Bus
Azure AD
  1. Number of users 
  2. Multi-factor authentication
  3. Number of applications
Service Fabric
  1. Minimum number of VMs in cluster (is not 2)


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 …

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.

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…