4 ms·
Let me preface this by saying I use AWS only when clients insist on it. I think there are much better options that don't lock their customers in anywhere near t
by stephenr 11y ago
Let me preface this by saying I use AWS only when clients insist on it. I think there are much better options that don't lock their customers in anywhere near to the same level.
I think AWS has plenty of badly named services, but some of these suggestions are much worse worse (and have a huge American influence - that fascination with using brand/implementation names for a generic/standard item) than the current actual AWS name:
* Amazon Unlimited FTP Server - why? ftp is a transfer protocol. S3 is about storage. It should be called Amazon Storage Server. Which it basically is (Simple Storage Service - S3)
* Amazon Memcached - I don't used the service so I don't know if it's only binary compatible with memcached but if its a generic cache that has multiple interfaces (the page references redis too) then more generic term like cache (and elastic implies it can grow/expand) seems more logical.
* Amazon Beginning Cut Pro - wtf. Transcoding is literally the process of converting a file from one type of encoding to another. That seems to be what this does. Final Cut Pro is not a mere format converter, it's a non-linear editor.
* Device Farm - I'll only concede that maybe this should reference mobile devices, but the name seems pretty clear and concise.
* CodeCommit - how is "code commit" less clear than "github". By this logic, Apple's email client should be called "Apple Outlook" because Outlook was a well known email client on the market.
* EC2 Container Service - the reference to EC2 means its slightly non-obvious, but Amazon Container Service would be much better than something referencing Docker. Docker !== Containers.
* WorkDocs, WorkMail - seriously, you're just replacing "Work" with "Company" here.
* Storage Gateway - what are you trying to be obtuse? From your very description, this sounds like exactly what the name describes - a local gateway to a storage service.
* Elastic Map Reduce - the compute/processing part of Hadoop is Map/Reduce. How is "Hadooper" more clear than the current one?
* Machine Learning - you're just being facetious now, right?
* OpsWorks - again, why does their name have to reflect a single specific implementation of a fairly well understood term(s) - Operations, DevOps, etc??
edit: typos
- pvg 11y agoYep, a lot of it is "plain English" for the values of "plain English" that include "entirely inaccurate" and "explained in terms of other, just as obtusely named services you may or may not be familiar with". The idea, though, is great - provide some overview of Amazon's zillions of services that doesn't read like it's been generated by a markovbot. Perhaps the authors will improve the implementation.
- martiuk 11y agoWhat would you suggest as an alternative to AWS?
- Handwash 11y agoAWS is quite okay, I think, and useful. They even named their free training day as AWSome Day.
- stephenr 11y agoThat's like me asking you "what car do you suggest?" without telling you what I want to use it for, how big my family is, or where I live. I have no idea what your business does or what services you need, but there are plenty of other vendors from simple rented virtual machines up to full co-lo of customer owned hardware. The good ones will rely on good customer satisfaction rather than artificial vendor lock-in to remain profitable and competitive.
- madeofpalk 11y ago> * Amazon Memcached - I don't used the service so I don't know if it's only binary compatible with memcached but if its a generic cache that has multiple interfaces (the page references redis too) then more generic term like cache (and elastic implies it can grow/expand) seems more logical. Considering all AWS ElastiCache is is "hosted Redis", that one confused me the most. Out of all the AWS services, this is the least 'magic' and custom and easiest to come up with a name.
- kevinbowman 11y agoFrom memory, when you create an ElastiCache cluster, you have to choose whether it's memcache or redis. It's really just a very thin wrapper around them running EC2 instances in your VPC which are running either memcache or redis.
- benihana 11y agoSo, if I understand this right, you're getting really really worked up at a slightly tongue-in-cheek post that tries to explain AWS in a way that's relateable to a lot of programmers. And you're upset because the words used in this post, which is about explaining Amazon's services to people who are familiar with similar services, wouldn't be a wise choice for Amazon to actually use, since it's too familiar with their competition? That seems silly, and kind of missing the entire point of this submission. I haven't used any of Amazon's services, so having something to translate back to things I can understand was really helpful, and I feel like I have a much better idea of what Amazon offers.
- ins0 11y agoExactly what i was thinking about as i submited this. Don't read this article as a "They should rename the Services to..." and more like "This name would explain the Service in a simpler form". Thanks for reading my mind btw :)
- stephenr 11y agoSimpler or easier to recognise by some, but wrong is hardly better.
- stephenr 11y agoI wouldn't call this worked up or upset. The post claims to have "better hames" for the AWS services. Many of those names are much worse. Take the suggested "Amazon Beginning Cut Pro" which was their suggestion for "Elastic Transcoder". "Beginning Cut Pro" is clearly a reference to Apple's NLE, Final Cut Pro. I would suggest that there are literally zero people on the planet, who would use Amazon's video transcoding service (I imagine it's essentially a distributed ffmpeg queue.) to process video files before importing them into FCP. This isn't "tongue in cheek", this is "stupid and confusing as an attempt at a laugh". I mean, what if I suggested that a hosted Memcached service be called AppStart because it uses memory and Apps use memory. > having something to translate back to things I can understand was really helpful My issue is that several of the services covered, already have a MORE MEANINGFUL name. So if I had no idea what "Elastic Transcoder" did, but it was instead called "Amazon Beginning Cut Pro", I would then assume it's somehow a tool meant to work with FCP, and disregard it (I don't need a NLE, at most maybe I need something akin to ffmpeg, so I can transcode/scale video files between formats automatically and efficiently. If it's comedy, call it comedy, and make it actually funny. If it's meant to be a useful guide, make it fucking accurate, or it's worse than what AWS is doing already.
- gldalmaso 11y agoto add: * Amazon Unlimited FTP Server: you can't really interact with S3 using a ftp client
- err4nt 11y agoBoth of the most popular FTP clients for Mac and Windows that Ive seen developers using have fantastic support for S3! http://cyberduck.io http://cyberduck.io https://panic.com/transmit/ https://panic.com/transmit/
- stephenr 11y agoThat is completely irrelevant. They also support SFTP, and WebDAV too. Are these protocols all the same thing now, just because some apps support multiple protocols?
- err4nt 11y agoHow is it irrelevant? FTP is a protocol, but people use FTP in a variety of wrong but commonly understood meanings: FTP Server = Hard drive accessible via FTP, not the server on that machine running the protocol FTP Program = a file-management interface that uses FTP protocol to send commands HTTP is also a protocol, though 'web browsers' can browse other protocols, as well as offline files. Saying that an FTP Client that contains support for S3 is a misnomer is like arguing that accessing a file from your desktop using a 'web browser' isnt correct since you arent browsing any web. The list is aimed at demystifying the confusing terms for the layman, its not aimed at providing the most technically correct taxonomy (since that would also not communicate much to the layman) When I use my FTP client for SFTP am I using FTP or SSH?
- stephenr 11y agoWhat layman who can't understand ftp is a protocol and doesn't mean any kind of storage, needs to understand the meanings of aws services? If you're using sftp you're using ssh. It doesn't matter if your client also talks to ftp servers.