Amazon Web Services in Plain English

Post by pravka » Fri, Sep 11, 2015, 6:40 PM UTC

Cthulhu_ wrote: post #76

unoti wrote: post #70

When you're building a new app based around a handful of these services, how do you have any idea what it will cost to host your business on a startup? In the past I've avoided using these, and just used VPS servers doing my own thing, because it's really hard for me to, for example, guess how many database queries I'll do or messages I'll send between app components. I feel much safer saying that I can limit myself…

I'd say run on Heroku, but IIRC they gave up on their free plan. You could run on Google App Engine though, IIRC they still offer a free service up until a certain number of requests or CPU usage or something in that direction. You could use those to determine how much your application actually uses the service. IIRC, Amazon also offers services for a fixed monthly price, you could look into that too.

Post by MichaelGG » Fri, Sep 11, 2015, 6:57 PM UTC

jonkiddy wrote: post #59

jlebar wrote: post #19

I have to say that I think "glacier" is an inspired name. It takes a negative -- slow data retrieval -- and turns it into a positive -- indestructible, huge, unstoppable.

I completely agree. It is a great name for the service. "There are two hard things in computer science: cache invalidation, naming things, and off-by-one errors." ~ Jeff Atwood

Post by Goladus » Fri, Sep 11, 2015, 7:23 PM UTC

WhitneyLand wrote: post #142

Goladus wrote: post #128

Earlier quoted context omitted.

The only real resemblance at all to FTP is that you use GET and PUT instead of filesystem commands. I mean, I guess if you really don't understand what FTP is and have no desire to understand how S3 is different from posix, then saying you have to use S3 like you use FTP kind of works. But it would be misleading to everyone else. > It's probably more redundant than FTP FTP is a transfer protocol , it says nothing abo…

Using FTP as shorthand is better than "Object Store", which sounds like the marketing BS this is designed to avoid.

Post by samstave » Fri, Sep 11, 2015, 7:32 PM UTC

michaelbuckbee wrote: post #82

dandare wrote: 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.

Post by samstave » Fri, Sep 11, 2015, 7:47 PM UTC

frankcaron wrote: post #75

michaelbuckbee wrote: post #67

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.

I'm kind of in love with you after writing this. Thank you for doing what so few product and service companies do: naming a product in a manner that makes it almost instantly-understandable as to what problem it solves.