4 ms·
if you just have webservers, api gateway + lambda is the way to go Edit: to make myself clear, I meant the backend, frontend, of course, should be served like b
by wolfi1 8y ago
if you just have webservers, api gateway + lambda is the way to go
Edit: to make myself clear, I meant the backend, frontend, of course, should be served like below
- WrtCdEvrydy 8y agoCloudfront + S3 for static sites. I've seen so many people just create an EC2 instance for serving static content. If you have a banging new React app that generates static files, you don't need anything more.
- wolfi1 8y agoof course, I meant it backend-wise
- meritt 8y agolambda gets incredibly expensive for anything that approaches even modest usage levels. Once you exceed about 10 requests/second, you'd be better off with the lowest tier virtualized instances ($2 - $5/mo from most providers including AWS)
- RhodesianHunter 8y agoNot if your usage patterns spike dramatically. Once worked at a place that needed to do rapid crawls of websites on short notice and we saved a lot of money by moving from.dedocatrd instances to lamdas that we could scale out and down as needed. How you use them is important.