Live data from Hacker News

Amazon Web Services in Plain English

expeditedssl.com

101–110 of 237 posts

Re: Amazon Web Services in Plain English

#101
post #28

Earlier quoted context omitted.

I understand where you are coming from. I'm just 'starting out' with a lot of this, despite a few years building/hosting websites, and these sort of services are the things I'm starting to look at. I'm completely disinterested in Amazon's offerings chiefly because they're so obtuse. Why should I expend so much cognitive load just figuring out what each service is and what it could do for me? It's undoubtedly possible…

Because when you figure out how to use them, you can save a tremendous amount of time and energy, and build sophisticated systems with simple code and little effort. When you have the need in a certain area, a lot of them will feel like "Wow, I didn't know that someone could automate this for me with so little effort compared to doing it myself". Most of it becomes increasingly valuable as you operate larger systems…

"When you have the need in a certain area..."

I find this is the key to understanding a service, library or technology. It is very difficult for me to wrap me head around something if I haven't yet encountered the problem it solves.

For example, I'm sure Docker is awesome, but I don't really understand it yet because I haven't yet felt the pain Docker takes away. So I enjoy following new technologies, but when I don't really see the point I just assume I haven't experienced the pain the new technology takes away.

Re: Amazon Web Services in Plain English

#102
Why do people like to describe services in a complex way? Maybe to seems a more complex product than it really is, or too look like "specialists" speaking about stuff.

This is very common for small companies without marketing experience, but this happening in companies like Amazon and Microsoft (Azure), I can't understand.

Re: Amazon Web Services in Plain English

#104
post #66

Whoa errors! * S3 is not FTP. It's more like static web hosting and storage. * VPC is not a "colocated rack" as it doesn't offer physical placement of hardware. Amazon VLAN would be a better name. It's just private network address space.

FTP is a good analogy. A lot of people are familiar with FTP, and given a good s3 client, it appears the same.

Re: Amazon Web Services in Plain English

#105

Hey HN, I wrote this, thanks for all the feedback. In particular if I've mischaracterized the functionality of a service or you see something that's really off please email me at mike@expeditedssl.com or just tell me here and I'll fix it.

Cognito is probably more like "oauth and backends for your apps"

About Cognito, now I can understand what they are trying to mean.

Re: Amazon Web Services in Plain English

#106
post #78

Earlier quoted context omitted.

Well done, as a front end developer I find this tremendously useful. Could you go even deeper and describe various components of some of the services? What is a bucket and what is an instance? etc. Thanks

The plan is to go back through and start doing a similar "plain english" post about each of the services. If you're interested in getting those, please drop your email into the little newsletter form on the page.

I did :)

Re: Amazon Web Services in Plain English

#109

Why do people like to describe services in a complex way? Maybe to seems a more complex product than it really is, or too look like "specialists" speaking about stuff. This is very common for small companies without marketing experience, but this happening in companies like Amazon and Microsoft (Azure), I can't understand.

A lot of companies have code names for their products, the obvious reason being easy/fast day-to-day communication. IMO this loses its effectiveness when you have a large panel of products, and each one is provided by at least one other company.

TL;DR version: I use "Amazon's " instead of a code name.

Post reply on HN