3 ms·
> If it is highly consistent a server may make sense. I'd argue that you should just package and deploy your Lambda as a Docker image and when you need consist
by oblio 5y ago
> If it is highly consistent a server may make sense.
I'd argue that you should just package and deploy your Lambda as a Docker image and when you need consistency head over to Fargate. It's costs are reasonably comparable with EC2 and you get rid of most Lambda limitations.
- throwaway2016a 5y agoVery good point that the Lambda code can be written in such a way that it can run from both Docker and Lambda. But I'm not a fan of Fargate. I find it easier to use vanilla EC2, and it's cheaper than Fargate. But I'm also very comfortable with EC2 and Fargate takes care of a lot of the ops stuff so to each their own. What I didn't mention too is Lambda has "Reserved Concurrency" pricing which for extremely consistent workloads lowers the gap... I've never had a product with that consistent a workload though.