On the other hand, it doesn't make much sense to keep reinventing the same things that AWS has already packaged into convenient and reusable little Lego blocks. I guess the excitement of inventing new stuff needs to be related to new technologies not yet commoditized.
Dunno what everyone else thinks but these AWS Lego blocks are anything but convenient and reusable. Frankly they're oversold from my perspective as someone that came a little late into the "aws cloud" game.
My experience is "it depends". I had, for example, a good experience with AWS Fargate. It's not inexpensive, but it did what it said it would. It let me focus on packaging apps into containers, and caring less about making them elastic.
I had the opposite experience with Lambdas/Serverless. It made easy things very slightly easier, and hard things impossible.
My experience with AWS services is that the ones that merely provide low-level building blocks (such as EC2) or host existing open-source software such as Postgres, Redis, etc are good, but the proprietary AWS-specific ones are bad because they not only lock you into AWS but make it more complex to develop against as you can't always run it locally (there is LocalStack, but it's a simplistic reimplementation that doesn't always reflect the real thing especially when it comes to edge-cases), can't inspect it or debug it easily (it is a black box) and costs money even during development.
AWS-hosted Redis? Sure! AWS-hosted RabbitMQ? Of course! AWS SQS? No thanks - it wouldn't give me anything useful that RabbitMQ can't do, however it will lock me into forever having to pay AWS, deal with their terrible console (or stacks of YAML files) to control the thing and expose me to potential edge-cases I will have no way to debug or replicate locally.
> AWS SQS? No thanks - it wouldn't give me anything useful that RabbitMQ can't do
Allow other AWS services to send it events (SNS, lambda, etc etc)? Reliably handle millions of messages per second without managing anything yourself? Transparent KMS encryption? Fine-grained role based permissions via IAM without any hard-coded credentials?
Do you have examples of which AWS "Lego blocks" are not convenient and reusable?
For me, the convenient "Lego blocks" that I use a lot include CloudFront (web server/CDN), S3 (file/web server), ACM (certificate manager), DynamoDB (NoSQL database), Firehose (message batching and storage), SQS/SNS (queuing and publish/subscribe), Step Functions (low-code business logic), Lambda (event-driven custom code execution) and API Gateway (REST API / WebSocket service). It is very rare to need to run any self-managed servers any more with all these services available.
Unfortunately I think the issue not AWS here. You say you lost interest when it became a frustrating exercise, I read it as you lost interest once you realized setting up a cloud environment is not trivial.
i dont know.
i.moved a lot of services and functionality from aws to self hosted and open source and my monthly bill reduced to 100 bucks.
from multiple k's
You must have run some really heavy stuff on AWS for it to cost that much, if you are taking advantage of serverless services (not just running idle containers or servers that cost by the hour).
