CEO of https://zeit.co here! Happy to answer any questions throughout the day :)
Now: realtime Node.js deployments
11–20 of 121 posts
Re: Now: realtime Node.js deployments
#12Re: Now: realtime Node.js deployments
#13CEO of https://zeit.co here! Happy to answer any questions throughout the day :)
Re: Now: realtime Node.js deployments
#14Earlier quoted context omitted.
Really cool website! I'm confused though exactly what is going on. Is this kind of like Heroku? What are the pros and cons of this service? For context, I'm currently running a production node/express/mongo service on Digital Ocean.
Compared to other providers, there's absolutely no setup involved. No Procfiles, ports, containers, dynos, processes, instances… Just type `now` where you have a `package.json`.
1) Does "Dynamic Realtime Scaling" mean you spin up more clusters and do load balancing automatically?
2) Can your $15/month cost cover this? Or is that what the 50GB bandwidth cap is for?
3) The nature of this service means we need to use a DB service like mLab (mongoLab) or run our own DB server right?
4) What about production logs?
Re: Now: realtime Node.js deployments
#15Re: Now: realtime Node.js deployments
#16Very cool! I was just saying how hard it is to get someone to deploy a quick node app. Trying it with a React + Express app right now. Taking a while to deploy but I assume you are getting hammered.
Re: Now: realtime Node.js deployments
#17CEO of https://zeit.co here! Happy to answer any questions throughout the day :)
Curious about performance of npm install, seems like it's one thing that could make it not so snappy. For compiled modules, does it have a decent amount of memory/CPU on the instances? How about connectivity? Does it use a mirror for NPM? Might it in the future?
Every time you run `now` it's as if you had installed from scratch (including semver invalidations like ^ or ~). The focus is on reproducibility.
Re: Now: realtime Node.js deployments
#18CEO of https://zeit.co here! Happy to answer any questions throughout the day :)
Re: Now: realtime Node.js deployments
#19Earlier quoted context omitted.
Curious about performance of npm install, seems like it's one thing that could make it not so snappy. For compiled modules, does it have a decent amount of memory/CPU on the instances? How about connectivity? Does it use a mirror for NPM? Might it in the future?
Our biggest focus is `npm install` performance. We have multiple caches to make it the best possible experience for you. Every time you run `now` it's as if you had installed from scratch (including semver invalidations like ^ or ~). The focus is on reproducibility.
Re: Now: realtime Node.js deployments
#20Red Hat Openshift has a solid free tier, free SSL, git push deployments, node / ruby / python / java / php / etc., mysql / postgres, redis. Why would I use this over that? https://www.openshift.com/
With the advent of microservices, code will become more succinct. Your backends will be aggregations of small functions with clear inputs and outputs.
The syntactic differences between languages will matter less. Our bet is that JS has the largest and most prolific community!