Cloudeasier cloud costs indicator: Methodology

Introduction

Beeing always up to date about public cloud costs might be really tricky. When you combine the number of regions, the number of providers, the number of lines in their service catalogue and the different buying options that each one of them propose, you have millions of scenarios to compare. And when you add to this the evolution of all those elements every week… it’s getting really challenging.

But you know what? Challenge accepted! 

Cloudeasier as created the C3I: The cloudeasier cloud costs indicator. Each month, Cloudeasier will publish an updated indicator, to give you deep insight of the pricing strategy and position for Amazon Web Services, Microsoft Azure and Google Cloud plateform. Additional providers will eventually apear within the next weeks. 

 

How it works?

Using our calculator app.cloudeasier.com, we will do the quotation of 3 different templated plateformes.

This calculator is updated daily with the full pricing catalogue from Azure AWS and GCP. And it detects for every need, the best template / config / pricing model to use (ie the cheapest that fit the technical needs). 

The C3I will be based on:

– For each template, the cheapest zone of each provider in Asia, US and Europe (The app works with all continents / countries, but for C3I, we are trying to have a synthetic view)

– A global indicator that will be the average of the 3 plateformes. 

And we will compare month to month the evolution of the results and explain why it changes (pricing update, new templates, new buying model, etc…)

Also, in S2 2020, we will add to C3I other tempalted plateformes with more PaaS services (functions, landa, K8S and Database as a Service)

Want to know more about the templated plateformes? let’s continue. 

 

 

Plateforme 1: Web App

If you are developing web applications, you probably have a platform like this. With each deployment of new web application projects, companies do the costing exercise of this platform. indeed, it is composed of:

  • Two Back servers and two other fronts of 4 CPU 8 GB of ram for production. It is often interesting to reserve servers for this type of use, since they are used 24/7 all month. so we have taken 1 year of commitment on these servers.
  • Two other less powerful servers for back and front stagging with 2 CPU 6 GB of ram, typically these servers are not used more than 100h per month because they are used only at the time of preproduction.
  • A stand-alone server of the same configuration as the stagging, which will be used for user acceptance tests and whose use will not exceed 100 hours
  • A 4th server for the development of the web application, with 2 CPU 6GB of ram which will be used more than the stagging and recipe servers. This server is used by development teams during working hours and working days, in this case 230 hours per month.

The shared cpu machine templates have very competitive prices compared to the other dedicated CPU template. So we have left the possibility of using this type of template for non-production environments.

For storage, all servers will be equipped with integrated storage of 50gb for the installation of the operating system. in addition to a 100gb disk whose performance can operate databases.

Plateforme 2: Software Package

Another platform typopology widespread use. Indeed it is a platform for software integration and deployment. 

We have chosen a generic configuration that can support a wide range of software:

  • Two large servers with SQL Entreprise license for the management of the production database, equipped with 6 CPU and 24 GB of ram. We associated a 50gb disk for the OS, and a 1TB disk with data base performance.
  • Four servers with SQL standard license for preproduction, wihch the usage doesn’t exceed 100 hours per month. They are equipped with 4 CPU and 12 GB of ram. We associate a 50gb disk for the OS and a 100GB disk with data base performance.
  • A server with the same configuration as the preproduction servers, which will be used for software integration, wihch the use will be set at 230 hours per month

 

Similar to the web application platform, non-production environments can be equipped with shared CPUs.

Plateforme 3: File share

Companies often use file servers to centralize stored data and manage file versions, but not only that, file servers have even more advantages in both security and ease of access to files.

We have chosen a typical file server platform:

  • 2 production servers, equipped with 4 CPUs and 16GB of ram, the main use of which is to manage file storage of 4 TB With database perfomance.
  • 2 other servers for the preproduction of the same configuration as the production but whose storage is reduced to a 500GB disk with data abse performance.

This platforme must be accessible all the time and its use is crucial for the proper functioning of the business, reason enough to take the best possible purchasing method: a 3-year commitment on the machines and a full upfront.

Share on facebook
Facebook
Share on twitter
Twitter
Share on linkedin
LinkedIn
Share on whatsapp
WhatsApp
Share on email
Email