3 ms·

Heroku for backend, automatically grow or shrink resources, nothing to maintain, nothing to configure and tons of services available alongside it. Netlify for

Heroku for backend, automatically grow or shrink resources, nothing to maintain, nothing to configure and tons of services available alongside it. Netlify for frontend, it is a static hosting service with some neat features like url rewriting that lets you proxy e.g. /api to a backend without revealing api keys and under the same origin / domain. What really draws me to this is: - no servers or software to maintain - horizontal scaling by design (heroku kind of forces it) - deploy process is "git push", fresh deploy is one click (heroku) and a few mins doing config on netlify though they have an api so maybe that's redundant - no lock-in, easy to replicate locally - databases are managed wrt backups, recovery etc - entire front end is static and will scale indefinitely with massive uptime https://heroku.com/ https://heroku.com/ https://netlify.com/ https://netlify.com/

pspeter3 11y ago
Why netlify and not S3 + CloudFront?
- benologist 11y ago
  The final outcome is the same - static files on a cdn - so it won't always matter but netlify lets you: 1) run a build process 2) own domain with automatic ssl and redirecting to w/e www-or-not, https-only etc 3) deploy with git push 4) url rewriting, header inserting, proxying
  - ChristianBach 11y ago
    Exactly, and because of the automatic URL rewriting Netlify will also give you instant cache validation. So when you update your site, unlike most static site hosts, you won't have to wait to see your changes live. But at the same time you get a very cached and very fast site. So best of both worlds.
- deleted 11y ago
  [deleted]
- bobfunk 11y ago
  We have an article on our blog about some of the differences. Typically you'll have to do quite a bit of work to get the same performance on S3+CloudFront as out of the box with Netlify, and if you do set up things to be as fast there, you'll suffer from slower cache invalidation. https://www.netlify.com/blog/2015/03/06/comparing-netlify-and-s3 https://www.netlify.com/blog/2015/03/06/comparing-netlify-an...
bliti 11y ago
What kind of traffic does your heroku instance handle? How many dynos and which dynos do you use?

pspeter3 11y ago

Why netlify and not S3 + CloudFront?

benologist 11y ago
The final outcome is the same - static files on a cdn - so it won't always matter but netlify lets you: 1) run a build process 2) own domain with automatic ssl and redirecting to w/e www-or-not, https-only etc 3) deploy with git push 4) url rewriting, header inserting, proxying
- ChristianBach 11y ago
  Exactly, and because of the automatic URL rewriting Netlify will also give you instant cache validation. So when you update your site, unlike most static site hosts, you won't have to wait to see your changes live. But at the same time you get a very cached and very fast site. So best of both worlds.
deleted 11y ago
[deleted]
bobfunk 11y ago
We have an article on our blog about some of the differences. Typically you'll have to do quite a bit of work to get the same performance on S3+CloudFront as out of the box with Netlify, and if you do set up things to be as fast there, you'll suffer from slower cache invalidation. https://www.netlify.com/blog/2015/03/06/comparing-netlify-and-s3 https://www.netlify.com/blog/2015/03/06/comparing-netlify-an...

bliti 11y ago

What kind of traffic does your heroku instance handle? How many dynos and which dynos do you use?