Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Now: realtime Node.js deployments

zeit.co

Post reply on HN
Print view View original

21–30 of 121 posts

Re: Now: realtime Node.js deployments

#23

Post by bufo »

Rauchg wrote: post #20
seibelj wrote: post #15

Red 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/

Our focus is on empowering the realtime JavaScript cloud with its rich module ecosystem. 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!

How are you thinking about latency in an environment where there's a waterfall of Now function calls? Will Now functions calling over Now functions naturally get cached on the same server?

Re: Now: realtime Node.js deployments

#26

Post by alanh »

Rauchg wrote: post #17
benatkin wrote: post #13

Earlier 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.

> Every time you run `now` it's as if you had installed from scratch (including semver invalidations like ^ or ~). The focus is on reproducibility.

This is very confusing to me as these seem to be contradictory statements. Installing "from scratch" (I take this to mean, as if node_modules is an empty folder) is not a reproducible action, as all it takes is one sub-dependency releasing a new version to change your installation.

Can you clarify what you mean and resolve this seeming paradox?

Re: Now: realtime Node.js deployments

#27

Post by joeblau »

seibelj wrote: post #15

Red 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/

This seems like a different use case than those solutions. This is if you're working on a project and you want to share the state of what you're working on across the net. Think of it like a point-in-time disposable link shortner but for a full node app.

Re: Now: realtime Node.js deployments

#28

Post by Rauchg »

bufo wrote: post #23
Rauchg wrote: post #20

Earlier quoted context omitted.

Our focus is on empowering the realtime JavaScript cloud with its rich module ecosystem. 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!

How are you thinking about latency in an environment where there's a waterfall of Now function calls? Will Now functions calling over Now functions naturally get cached on the same server?

There's no explicit concept of "now functions". You simply deploy HTTP/2 services to the cloud.

HTTP/2 significantly improves performance by introducing multiplexing and header compression. There's no need to introduce new concepts or APIs. REST away!

Post reply on HN