3 ms·

I don't think there is any significant technical challenges to running this on lambda. You'd just need some sort of workflow to update the lambda image with ea

I don't think there is any significant technical challenges to running this on lambda. You'd just need some sort of workflow to update the lambda image with each blog update. A big downside to hosting on AWS though is if your site gets HN'ed, you could have a hefty bill on your hands.

cpach 5y ago
Couldn’t the risk of hefty bills be lowered by using CloudFront as a caching layer?
jedberg 5y ago
That's unlikely. Using Cloudfront you'd only pay 8 cents per GB (once you get past the 50GB of free data tier). Or you can put Cloudflare in front of it and pay nothing.
- indigodaddy 5y ago
  So I’m not that familiar with using CDNs. So Cloudflare would actually serve 100% of the workload for a static site? That’s where you leave everything default for a domain in Cloudflare’s UI right? Usually I uncheck the “use cloudflare” or whatever they call it, essentially just having Cloudflare do the DNS only.
  - jedberg 5y ago
    Not 100% but petty close. For a mostly static website like a blog it could easily serve 95%+ of the traffic. And yes, it's where you leave it checked to use Cloudflare for your traffic.
    - indigodaddy 5y ago
      Thanks for the response and info!