Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS services explained in one line each

adayinthelifeof.nl

Post reply on HN
Print view View original

271–280 of 355 posts

Re: AWS services explained in one line each

#271

Post by ggregoire »

joshfraser wrote: post #264

Sometimes it pays to be boring. One of the hardest parts of using AWS is learning all their silly names for everything. I know it's tempting to be cute when naming things, but everyone else wishes you would just be clear and descriptive. I've seen this play out at startups that love to name servers after galaxies or cartoon characters. It's all fine until your new employee onboarding guide comes with a massive memori…

Star Wars still seem to be the greatest source of inspiration for backend engineers when comes the time to find a name for a new microservice.

Re: AWS services explained in one line each

#273

Post by RedShift1 »

sixo wrote: post #246
RedShift1 wrote: post #136

This is a 100 x better than their website. I've actively walked away from Amazon products because I could barely make out what it really was and if I could use it for the application at hand. Many thanks!

"Redshift: Warehousing. Store lots of data that can be processed through streams." Not sure what that second sentence means...

The counterpart to stream processing is batch processing. With batch processing you run a job every hour or so and calculate a result, with stream processing you immediately calculate the result you want as the data is coming in.

Re: AWS services explained in one line each

#274

Post by abc_lisper »

elchief wrote: post #253

I made this list for my buddy a while back. It's meant to be more humorous than exactly correct Route 53 - Holy shit! It's NSD WAF - Holy shit! It's modsecurity SES - Holy shit! It's Postfix Inspector - Holy shit! It's OSSEC GuardDuty - Holy shit! It's Snort Data Pipeline - Holy shit! It's Cron and Bash Athena - Holy shit! It's Prestodb Glue - Holy shit! It's Hive Metastore and Spark OpsWorks - Holy shit! It's Chef V…

I am going to screenshot this for future reference

Re: AWS services explained in one line each

#275

Post by rantwasp »

core-e wrote: post #248
dodobirdlord wrote: post #216

Earlier quoted context omitted.

Cognito is an identity service, “incognito” means unknown, “cognito” means known. Polly is a joke about how parrots talk, the service does text-to-speech. Athena is a goddess of wisdom, the service is for querying databases. The name is frequently some sort of silly inside joke. Except Fargate, that name means nothing...

I noticed you conveniently left out Redshift. :) What about Snowball, Chime, Sumarian, and Route 53?

Here is the redshift: https://en.wikipedia.org/wiki/Redshift#Doppler_effect

It's a tongue in cheek about https://en.wikipedia.org/wiki/Redshift#Expansion_of_space and how

Re: AWS services explained in one line each

#276

Post by julianeon »

abc_lisper wrote: post #274
elchief wrote: post #253

I made this list for my buddy a while back. It's meant to be more humorous than exactly correct Route 53 - Holy shit! It's NSD WAF - Holy shit! It's modsecurity SES - Holy shit! It's Postfix Inspector - Holy shit! It's OSSEC GuardDuty - Holy shit! It's Snort Data Pipeline - Holy shit! It's Cron and Bash Athena - Holy shit! It's Prestodb Glue - Holy shit! It's Hive Metastore and Spark OpsWorks - Holy shit! It's Chef V…

I am going to screenshot this for future reference

I copy and pasted it for you, to save you a click.

Route 53 - Holy shit! It's NSD

WAF - Holy shit! It's modsecurity

SES - Holy shit! It's Postfix

Inspector - Holy shit! It's OSSEC

GuardDuty - Holy shit! It's Snort

Data Pipeline - Holy shit! It's Cron and Bash

Athena - Holy shit! It's Prestodb

Glue - Holy shit! It's Hive Metastore and Spark

OpsWorks - Holy shit! It's Chef

VPC - Holy shit! It's a VLAN

Snowball - Holy shit! It's a truck full of hard drives

CloudWatch - Holy shit! It's syslogd

Neptune - Holy shit! It's Neo4j

ElastiCache - Holy shit! It's Redis

DynamoDB - Holy shit! It's MongoDB

S3 Glacier - Holy shit! It's DVD backup

EFS - Holy shit! It's NFS

Elastic Block Store - Holy shit! It's a SAN

Elastic Beanstalk - Holy shit! It's Apache Tomcat

EMR - Holy shit! It's Apache Hadoop

Elastic Cloud Compute - Holy shit! It's a virtual machine

Kinesis - Holy shit! It's Apache Kafka

QuickSight - Holy shit! It's Tableau

Re: AWS services explained in one line each

#277

Post by kyawzazaw »

rantwasp wrote: post #230
teej wrote: post #205

Earlier quoted context omitted.

Cognito? Lightsail? Redshift? CodeStar? Athena? Polly? There are loads of AWS services that don’t follow any logic, they’re just distinct, easy to spell nouns.

go to: https://aws.amazon.com/products/ look up your service. each service has a 1 line description that captures what it does. eg Athena = query data in s3 using sql i don’t really get why people cannot be bothered to learn what a service does and want to pretend they get it from the name. you need to learn the ins and out of the service. the name is the least of your worries.

btw, How does AWS amplify fit into this?

Re: AWS services explained in one line each

#278

Post by Shorel »

exhaze wrote: post #90
coder543 wrote: post #72

Earlier quoted context omitted.

Isn’t that exactly what the person you replied to said? You’re showing what you’ve been charged for previously. That part works, at a certain level of detail. That doesn’t show what you are being charged for right now , nor does it help you predict what your total costs will be at the end of the month.

You bring up a good point - it would be a good idea for AWS to set some sensible max budget defaults for new accounts to prevent surprises. Since they don't, if you are literally so concerned with your current costs for this month, you can set a budget and alerts for whatever you want, so that you don't exceed some cost. Also, they show you your current cost for this month, up until the moment, as well as a daily bre…

I started using my new account yesterday.

I already got a surprise, because in one place it says t2.micro and t3.micro instances are free for twelve months.

But, if the instance runs Windows, or the zone is this or that, or something else I don't know, the only free tier instance is actually the t2.micro.

And then there's the Unlimited option, and CPU credits, where if your CPU use goes over 25% for some time, it will either: Be throttled so slow as to be useless, or, not being free and you still have to pay for each hour of use.

And that's just the beginning!

Re: AWS services explained in one line each

#279

Post by rantwasp »

chapium wrote: post #224
s_dev wrote: post #31

Similar to https://expeditedsecurity.com/aws-in-plain-english/ Why does AWS use such convoluted language? Is it because they're dominant and it adds friction to moving to another provider?

Why is lemon sugar flavored carbonated beverage called Mountain Dew? Shouldn't the soda companies use less convoluted language? Why is Confluent not just called Kafka+? Why isn't Kafka called LinkedIn distributed subscriber service?

and more importantly should diet mountain dew be called "lemon flavored carbonated beverage" or "lemon flavored sugar-free carbonated beverage"?

Re: AWS services explained in one line each

#280

Post by kyawzazaw »

vladoh wrote: post #247

You are missing one of the really amazing services: Snowmobile ( https://aws.amazon.com/snowmobile/ ). It is a real truck, that connects to your data center, copies up to 100 PB of data and drives back to one of the AWS data centers and dumps the data there...

And the companion Snowball (https://aws.amazon.com/snowball/)
Post reply on HN