3 ms·

I wondered how soon "Coming soon" would be. Now I have to update my recent blog post [0] before the final two parts are even out :) - part two is out tomorrow B

I wondered how soon "Coming soon" would be. Now I have to update my recent blog post [0] before the final two parts are even out :) - part two is out tomorrow BTW. There seems to be a bit of an arms race with Azure right now. The current map [1] has four more regions "Coming soon". Looking forward to London. [0]: https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-confusion-part-1/ https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-c... [1]: https://aws.amazon.com/about-aws/global-infrastructure/ https://aws.amazon.com/about-aws/global-infrastructure/

inopinatus 10y ago
London might be RSN, the EC2 API endpoint for what I'm guessing is London (eu-west-2) is resolvable, reachable and happily 401'ing requests as of a few days ago. Obligatory jest: they'll have to rename it post-Brexit.
- jsingleton 10y ago
  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/ I've updated part one to include the new region, will probably have to update for London again soon - https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-confusion-part-1/ https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-c... Part two is also now out, part three next week - https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-confusion-part-2/ https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-c...
  - 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.

inopinatus 10y ago

London might be RSN, the EC2 API endpoint for what I'm guessing is London (eu-west-2) is resolvable, reachable and happily 401'ing requests as of a few days ago. Obligatory jest: they'll have to rename it post-Brexit.

jsingleton 10y ago
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/ I've updated part one to include the new region, will probably have to update for London again soon - https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-confusion-part-1/ https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-c... Part two is also now out, part three next week - https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-confusion-part-2/ https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-c...
- 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.