3 ms·
We use Fargate a lot for internal tooling. It's pretty great! Being able to schedule containers instead of Lambdas is nice, and genreally not having the restric
by lvh 7y ago
We use Fargate a lot for internal tooling. It's pretty great! Being able to schedule containers instead of Lambdas is nice, and genreally not having the restrictions of a Lambda environment is nice.
We have, no joke, Lambdas that kick off Fargate tasks to do "actual work". Why do we have Lambdas? Because that's the integration point AWS has everywhere. "Run code when X happens" on AWS means a Lambda, so that's what we use.
- poxrud 7y agoI think that this should be the only use case for lambdas. They should respond to events and act as the glue between aws services. If you're doing anything that requires a running time of over 200ms you should be using a proper app server, probably inside a docker container.
- pbalau 7y agoI have on my todo list a lambda function that will get invoked from bitbucket and will kick off a bunch of tasks. Then another one that can be called multiple times and let you know if those tasks finished and the exit code.