It'd be nice to include "year introduced" data as well. My AWS knowledge peaked sometime in 2012 after DynamoDB came out. I know a bit about newer things (like Lambda) but there's a lot of catching up to do...
AWS services explained in one line each
241–250 of 355 posts
Re: AWS services explained in one line each
#242Earlier 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.
We were in no way one of "their biggest accounts". We were a couple guys in a cramped office over a mattress store, with a production service so small we could have run it from my old laptop. I guarantee it cost them at least 10x more to send those consultants over to us than we spent on AWS in a year, even before the optimizations they pointed out.
But here you are, letting us know that they have been wonderful sending consultants.
It's part PR, part long term customer acquisition
Re: AWS services explained in one line each
#243The title should have been a computer science introduction to marketing terms
Re: AWS services explained in one line each
#244Earlier quoted context omitted.
I usually try to cut them some slack. I mean, they're operating this stuff at Internet scale and have never (AFAIK) raised prices. They've basically got two options: * Price things in an intricate way sufficiently specific to actual costs of providing the service for many use cases * Price things more generally in a way that more or less probably results in about the same revenue The problem with option #2 is that it…
Doesn't that kind of problem get easier at large scale? It's like any time you have a limited resource to share out. e.g. if an ISP has 150mbits of connectivity, it would be difficult to provide a '100mbit' service to two homes - one busy user will clearly hit the other. But if you have 1500mbits to share out to 20 homes, the service will seem much better. As you scale up, it becomes easier to provision less per cust…
One case that comes to mind is when they started charging for S3 API requests because people were using it as a free KV store.
Re: AWS services explained in one line each
#245Earlier quoted context omitted.
I usually try to cut them some slack. I mean, they're operating this stuff at Internet scale and have never (AFAIK) raised prices. They've basically got two options: * Price things in an intricate way sufficiently specific to actual costs of providing the service for many use cases * Price things more generally in a way that more or less probably results in about the same revenue The problem with option #2 is that it…
>I mean, they're operating this stuff at Internet scale and have never (AFAIK) raised prices Prices should have gone down because they've continued to scale up and go into custom cooling/hardware/backbones/etc. You're basically saying that you're cutting them slack because their margins have gotten much larger and they haven't decided to raise prices to make them even bigger.
Early customers were taking a bet on a new thing. Later customers are buying into the stability of the brand.
Re: AWS services explained in one line each
#246This 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...
Re: AWS services explained in one line each
#247You 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...
Re: AWS services explained in one line each
#248Earlier 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.
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?
Re: AWS services explained in one line each
#249Earlier quoted context omitted.
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.
I mean it's a retention tactic at the company scale but for the individual consultant they're genuinely trying to help you out. I frequent a local family-owned Italian restaurant/pizza place and my usual order jalapeños, banana peppers, and roasted garlic so I do a build you own. Totally fine, happy to pay the price. But one day I come in and the woman working the take-out counter sees my order before it goes in and…
> So now I'm the vegetarian that always gets a meat lovers and she makes the joke every time I come in.
I've seen that before, and I've also seen the opposite where people buy the veggie pizza and then add a meat or two on top to get a cheaper supreme pizza.
Re: AWS services explained in one line each
#250This 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...
Maybe allows stream reading a database?