3 ms·
“Why run on lambda instead of fargate? Oops, we won’t tell you.” - AWS
by faangiq 4y ago
“Why run on lambda instead of fargate? Oops, we won’t tell you.” - AWS
- andrew_ 4y agoThis is going to throw unknowing readers for a loop, because it's a comment trying to be cheeky. Simply put: Fargate/ECS/EC2+EB = long running tasks Lambda = Short burst tasks with a max life of 15 minutes Running a lambda 24/7 will nuke your credit card. Using Fargate for a scheduler/cron job that only runs 4 times a day will nuke your credit card. Use the right tool for the right job.
- alex-korr 4y agoAWS datapipeline is likely the best solution for a longer running batch that gets run 3-4 times a day.
- andrew_ 4y agoIt's definitely an option. Wrapped services are almost always more expensive, so careful attention to pricing details is needed.
- alex-korr 4y agoThe bulk of the cost here is usually on the EC2 side. The main extra cost is the price it takes your runner EC2 instance(s) to bootstrap - ie usually about 2-3 minutes. Can be mitigated by using prepaid discounts, etc.