This is really well done! I might tweak the Lambda one a little to mention what they run in response to or to even drop in the serverless buzzword.
AWS services explained in one line each
21–30 of 355 posts
Re: AWS services explained in one line each
#22Reminded me of these similar threads I read a while earlier: Azure: https://web.archive.org/web/20190321175020/https://www.exped... https://news.ycombinator.com/item?id=13442597 AWS: https://expeditedsecurity.com/aws-in-plain-english/ https://news.ycombinator.com/item?id=10202286
I figured somebody has done this before. I purposely did not look for it to keep my findings unbiased. It was fun clicking on random services and tweak with it until figuring out what it was for and how to use it (and actually see some results)
Re: AWS services explained in one line each
#23Earlier quoted context omitted.
I'd prefer to see this integrated into the AWS UX. For an external crowd-sourced version, I'd like to see something like this with a column for maturity, and whether it actually works. The classic AWS services are rock-solid, and perfectly sufficient to build a business on. Many of the newer ones are.... much less so. A green checkmark, yellow question mark, and red land mine icon would go a long way towards letting…
> integrated into the AWS UX Sure, it should be right in the headline of the service's "about" page. The fact that people need this at all is UX problem. If people are reading your "about" page and nobody understands what the hell your thing does, maybe your marketing, faux-tech, word salad is pointless.
>The fact that people need this at all is UX problem.
Is it a UX problem or is it intentional deep branding to further promote vendor lock-in? This is one reason I've been opposed to AWS since the early phases--I don't want to learn all of their stupid branded vendor-specific nomenclature.
Re: AWS services explained in one line each
#24Route 53 is too generalized
Re: AWS services explained in one line each
#25"Large & scalable non-relational database (but not really a NoSQL system)"
triggered
Re: AWS services explained in one line each
#26Consider that your typical enterprise software project will use quite a lot of these, and that you pay for them all separately, and sometimes pay twice for them (e.g. S3 you pay for storage and for outbound bandwidth).
It's quite a tour de force how Amazon have taken "separation of concerns", applied it to web services and used it to create complex and difficult to understand or predict pricing to print money. Bravo.
Re: AWS services explained in one line each
#27There's an open guide[1] that's pretty useful. Amazon also publishes (at least some) documentation on Github[2].
Re: AWS services explained in one line each
#28Consider that your typical enterprise software project will use quite a lot of these, and that you pay for them all separately, and sometimes pay twice for them (e.g. S3 you pay for storage and for outbound bandwidth). It's quite a tour de force how Amazon have taken "separation of concerns", applied it to web services and used it to create complex and difficult to understand or predict pricing to print money. Bravo.
For those not in "the biz", the idea of a WordPress site isn't too far-fetched.
One can mention that there is a LAMP stack behind WordPress without knocking too many unconscious.
Amazon's genius has been to sell the various permutations of the acronym "LAMP" as services.
Re: AWS services explained in one line each
#29AWS sounds like a good idea until you start calculating the cost of the setup with any kind of clustering and moderate data traffic.
Re: AWS services explained in one line each
#30I see that AWS IoT Greengrass is missing. https://aws.amazon.com/greengrass/ I may be wrong but from what I understood, it's more or less a way to manage AWS Lambda functions (cgi-bin scripts), Docker, and a MQTT client connected to AWS on your GNU/Linux devices (raspbian on a raspberry pi for example, or a x86 pc). However you still need Ansible or similar to manage the device so the actual value is kinda low becaus…
The whole lot of IOT services are pretty confusing. Mostly because I have no experience with IOT/MQTT in general and it took a few days to actually figure out how to create and connect things (emulated). I actually bought some IOT devices (lamps, sensors) to try it out, but this turned out to be vendor-locked without any possibilities for MQTT. I reckon somebody with more experience in the IOT field could provide mor…
Do your sensors/lamps use Zigbee? I use the excellent Zigbee2MQTT library and a DIY Zigbee sniffer. Now I can use most vendor-locked IOT-devices (Hue, Ikea Tradfri, cheapo Chinese stuff) in my Home Assistant without the need of a separate bridge.
Check if your devices are supported here: https://www.zigbee2mqtt.io/information/supported_devices.htm...