3 ms·

Interesting. I made the required EU quip in this post :) - https://unop.uk/azure-eu-regions-naming-confusion/ https://unop.uk/azure-eu-regions-naming-confusion

• inopinatus 10y ago
  Can I suggest you update it to revise this spectacularly misleading statement: "If you have a global presence then getting your content close to users if very important for performance. Azure currently serves more regions than AWS." Azure regions and AWS regions are not cardinally comparable. Their functions and availability properties are not isomorphic. AWS would prefer that you compare AWS AZs to Azure regions, and then they get to claim the larger number. But I don't suggest that either, and the matter of content delivery is another comparison again. The distinctions between the two platforms are significant and well documented, so on reading this my trust in this source declined rapidly. I also flatly disagree with this article about the evils of lock-in. Exploiting a rich platform is a recipe for high productivity and opportunities. Re-hosting an application is rare, fraught with pitfalls, and doesn't create any value. So why optimise for it? In my experience, it's better to choose the platform best oriented to your organisation's culture and principles, and adopt it wholeheartedly.