Netlify raises $30M to replace webservers with Application Delivery Network
1–10 of 187 posts
Re: Netlify raises $30M to replace webservers with Application Delivery Network
#2Netlify is fantastic. It simplifies deployment and delivery of the websites dramatically. What Heroku did for app development, they did for websites. And even though they are nominally static websites, you can wire them with React or Vue and still have apps.
They make my life easy.
Re: Netlify raises $30M to replace webservers with Application Delivery Network
#3Ok, I'm a web dev and I hate having to deal with web servers, configs, CI, etc. The idea sounds great, but I can't understand how this works from this post.
Can someone explain how this works exactly? Are they basically offering a way to prebuild apps to static assets and host them on CDNs? How do server-side only things will happen then?
Re: Netlify raises $30M to replace webservers with Application Delivery Network
#4Netlify is fantastic. It simplifies deployment and delivery of the websites dramatically. What Heroku did for app development, they did for websites. And even though they are nominally static websites, you can wire them with React or Vue and still have apps. They make my life easy.
Agreed. I've switched out my complicated GitHub+S3+CloudFront+Cloudflare for static hosting to Netlify. Netlify also handles some of the stuff you don't even think about - e.g. partial deploy failure. With my past scripts I might push `index.html`, lose network, error out, etc, and not push the updated `assets/blah.css`.
They also have Functions https://www.netlify.com/features/functions/ for dynamic content, but I haven't worked with those, yet.
Re: Netlify raises $30M to replace webservers with Application Delivery Network
#5Netlify is fantastic. It simplifies deployment and delivery of the websites dramatically. What Heroku did for app development, they did for websites. And even though they are nominally static websites, you can wire them with React or Vue and still have apps. They make my life easy.
Agreed. I've switched out my complicated GitHub+S3+CloudFront+Cloudflare for static hosting to Netlify. Netlify also handles some of the stuff you don't even think about - e.g. partial deploy failure. With my past scripts I might push `index.html`, lose network, error out, etc, and not push the updated `assets/blah.css`. They also have Functions https://www.netlify.com/features/functions/ for dynamic content, but I h…
Neither of you explained in layman terms what they actually do.
Re: Netlify raises $30M to replace webservers with Application Delivery Network
#6Earlier quoted context omitted.
Agreed. I've switched out my complicated GitHub+S3+CloudFront+Cloudflare for static hosting to Netlify. Netlify also handles some of the stuff you don't even think about - e.g. partial deploy failure. With my past scripts I might push `index.html`, lose network, error out, etc, and not push the updated `assets/blah.css`. They also have Functions https://www.netlify.com/features/functions/ for dynamic content, but I h…
Neither of you explained in layman terms what they actually do.
it means you set it and forget it
Re: Netlify raises $30M to replace webservers with Application Delivery Network
#7Ok, I'm a web dev and I hate having to deal with web servers, configs, CI, etc. The idea sounds great, but I can't understand how this works from this post. Can someone explain how this works exactly? Are they basically offering a way to prebuild apps to static assets and host them on CDNs? How do server-side only things will happen then?
Think Heroku but just for deploying static assets. You can do something as simple as have a git repo of assets, push it, and you're up and running with SSL, etc, straight away.
How do you get dynamic? Well, they support a build process so static sites or assets can be built at their end, if that's how you roll. But if you want fully dynamic sites, well, no, you can use their AWS Lambda-powered functions service to help build this out, but you won't be deploying something like a PHP or Rails app to Netlify :-) This limitation opens up a lot of other opportunities to simplify deployment, however.
Re: Netlify raises $30M to replace webservers with Application Delivery Network
#8This is just marketing pitch. Could someone paste some technical architecture on how this is done?
Also how you manage applications and data across different jurisdictions and countries?
Re: Netlify raises $30M to replace webservers with Application Delivery Network
#9Ok, I'm a web dev and I hate having to deal with web servers, configs, CI, etc. The idea sounds great, but I can't understand how this works from this post. Can someone explain how this works exactly? Are they basically offering a way to prebuild apps to static assets and host them on CDNs? How do server-side only things will happen then?
This looks a lot like github pages, but with some additional infrastructure? Where does the backend go?
Re: Netlify raises $30M to replace webservers with Application Delivery Network
#10Earlier quoted context omitted.
Agreed. I've switched out my complicated GitHub+S3+CloudFront+Cloudflare for static hosting to Netlify. Netlify also handles some of the stuff you don't even think about - e.g. partial deploy failure. With my past scripts I might push `index.html`, lose network, error out, etc, and not push the updated `assets/blah.css`. They also have Functions https://www.netlify.com/features/functions/ for dynamic content, but I h…
Neither of you explained in layman terms what they actually do.
They're a static site web host. You deploy using git, and they handle pulling your site from git and deploying it to a CDN. If you're using a static site engine like Hugo or Jekyll, they'll build the site for you as well.
I think what people are excited about is deploying a JavaScript-based frontend (probably written in React or Vue.js) using Netlify, so the client-side code is quickly distributed and accessible.