3 ms·

Seems like Azure and GCP are growing at the same rate of 27% despite the size difference. Looks good for Azure.

onlyrealcuzzo 4y ago
Azure is mostly Office 365 & Cloud is mostly gSuite - so I'd caution against saying "GCP" and pretending like these are good comparisons to AWS. Azure & Cloud probably are decent comparisons to each other, though.
- bloodyplonker22 4y ago
  I have never met a person who called GCP "Cloud" like it was the authoritative cloud.
  - pesfandiar 4y ago
    I suppose they're referring to line items in each company's earnings report.
- mfer 4y ago
  Azure and Office numbers are separate in the announcement.
- phillipcarter 4y ago
  I doubt someone who works in accounting would confirm on this site, but the O365 stuff is categorized differently than Azure. So I don't think it's an office suite underneath a compute platform's trenchcoat.
  - SvenL 4y ago
    It depends, if you buy an Office365/Microsoft365 subscription with SharePoint and the other stuff you also get an Azure AD for authentication, including an Azure Subscription. So you’re also an Azure user…
ArchOversight 4y ago
As a user of AWS/GCP/Azure, Azure is the one where we have the most issues, the most services that somewhat work but never right and where it is the biggest pain to actually get up and running successfully. We've also run into a lot of random limitations that are massive pain points in building automation against Azure where there's a mixture now of terraform, Powershell, and Azure Resource Manager templates to try and enforce state. We have also found that we are spending almost 25% more in Azure for similar compute capabilities as we've had to launch more servers to meet expected baseline performance (or pricier systems). The lack of proper AZ's in certain locations is also a huge bummer, on top of that, we've found that in certain regions you will have certain instance types that are available in one AZ but not the other. So you end up having to find somewhat equivalents and rewrite infrastructure as code to deal with that mess. Last but not least is the fact that GCP and Azure both don't have great support for IPv6. AWS may have been late to the game, but it's easy to deploy, and it just works. Whereas in GCP you have to be in certain regions, and in Azure I still am not sure what they were smoking with giving such a tiny public IPv6 prefix: https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-address-prefix https://learn.microsoft.com/en-us/azure/virtual-network/ip-s...
- gxt 4y ago
  Doing any but pure ARM or blueprint/arm on Azure is shooting yourself in the throat.
  - ArchOversight 4y ago
    That's great and all, but I need it to integrate with terraform because then I can easily connect it up to our other cloud providers, and setup DNS and stuff like that automatically across the clouds. Azure's terraform provider is also not the greatest, unfortunately.
- victor106 4y ago
  I agree with this. Been using AWS and Azure for a long time and only recently started using GCP. I was surprised how fast GCP services and resources startup. On AWS/Azure it takes more than a few for VM to spin up but on GCP it feels like a few seconds.

Azure is mostly Office 365 & Cloud is mostly gSuite - so I'd caution against saying "GCP" and pretending like these are good comparisons to AWS. Azure & Cloud probably are decent comparisons to each other, though.

bloodyplonker22 4y ago
I have never met a person who called GCP "Cloud" like it was the authoritative cloud.
- pesfandiar 4y ago
  I suppose they're referring to line items in each company's earnings report.
mfer 4y ago
Azure and Office numbers are separate in the announcement.
phillipcarter 4y ago
I doubt someone who works in accounting would confirm on this site, but the O365 stuff is categorized differently than Azure. So I don't think it's an office suite underneath a compute platform's trenchcoat.
- SvenL 4y ago
  It depends, if you buy an Office365/Microsoft365 subscription with SharePoint and the other stuff you also get an Azure AD for authentication, including an Azure Subscription. So you’re also an Azure user…

ArchOversight 4y ago

As a user of AWS/GCP/Azure, Azure is the one where we have the most issues, the most services that somewhat work but never right and where it is the biggest pain to actually get up and running successfully. We've also run into a lot of random limitations that are massive pain points in building automation against Azure where there's a mixture now of terraform, Powershell, and Azure Resource Manager templates to try and enforce state. We have also found that we are spending almost 25% more in Azure for similar compute capabilities as we've had to launch more servers to meet expected baseline performance (or pricier systems). The lack of proper AZ's in certain locations is also a huge bummer, on top of that, we've found that in certain regions you will have certain instance types that are available in one AZ but not the other. So you end up having to find somewhat equivalents and rewrite infrastructure as code to deal with that mess. Last but not least is the fact that GCP and Azure both don't have great support for IPv6. AWS may have been late to the game, but it's easy to deploy, and it just works. Whereas in GCP you have to be in certain regions, and in Azure I still am not sure what they were smoking with giving such a tiny public IPv6 prefix: https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-address-prefix https://learn.microsoft.com/en-us/azure/virtual-network/ip-s...

gxt 4y ago
Doing any but pure ARM or blueprint/arm on Azure is shooting yourself in the throat.
- ArchOversight 4y ago
  That's great and all, but I need it to integrate with terraform because then I can easily connect it up to our other cloud providers, and setup DNS and stuff like that automatically across the clouds. Azure's terraform provider is also not the greatest, unfortunately.
victor106 4y ago
I agree with this. Been using AWS and Azure for a long time and only recently started using GCP. I was surprised how fast GCP services and resources startup. On AWS/Azure it takes more than a few for VM to spin up but on GCP it feels like a few seconds.