3 ms·
As usual with such benchmarks, I miss performance comparisons over time. Did Fargate outperform the other two solutions because it's generally faster or because
by Dunedan 8y ago
As usual with such benchmarks, I miss performance comparisons over time. Did Fargate outperform the other two solutions because it's generally faster or because API Gateway was just slow during the few minutes that benchmark took?
What'd also be interesting here would be a price comparison. Without having done the math I'd expect Fargate to be significantly more expensive than the other solutions, which'd make a nice trade-off of cost vs. performance: If performance matters choose Fargate, if cost matters choose API Gateway as service proxy.
- abd12 8y agoAuthor here. I'd say this was about in line with what I'd see from using API Gateway and Lambda. I thought about doing a price comparison, but that gets really tricky. At some point, you're testing the skills of the tester more than the services themselves. Agree with your expectations though. I think Fargate is naturally faster and can be moreso given the number of knobs you can tune. This will likely cost you more, both in direct resource costs and in engineering time trying to fine-tune the knobs. Whether that's worth it depends on your business needs.
- vanrysss 8y agoIt's a (relatively) fixed-cost model vs pay-as-you-go. At a certain level of traffic something built on top of ALB/Fargate will be cheaper to run than serverless solutions.