Amazon Web Services in Plain English

Post by djm_ » Fri, Sep 11, 2015, 2:03 PM UTC

michaelbuckbee wrote: post #84

djm_ wrote: post #71

Earlier quoted context omitted.

Hi Michael! Great guide. SNS is not just for mobile app developers and should probably belong in the "Web Developer Services" section. It is a general messaging service and can deliver messages to SQS, AWS Lambda, email and arbitrary HTTP(S) endpoints. For example, we have some S3 buckets set up to send an SNS message to an SNS topic on new object creation, the topic then in turn notifies our subscribed HTTPS endpoin…

All good points, I think this is where the "plain english" starts to break down and you _have_ to really come to grips with exactly what the services are doing. I was trying to write this from the standpoint of describing what the services did to another developer in a really high level way.

Post by Anderkent » Fri, Sep 11, 2015, 2:03 PM UTC

jimbokun wrote: post #92

mattmanser wrote: post #90

Earlier quoted context omitted.

You've got a nasty shock coming then, you'll spend far more time scouring badly written documentation about something that is supposedly simple but just doesn't work and once you've got working you'll never, ever use again until you've forgotten everything and then you need to set it up again and you'll have to go through the whole soul destroying process again but the documentation you find is now out of date, why-g…

Now re-read your first paragraph in light of the second one. Sometimes, it really is easier to just implement something your self than go through the "soul destroying process" of figuring out how to correctly set up and configure a library, framework, or piece of open source infrastructure. Not an algorithm, but it can be a lot easier to write your own SQL, for example, than setting up and configuring Spring and Hibe…

Post by JangoSteve » Fri, Sep 11, 2015, 2:09 PM UTC

michaelbuckbee wrote: post #84

djm_ wrote: post #71

Earlier quoted context omitted.

Hi Michael! Great guide. SNS is not just for mobile app developers and should probably belong in the "Web Developer Services" section. It is a general messaging service and can deliver messages to SQS, AWS Lambda, email and arbitrary HTTP(S) endpoints. For example, we have some S3 buckets set up to send an SNS message to an SNS topic on new object creation, the topic then in turn notifies our subscribed HTTPS endpoin…

All good points, I think this is where the "plain english" starts to break down and you _have_ to really come to grips with exactly what the services are doing. I was trying to write this from the standpoint of describing what the services did to another developer in a really high level way.

Post by matthewrhoden1 » Fri, Sep 11, 2015, 2:10 PM UTC

Post by [deleted] » Fri, Sep 11, 2015, 2:14 PM UTC

mattmanser wrote: post #90

kevindeasis wrote: post #55

It took me forever to understand what each services aim to do. Like I could have literally been a better programmer by spending all the time learning algorithms instead of figuring out what each of the aws services do. I wish I've had access to this post before. I like the services they offer, I just really hate the names they gave it. Funny enough, Jeff Bezos said in an interview that names of a product is important…

You've got a nasty shock coming then, you'll spend far more time scouring badly written documentation about something that is supposedly simple but just doesn't work and once you've got working you'll never, ever use again until you've forgotten everything and then you need to set it up again and you'll have to go through the whole soul destroying process again but the documentation you find is now out of date, why-g…