Amazon literally should pay you for this. I will be signing up for some additional services now that I know what they are. Thank you.
Also, love the light application of humor.
Amazon Web Services in Plain English
201–210 of 237 posts
Re: Amazon Web Services in Plain English
#202Earlier quoted context omitted.
Running a business on AWS is like taking Uber to work every day. At some point it makes sense to just buy the car.
> Running a business on AWS is like taking Uber to work every day. At some point it makes sense to just buy the car. To make the analogy accurate: Running a business on AWS is like taking Uber to work every day. At some point it makes sense to just buy the car, hire a driver, find a good mechanic, lease a parking spot, purchase automobile insurance, remember to buy gas, deal with speeding tickets, schedule regular ma…
> At some point it makes sense, but it is way, way down the road for most startups.
Thing is, unlike the "get driven to work" analogy, programmers/etc are in the same problem domain as the required services.
It would be like a mechanic taking an Uber to his garage every day because he couldn't be bothered personally owning a car. What?!
"Car leases" (rented dedicated servers [possibly even managed]) are a happy medium everyone should consider.
Re: Amazon Web Services in Plain English
#203i have never used S3 to do anything with FTP. FTP is terribly insecure... S3 is not. you're an idiot. stopped reading.
Re: Amazon Web Services in Plain English
#204SES is great for newsletters. We use it for that all the time. Not sure why this article concludes it's only a good idea for transactional email.
I agree - I built support for Amazon SES into Dada Mail[0], and allows my users to take a quantum leap from running Dada Mail and using their (not so good) shared host mail servers, to sending via SES. Deliverability and speed goes through the roof and the service is incredibly cheap AND you're in complete control over your own data, as your hosting the app yourself.
Re: Amazon Web Services in Plain English
#205SES is great for newsletters. We use it for that all the time. Not sure why this article concludes it's only a good idea for transactional email.
I agree - I built support for Amazon SES into Dada Mail[0], and allows my users to take a quantum leap from running Dada Mail and using their (not so good) shared host mail servers, to sending via SES. Deliverability and speed goes through the roof and the service is incredibly cheap AND you're in complete control over your own data, as your hosting the app yourself. [0] http://dadamailproject.com/
Also, original author - are you using confirmation in your email subscriptions? I signed up for your mailing list, and didn't get a confirmation email - it just says I'm subscribed. That's usually not a good idea, as I can put just anyone's email address in there. FYI.
Re: Amazon Web Services in Plain English
#206Hey 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 think you misspelled "ingest" ;)
Re: Amazon Web Services in Plain English
#207Earlier quoted context omitted.
File store? I agree that "object" makes no sense when applied to S3. It's not like you can store an "account" object and call a method to get back the current balance, with accrued interest for the time since last deposit added in. Or even store an image and call a method to get back a black-and-white version. Etc. IMNHO "File server" implies it exports an actual file-system, and would also be wrong. In that light, I…
> I agree that "object" makes no sense when applied to S3. It's not like you can store an "account" object and call a method to get back the current balance, with accrued interest for the time since last deposit added in. Or even store an image and call a method to get back a black-and-white version. Etc. Well, yes, they aren't OOP objects. But as you say, "files" isn't great either. But it was a theoretical alternat…
> But FTP isn't even close. You could not find/replace "Object" with "FTP" without making those docs completely incoherent.
That's the wrong comparison though. You could replace all instances of "S3" with "an FTP server" and it would make a ton of sense, minus the reliability claims.
Re: Amazon Web Services in Plain English
#208Earlier quoted context omitted.
Using FTP as shorthand is better than "Object Store", which sounds like the marketing BS this is designed to avoid.
How is "Object Store" marketing bs? What is the proper term for an S3 object? It's not file , because file is a term that comes from the context of a filesystem, which is what S3 is not. Read the S3 docs: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingObjects.... That is the technical term they've chosen to describe the key, its value, and all its associated metadata. As far as terms go, it's rather straightforw…
So when I download a file from a website, I'm not actually downloading the file? Since it doesn't become a file until it gets flushed to disk by my browser? So what is the name for the sequence of bytes that are actually downloaded?
Re: Amazon Web Services in Plain English
#209Hey 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.
Would love to hear by what % your revenue increased today (or in the next month or so from lag time)
We don't actually have an AWS product released yet. This article was part of our becoming more familiar with all the different aspects of AWS (like a lot of other developers we're long time users of S3 and EC2 and PAAS services built on top of parts of AWS).
Re: Amazon Web Services in Plain English
#210Earlier quoted context omitted.
> Running a business on AWS is like taking Uber to work every day. At some point it makes sense to just buy the car. To make the analogy accurate: Running a business on AWS is like taking Uber to work every day. At some point it makes sense to just buy the car, hire a driver, find a good mechanic, lease a parking spot, purchase automobile insurance, remember to buy gas, deal with speeding tickets, schedule regular ma…
> At some point it makes sense, but it is way, way down the road for most startups. Thing is, unlike the "get driven to work" analogy, programmers/etc are in the same problem domain as the required services. It would be like a mechanic taking an Uber to his garage every day because he couldn't be bothered personally owning a car. What?! "Car leases" (rented dedicated servers [possibly even managed]) are a happy mediu…
> Thing is, unlike the "get driven to work" analogy, programmers/etc are in the same problem domain as the required services.
But programmers should be focusing on delivering their startup's unique technology or service, not building and maintaining commodity infrastructure.