4 ms·
Small point: what really is the advantage in pushing those services 'to the edge'? AWS lambdas, when they are warm, are fast. Supposing there is a 100ms extra
by jariel 6y ago
Small point: what really is the advantage in pushing those services 'to the edge'?
AWS lambdas, when they are warm, are fast.
Supposing there is a 100ms extra response time due to non-edge and AWS Lambda for whatever reason - is 100ms really the issue when you're facing a blast of 1.5M users? Issn't it the sheer onslaught of scale that is the concern?
It'd seem to be Static hosting some content on S3 + Lambda+Stripe basically would handle the task no problem.
Or am I missing something?
- faitswulff 6y agoAre lambdas limited by region? They noted in the post that they would be expecting the Irish diaspora from 130+ countries to be participating as well.
- pvhee 6y agoIf you can push services to the edge without adding complexity to your setup, why wouldn't you? The simplicity (and pricing model) of running code on Cloudflare Workers should be reason enough to do this. I agree that AWS Lambda for this project would have been more than sufficient, together with S3 for static hosting. However, the advantage of CF workers over is that you combine both the CDN, static hosting, the API layer and the back-end logic running in one and the same worker, therefore significantly simplifying your setup. With AWS (and without using Lambda@Edge), we'd probably have to use a combination of Cloudfront, S3, API Gateway & Lambda. All of these could easily be defined in code with something like the Serverless framework or AWS SAM, but there are a lot more moving parts here when compared to CF Workers.