> Building an api with api-gateway + lambda (...) is guaranteed to be more cost-effective for unpredicted load. Depends on the use case. I run a cron monitorin

> Building an api with api-gateway + lambda (...) is guaranteed to be more cost-effective for unpredicted load. Depends on the use case. I run a cron monitoring service on a similar nginx/uwsgi/django/postgres stack [1]. My service needs to handle lots of really small and simple HTTP requests, and almost every request needs to do a (small and quick) database write. I did napkin math – at the current usage levels, Lambda per-request fees alone would use up significant chunk of my current hosting budget. [1] https://blog.healthchecks.io/2019/08/a-look-at-healthchecks-io-hosting-setup-summer-2019/ https://blog.healthchecks.io/2019/08/a-look-at-healthchecks-...