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

221–230 of 355 posts

Re: AWS services explained in one line each

#221

Post by NikolaeVarius »

llbeansandrice wrote: post #199
pas wrote: post #135

Earlier quoted context omitted.

Why? They could have simply named them with AWS Serverless, or AWS Compute, or whatever. Using these brand names might make it easier to evolve them later, or they really wanted nice sounding names because eventually you'd have to write out long phrases with the AWS prefix, and that's probably harder to market.

> AWS Serverless Which serverless? ECS Fargate? Lambda? Step Functions? There are tons of AWS services which are technically "serverless". Even S3 obfuscates away the server. https://aws.amazon.com/serverless/

Los Balancer = HaProxy Serverless

Re: AWS services explained in one line each

#222

Post by kube-system »

jaytaph wrote: post #103
wartijn_ wrote: post #79

Earlier quoted context omitted.

Isn't VPC a wel known term? I guess the author just included that definition to make the list complete.

I've updated it to "virtual private network" instead.

You're never going to please everyone, but I think that might be confused with a VPN.

Amazon simply describes it as a "virtual network"

Re: AWS services explained in one line each

#223

Post by mixedCase »

scarface74 wrote: post #214
mixedCase wrote: post #211

Earlier quoted context omitted.

No longer at that gig, but in order: Kubernetes applications using Kubernetes abstractions, S3 API abstracted away at the library level, RBAC done through Kubernetes (which includes IAM integration), we did use SQS and SNS but those were easy to replace given our abstractions. No security audits (third party ones at least, we did have scripts and checklists for deps and GDPR compliance). No hybrid networks, we either…

Everything seems easy until you actually get your project management organization involved, and your IT staff, your QA, your business analysts, your compliance department, start allocating cost for your staff etc....

Well that's because you're locked-in :). If you're already locked in, you're screwed and have to work your way out or live with it and the consequences that come either now or later.

If I get to make the call and I care one bit about the business beyond next quarter, I would always have a clear way out to heavily reduce risks to a situation that we have seen play out many times before with the Oracles and IBMs of the world.

Re: AWS services explained in one line each

#224

Post by chapium »

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?

Re: AWS services explained in one line each

#226

Post by scarface74 »

mixedCase wrote: post #223
scarface74 wrote: post #214

Earlier quoted context omitted.

Everything seems easy until you actually get your project management organization involved, and your IT staff, your QA, your business analysts, your compliance department, start allocating cost for your staff etc....

Well that's because you're locked-in :). If you're already locked in, you're screwed and have to work your way out or live with it and the consequences that come either now or later. If I get to make the call and I care one bit about the business beyond next quarter, I would always have a clear way out to heavily reduce risks to a situation that we have seen play out many times before with the Oracles and IBMs of the…

The same happened when moving from a colo to AWS...

You can’t imagine the red tape moving from Workday and their homespun EMR (Healthcare) written 20 years ago using Powerbuilder.

Re: AWS services explained in one line each

#227

Post by qchris »

doorstar wrote: post #189
FridgeSeal wrote: post #181

Earlier quoted context omitted.

Dealing with Azure causes me physical pain. AWS you can poke around and figure it out, Azure is a Kafkaesque nightmare of infinitely confusing UI/UX, a permission system that is like trying to hit a moving target in a dark room, being moved by someone that hates you, doing anything seems needlessly complex, and trying to replicate/test anything locally is horrible (looking at you Azure functions).

My sibling... I'm trapped in this mess because the nature of our Client is that they'd consider anything besides Azure as a slap in the face, but it's been absolutely the most miserable task I've taken on in years. As a bonus I'm getting side-eyed by teammates who have a naive faith in The Cloud and can't comprehend why this is taking so long and why I can't just give them a cost estimate.

As an aside, unless I'm reading this very wrong, this is the first time I've seen the use of "my sibling" as a gender-neutral replacement of "my brother/sister" to express empathy. I'm delighted by it.

Re: AWS services explained in one line each

#228

Post by skrebbel »

bt1a wrote: post #217
skrebbel wrote: post #208

Earlier quoted context omitted.

That's not openly joking, it's sales. If you feel like you're way overpaying for AWS, you're much likelier to look out for alternatives. So if they help their biggest accounts save some money, it'll net them way more in the long run.

Right - it gives the illusion that you're 'getting an amazing deal and wow these people are great' when it reality you're probably getting gouged without the consulting and have to opt in for fair prices.

Yep. To be frank I think that spinning it as a joke and not an honest retention tactic almost feels like lying.

Re: AWS services explained in one line each

#229

Post by topkeks »

traeregan wrote: post #168

Here's the Google Cloud equivalent: https://github.com/gregsramblings/google-cloud-4-words

That is an excellent list. There's also a guide that compares Google Cloud with AWS and highlights the similarities and differences between the two. https://cloud.google.com/docs/compare/aws

Re: AWS services explained in one line each

#230

Post by rantwasp »

teej wrote: post #205
rantwasp wrote: post #195

Earlier quoted context omitted.

nowhere close to 100x. actually it’s worse than the aws names across the board. the names have a logic to them but I agree it’s intimidating to learn hundreds of things at the same time - so you don’t. you learn the bits and pieces you need. for example: EC2 actually comes from Elastic Cloud Compute. You have Compute in the Cloud which also happens to be elastic. S3 is Simple Storage Service. It’s a Service for Stori…

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.

Post reply on HN