News for hackers. Stuff that matters.
Re:Why I recommended ECS instead of Kubernetes to my latest ... by HatchedLake721 on Thursday June 08, 2023 @01:41PM (#36245722)
That's a very weird suggestion.

What SQS has to do with EC2?

One is a queuing service, the other one is a VM.

So instead of using SQS that has $0 cost when there are no customers, you suggest I install, configure and run RabbitMQ on an EC2, to save $0 when there are no customers?

Or save $1 when I have 100 customers? SQS is dirt cheap.

The point of SQS or any other usage-based AWS _developer_ service compared to DIY is that you can be up and running in minutes at a cost of less than a dollar.

I'll pick SQS any time of the day to increase my developer velocity and have queueing functionality in 15 minutes to focus on building value rather than waste my life installing, configuring and running anything on EC2.

Re:Why I recommended ECS instead of Kubernetes to my latest ... by djbusby on Thursday June 08, 2023 @01:52PM (#36245875)
The question is: what are queueing for zero customers?
Re:Why I recommended ECS instead of Kubernetes to my latest ... by sokoloff on Thursday June 08, 2023 @01:55PM (#36245924)
You might as well ask “why use a database when you have no customers?”
Re:Why I recommended ECS instead of Kubernetes to my latest ... by HatchedLake721 on Thursday June 08, 2023 @02:47PM (#36246695)
If I'm building a marketing automation app that allows customers to do a newsletter blast, I'll put those 1000 email recipients into a queue and run through it at a required pace with a retry interval if anything fails.

What do you suggest I do before I get my first customer?

- Blast 1000 emails in one go and pray upstream accepts it?

- Push these to a database and keep checking it with a CRON?

- Run RabbitMQ on an EC2 and push 1000 messages there?

- Implement SQS in "15 minutes" at $0 cost?

Re:Why I recommended ECS instead of Kubernetes to my latest ... by Nextgrid on Thursday June 08, 2023 @03:33PM (#36247478)
The AMQP protocol alone and its various, good client libraries (compared to terrible AWS SDK which is a very thin abstraction over just sending/parsing raw JSON off the wire) is by itself enough to justify RabbitMQ.

> when I need queueing functionality to increase my developer velocity so I can focus on building value rather than wasting my life installing, configuring and running anything on EC2.

SQS still requires configuration, which means you either need to use the (terrible) AWS console UI or spin up a whole Terraform/CloudFormation/CDK/etc stack, not to mention that merely connecting to it requires correctly setting up AWS IAM (so you don't use a key that gives access to your entire AWS account). Vim'ing the RabbitMQ config file in contrast doesn't seem so bad, and even just using a static hardcoded password means the worst an attacker can do is take down your queue instead of taking over your entire cloud infra.