Earlier quoted context omitted.
Seems to work for Reddit, Zynga, Dropbox and Netflix.
Probably avoid using Reddit as a performance metric, they like their 500 errors.
Some of that could be Cloudflare
Amazon Web Services in Plain English
61–70 of 237 posts
Re: Amazon Web Services in Plain English
#62Would be nice if the services' header linked to the official AWS product page.
Re: Amazon Web Services in Plain English
#63Great post some of this stuff has been is a mystery to me. Probably one of the reason I use Digital Ocean. For my personal needs, a simple VM will do and they even let me attach my Keys before instance creation.
Re: Amazon Web Services in Plain English
#64Awesome. I wish there was a column to tell you Google's version of the same service, where applicable.
Re: Amazon Web Services in Plain English
#65Has AWS deprecated any of the services they've launched? If not, isn't that almost unprecedented in the worlds of either enterprise software and SaaS?
They used to have SimpleDB which had been mostly deprecated in favor of DynamoDB.
Re: Amazon Web Services in Plain English
#66Whoa 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.
Re: Amazon Web Services in Plain English
#67Hey 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.
Re: Amazon Web Services in Plain English
#68"It's like: Stacking cash on the sidewalk and lighting it on fire" Is an accurate description of a large number of products that I have been forced to use after various CTOs have played golf with a vendors sales team.
It is not an accurate description, however, of the economics or value proposition of Direct Connect. When we're moving TB to an off-cloud location it's almost a no-brainer. Similar when latency sensitive. The highest barrier, quelle surprise, is dealing with interconnect telcos.
Yeah, and at certain data centers it is as simple as ordering a cross connect. There are many AWS services and each have many use cases where the customer is getting an excellent value. Unfortunately, just like deciphering all of the names is very difficult as OP demonstrated so well, understanding the use cases where you can get a good value as a customer is also esoteric and poorly documented. While AWS has pretty good docs in general for each service. Most of the naive implementations presented in tutorials and docs would not be a valuable reason for a customer to use the service. I wonder if documenting this type of stuff better would help them grow the business or if they just don't care and they want to just rip off as many faces as possible. I guess in traditional enterprise software, this is always the role of the consultants / partners rather than the role of the vendor. The vendor sales guy always just wants you to take the license that puts the most money in his pocket and it is up to those partners and consultants to explain to you how to optimize your usage and licensing.
Re: Amazon Web Services in Plain English
#69Hey 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.
This is great... well done. Any chance you could side-by-side it with Azure & Google Cloud's offerings? That would be MASSIVELY useful!
Re: Amazon Web Services in Plain English
#70When 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 to N servers with so much memory. How do you make that jump to thinking the other way?