in 2006 Azure Historical enterprise partner with Windows & Office 365 Started in 2010 with SQL GCP Challenger since 2011 Launched AppEngine in 2008 Launched GKE in 2014 Market Penetration
◦ SLA on network / connectivity (99,99%) • GCP ◦ SLA on VM & Network / connectivity (99,99%) Quality / Availability HA & Fault Tolerance • AWS & GCP ◦ Distribute VM across AZ ▪ enhance availability ▪ enable HA or Fault Tolerance • Azure ◦ Availability Set do it for you
level • File & Object Storage at application/API levels Object storage from Short Term → Long Term → Tape • New protocol created by AWS: S3 ◦ API became a standard de facto • Policies to migrate automatically to cheaper storage Storage : No limit Free to add data, cheap to store, expensive to retrieve Storage
to 99.99% (depending on storage classes) AWS Refund up to 100% GCP Refund up to 50% •Storage durability: 11 9’s Means replicated at least 3 times SLO & SLA - Everything fails, all the time (Werner Voegels) Azure •Network availability: Starts at 95% oStorage availability: 98.0% to 99.99% (depending on classes) (economy !?) Azure Refund up to 100% oStorage durability: from 11 to 16 9’s
isolation ✔ Multitenancy Late release of EKS --2018 in US Enables fully shutting down a cluster easily Optimizes cost CI/CD… needs custom integration with Lambda Allows different scaling pools with pain CaaS - AWS
Instances) Max 400 nodes / 8 pools (GPU, CPU, …) No private cluster, no access to master, no HTTPS for API access on master Perfect integration with Gitlab & Azure DevOps integration channel: •Service Account, •Namespace •Environment CaaS - Azure
• Runs outside of the cluster Azure: Service Fabric Mesh • capability added to Service Fabric • incompatible with K8S • Native integration with dev. pipelines • Azure SMI: brand new spec for SM GCP: Istio • Leader • Wider adoption • Works “virtually” everywhere • Runs inside the cluster
leader : Greater coverage of services •Kubernetes (multi-cloud) •Infrastructure •Pricing : In previous mode Pay-as-you-go package in use •Operations done by you or service provider Hybrid - Azure
2019 ◦To do What ? For the ELB / ECS / EKS / EMR /(big data) / RDS •Appliance including PaaS •VMWare or equivalent based •Unknown pricing •Operations done by AWS •Compliant Vmware API Hybrid - AWS
of services •Very large set of ML/IA services •IaaS oriented Clouder Strengths AZURE •Hybrid solution •Easiest migration •Great for windows-based organizations •Dev & PaaS oriented GCP •Mastery container model •AZ eco-conscious option •ML research / Best algo for ML/IA •StackDriver •Dev & Container oriented
they really have in common? What are their major differences? Is the choice for one of the 3 a question of heart, available skills or technical abilities?
each of these platforms. So going around the 3 in an exhaustive way during a talk is utopian. We will therefore get to the point and focus on the major services, the most used and for which the comparison is the most interesting.
the Cloud & Technos department of Capgemini Sogeti ATS and work necessarily, every day, in these environments. Without ever drawing a tight line between our playgrounds with the objective of challenging ourselves on a daily basis on the implementation of good practices.
different access? • Trust over control AWS •Cognito •Directory service •TrustAdvisor •1 out of 5 major pilars GCP •Directory Management •Cloud identity . Directory Service pour tous Azure •Active Directory •Windows based •Easily breakable IAM