I've been playing around with these platforms for a few months, hosting small node projects on each, but this is getting a little tiring going back and forth from each one.
Thought it would be worth getting DEVs thoughts on these platforms and which ones are being used more in the DEV community.
So, do you use any of these to host your js/node projects?
If yes, which one and why? π¨βπ»π©βπ»
Happy coding!
Oldest comments (23)
I use both Heroku and Netlify.
Heroku for microservices with Node.js/Express.
Netlify to host my static website built with Jekyll.
That seems like a logical split between the two platforms, I've been really enjoying how easy Heruko makes getting an express server up and running π
Yes, that's the reason I chose Heroku over spinning up a DO droplet and setting everything up for such a small service.
Since deployments to Heroku happen through Git, I don't need to set up and maintain tons of CD pipelines for my microservices. π
Finally tried heroku for a node server the other day. I was blown away how easy it was. I setup the server on my local machine. Signed up, installed the heroku cli, and ran 2 commands. 1 minute later and I had a url to my node server in the cloud. I waited so long to try it because I thought it would be complicated, but it was super easy
Neetlify, yet to try Heroku and Now.sh in any big project.
Why heroku/now for larger projects? Databases?
I'm currently using Netlify to deploy/host my site. The documentation in Netlify is super helpful and very user friendly.
Heroku, super easy to use.
Netlify for static sites. Absolutely love how easy it is. And deploy straight from git is just π€©. I wish there was a solution like this for some of our php sites π’.
@seb True that. All ZEIT Now, Netlify and Heroku shine with their github integrations.
ZEIT now shines with your use case. The good news is ZEIT Now does supports Php π
Netlify for a couple sites and then a raspberry pi 3b+ for light node projects
Nifty! Thinking about grabbing a pi 4 to toy around with, they look like a lot of fun π
They are pretty great.. Once the project is production ready it moves off the pi but it helps to be able to deploy and show to whoever outside my network. Plus the non existent latency makes it feel faster then free heroku / digital ocean 5 dollar account
Netlify for front-end, because it's so easy to set up. It's also easy to proxy any backend needs elsewhere via redirects.
I use Serverless Framework and AWS for backend because of its low cost while having flexibility to add more (also low cost) services (e.g DynamoDB).
I have used all ZEIT Now, Heroku, Netlify and Google Firebase. All have features which are unique to their platform, and no one is going to stop making the developer experience better anytime soon, which is extremely good for us all.
I have stuck with ZEIT Now as their developer experience outshines the competitors in more than many use cases. Here are some outshiners:
and if that is already not enough, here is the best one:
I know ZEIT since 2017, I have seen its products evolve, documentation etc. I can give a totally honest opinion of ZEIT : )
2017 & 2018 (until the middle of the year) a container-based approach
Pros:
Cons:
2018 (October) - It's time Serverless <3
pros:
Cons:
now.json, It is necessary to define it when you want to implement an application ofnodebut very soon it will not be necessary to definenow.json. You will only have to execute thenowcommand and that's it πI hope I have helped π