3 ms·

I love it. This could be specific to the work I'm doing though. I'm doing workflows. For each workflow I have a lambda endpoint for the REST call and then run a

I love it. This could be specific to the work I'm doing though. I'm doing workflows. For each workflow I have a lambda endpoint for the REST call and then run a container that does all of it, we use a little SQS, Lambda, and Dynamo here and there, but it's just a process that runs for a while and dies. If I was doing this on a server I would have to use some kind of distributed task runner, scale-up servers etc.. With Faregate I don't even see the servers come up and down, it's just a magic box of runtimes. DO NOT USE AWS STEP, it's hot garbage.

namaria 3y ago
> DO NOT USE AWS STEP, it's hot garbage. This right here is the epitome of the cloud risk: the tarpits are hidden and keep moving. People swear by some golden happy path they found. They claim that means cloud is an amazing new frontier of platform engineering. Then they warn of the hidden tarpit they found and never seem to connect the dots.
- foofie 3y ago
  AWS Step Functions is hardly a hidden tarpit. Step Functions are AWS' answer to the question "how can we easily execute lambdas from AWS triggers as part of a Saga?" Sagas are hard, and developers already use AWS stuff like S3 and SNS to run lambdas as part of transactions. Providing a high-level Saga service sounds like a solution to everyone's problem, but getting it right seems to be a problem too hard for AWS. But you do not need a Step Functions to run Lambdas, specially if you don't have to run them as part of distributed transactions.