17 criteria to choose a cloud service provider for your company

Recently I had the mission to decide which cloud provider my company was to adopt. After taking a deep look at the capabilities, benefits, and other key important points of the three main clouds in the market (Azure, Amazon, and Google), I was very excited about the result and the effort put on and decided to share so it could help more people. This is a decision matrix developed to take the decision in my company. I strongly encourage you to inspire in this one and make the needed changes for yours. I hope it helps you to take your own decision as well. There are three main areas in this article: 1) Define the goals of the journey, 2) The spreadsheet, 3) the Adopted Criteria, and 4) the Final Decision.

1 — Define the goals for the cloud journey

  • Overall company speed — essential for keeping competitive time to market.
  • Teams autonomy — one more important move to keep time-to-market as fast as possible and to foster DevOps adoption.
  • Cost savings — use the cloud benefit of the pay-as-you-go.
  • Enable software scalability — some of the products still suffer from on-prem challenges to scale.
  • Security — improve security while handing over a few of the key concerns to the cloud provider.
  • Better infrastructure costs management
  • Keep auditing key aspects valid — eg.: PCI compliant.

2 — The spreadsheet

3 — Define the criteria list

Five is the highest possible score. One is the lowest. Any other number between those are valid scores.

* These items were not included in my initial analysis and were suggested by a couple of friends using the model. I’m bringing them here as a few more suggestions for you.

2.1. Cost

Why this criterion is important: Since the cloud move is an already taken decision, the goal of this criterion is to evaluate which cloud is the cheapest for this specific scenario need.

2.2. Feature count

2.3. Oracle migration ease

2.4. Available SDKs

2.5. DDoS protection

2.6. Security overall

Source: Three main sources from security experts blogs were used to this evaluation:

2.7. Machine Learning and Data Science features

2.8. Community

2.9. Professionals availability

2.10. Professionals cost

2.11. Companies already present in each cloud

2.12. Internal team knowledge

2.13. Auditing capabilities

2.14. Cloud migration products

4 — Conclusion

This adoption must also come hand-by-hand with an internal plan to improve people’s knowledge of the selected cloud. The cloud brings several benefits compared to on-premises services, and like everything in life there are trade-offs and new challenges will appear.

Sharing experiences on IT subjects. Working for AWS. DevOps, Kubernetes, Microservices, Terraform, Ansible, and Java