News for hackers. Stuff that matters.
Re:Netlify raises $53M Series C as microservices approach to... by speleding on Saturday March 07, 2020 @07:00AM (#22511165)
Make sure that you've set the correct cache control headers on the S3 objects. So "Max age" should be something far future for static assets and something near future for HTML files.

If you forget that then Cloudfront will retrieve the objects from S3 every time there is any activity on your site and your bill will go up really fast.

Re:Netlify raises $53M Series C as microservices approach to... by nicoburns on Saturday March 07, 2020 @07:15AM (#22511209)
This is precisely why netlify's offering is valuable. It works out of the box with zero config. If you're using a common static site generator you don't even need to setup the build process, just give it your git repo, and push when you want to deploy.
Re:Netlify raises $53M Series C as microservices approach to... by debaserab2 on Saturday March 07, 2020 @05:22PM (#22514629)
That's not really a compelling reason when it's literally a single input field on a form to setup. Also, if you're in the business of web development, HTTP cache control headers are something you should know about regardless.
Re:Netlify raises $53M Series C as microservices approach to... by nicoburns on Sunday March 08, 2020 @09:17AM (#22517865)
As with a lot of AWS, it's easy if you know you need to do it, but there are a lot of gotchas which can be very expensive if hit (and there's no way to limit expenditure).