Netlify raises $53M Series C as microservices approach to web development grows
I've used Netlify as a "Heroku for static sites".<p>I deploy my React apps and landing pages there and don't need to worry about the underlying compute, or load balancing, or anything else. Thankfully I didn't do any frontend work before Netlify was available!<p>I don't really get all the hype around the Jamstack (<a href="https://jamstack.org/" rel="nofollow">https://jamstack.org/</a>), though.<p>Netlify's hypothesis seems to be that if you deploy websites on CDNs, instead of on web servers, then you'll get better performance.<p>Also, because it's just a static site, there's no backend or database, so you get better security.<p>I accept this hypothesis, but it seems like you still need a backend. Netlify is promoting functions as a service [1] so you can avoid having web servers for the backend too, but I'm a little skeptical you get the flexibility to build applications with dependencies or non-trivial business logic or design with this approach.<p>If anyone's tried a FaaS and this is incorrect, please describe your experience!<p>[1] <a href="https://www.netlify.com/products/functions/" rel="nofollow">https://www.netlify.com/products/functions/</a>