Whenever this list comes up there's generally a group of people that dislike it for trying to be at least mildly humorous (The whole concept for it started with my developer friends and I joking about some of the names and how opaque they were, so not sure what I'm supposed to do).
There were a couple substantial edits I made to it where a few funny lines were cut in favor of better explaining what/how something worked.
I also started fleshing out some of the services with slightly more in-depth articles about them (such as this discussion of AWS Buckets where I compare Amazon's CTO to a character from 28 Days Later - https://www.expeditedssl.com/aws-s3-buckets-of-objects
I've sometimes thought that I should try and make it into an ebook or something, but there's always been something more interesting to work on. Thanks to everyone who has enjoyed it, shared it with their friends and hopefully took their first steps to messing around with AWS.
When did you first write it? I didn't notice a date on the page. That might be a useful addition to the page.
I hope you do spend more time to update this with the newer releases from Amazon. I find that in the console now, it has got to the stage that I cannot easily find the services I need in their drop down. (Yup, I know they recently redesigned the drop down to showcase thing a lot more clearly, but there is still SO much on there that I resort to the search function now, because I know the name of the service I am after, but it is actually quicker for me to type the name than to hunt for it in the list!).
I don't feel like litigating that through PRs.
not sure what the difference is. all local files on your HD also abide by these same rules. if you want to use any file you have to open it which ends up as a block of bits in memory
The problem with these intrusive tactics is literally the next thread on HN right now: https://news.ycombinator.com/item?id=13439828
I like it :-)
ElastiCache is not "AWS Memcache" (it supports other caching services), and S3 is not "unlimited FTP" (it does not support FTP protocols).
Amazon RDS is not Amazon SQL (that's what they should have called Aurora), but Amazon Hosted RDBMS.
I'd also argue that EC2 isn't always a virtual server (once you get to a certain size, you're on your own iron), and that SES can be used for more than transactional emails.
But, that aside, not a bad job.
You are right that this simplification is not technically correct anymore.
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.
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.
Edit: Should that "puts da" be on that page?
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"
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.
Simple Storage Service = twenty-two characters and six syllables
Given how much it's used in discussions around online storage, the former is definitely preferable. The fully spelled-out name is really only useful to ultra-newbies, and not to anyone with even a hint of experience in the product. Not much gained there.
Or what is SAP?
>You could use it to send a newsletter if you wrote all the code, but that's not a great idea.
You actually can use a self hosted solution like Sendy to send marketing emails & newsletters via SES & only pay for the emails you send using SES
(In fact, you don't HAVE to tie services together that you don't need. If you have a separate RDS instance already that you want to use, you can tell your Elastic Beanstalk project to use that instead of creating a new one).
I use Elastic Beanstalk for all my projects now, and like how I can deploy from Git repositories so easily with a single command. Granted the interface isn't as easy as Heroku, but you have the bonus of added configurability in your apps.
The one service name that's self declared.
Source: Acronyms seriously suck https://twitter.com/davejohnson/status/602951117413216256
Although to be honest, I did have to look up "updoot" in the Urban Dictionary :), so to be fair I should say unnecessary use of urban slang can also hamper communication.