4 ms·

This is really useful for a layman like me who doesn't have a lot of exposure to AWS. Anything similiar for Azure? I would really like to understand the differ

by dcw303 10y ago

This is really useful for a layman like me who doesn't have a lot of exposure to AWS. Anything similiar for Azure? I would really like to understand the difference between the different types of app services, and especially how they relate to the project templates in Visual Studio.

michaelbuckbee 10y ago
https://www.expeditedssl.com/azure-in-plain-english https://www.expeditedssl.com/azure-in-plain-english
- mrweasel 10y ago
  Sadly that one try to be a little too funny. For example: Express Route - "Should have been called Pretty good" that not really helpful. It should have been called "Azure MPLS" or "Azure direct connect"
  - pxndx 10y ago
    I understood that as "that's already a pretty good name".
- jsingleton 10y ago
  That's a good high-level list, although the comparisons don't always match up. For example, I'd say Traffic Manager is more like Route 53 than ELB (which only works within a region). If you're after something a bit more in-depth (but covering less services) then I wrote a three part series last year. It may be a little out-of-date, but most of it still applies. Azure now supports MySQL, for example. 1: 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... 2: 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... 3: https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-confusion-part-3/ https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-c... Edit: Should that "puts da" be on that page?
inopinatus 10y ago
I'd say if you haven't had a lot of exposure to AWS, this list is likely to give you a misleading impression in many cases; many items are either factually or taxonomically wrong, or grossly oversimplified to force them into a particular category, or confuse the underlying implementation (or even unverified assumptions about the underlying implementation) for the service offering. There are also some surprising omissions, like ELB/ALB or KMS, and some impossible and even self-defeating suggestions, like using someone else's trademark (again, with questionable validaty). It's especially misleading if, as you say, you want to understand differences between AWS and Azure services, because that sometimes comes down to nuances. So I recommend treating it as humorous parody, not documentation. It is a little bit amusing if you're already in the know. Source: I'm ex-AWS.

by dcw303 10y ago

michaelbuckbee 10y ago

https://www.expeditedssl.com/azure-in-plain-english https://www.expeditedssl.com/azure-in-plain-english

mrweasel 10y ago
Sadly that one try to be a little too funny. For example: Express Route - "Should have been called Pretty good" that not really helpful. It should have been called "Azure MPLS" or "Azure direct connect"
- pxndx 10y ago
  I understood that as "that's already a pretty good name".
jsingleton 10y ago
That's a good high-level list, although the comparisons don't always match up. For example, I'd say Traffic Manager is more like Route 53 than ELB (which only works within a region). If you're after something a bit more in-depth (but covering less services) then I wrote a three part series last year. It may be a little out-of-date, but most of it still applies. Azure now supports MySQL, for example. 1: 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... 2: 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... 3: https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-confusion-part-3/ https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-c... Edit: Should that "puts da" be on that page?

inopinatus 10y ago

I'd say if you haven't had a lot of exposure to AWS, this list is likely to give you a misleading impression in many cases; many items are either factually or taxonomically wrong, or grossly oversimplified to force them into a particular category, or confuse the underlying implementation (or even unverified assumptions about the underlying implementation) for the service offering. There are also some surprising omissions, like ELB/ALB or KMS, and some impossible and even self-defeating suggestions, like using someone else's trademark (again, with questionable validaty). It's especially misleading if, as you say, you want to understand differences between AWS and Azure services, because that sometimes comes down to nuances. So I recommend treating it as humorous parody, not documentation. It is a little bit amusing if you're already in the know. Source: I'm ex-AWS.