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

101–110 of 121 posts

Re: Now: realtime Node.js deployments

#101

Post by gkoberger »

mmaunder wrote: post #94
gkoberger wrote: post #92

Earlier quoted context omitted.

Just to piggyback for people confused: It's zero-configuration Node hosting, for permanent lightweight microservices or temporary Node projects that need to be accessible online. In other words, it's as close to uploading PHP files to a server that you'll get with Node. For people wondering, the creator is Guillermo Rauch, who is behind Socket.io and LearnBoost (the company that brought us Express, Mongoose, Stylus,…

Why not just upload node files to a server?

For PHP, you upload index.php, go to yoursite.com/index.php, and it works. Node isn't like that at all. For example, here's the "Hello World" guide for getting Node started:

https://www.digitalocean.com/community/tutorials/how-to-set-...

This is basically the problem `now` is solving... "what if Node was as easy as PHP?"

Re: Now: realtime Node.js deployments

#102

Post by bikamonki »

The pricing structure is missing a couple of middle tiers and overall the service lacks useful features. For instance: I could buy a $5/mo droplet in Digital Ocean, one click install node, even use my own domain and manage deployments/restarts almost as easy. For that money I get 1TB transfer and 20GB ssd and many more features (b/c I basically get a VPS where I can do whatever). It takes me 10 min to setup the server and zero minutes to deploy each new version (I use deploybot so every git push is really a deployment).

Some things are not clear:

"Dynamic realtime scaling" Forever? Unlimited? Say 1MM concurrent API calls for $15/mo?

URLs change after each deployment? Do I need to update endpoints on all clients?

Re: Now: realtime Node.js deployments

#104

Post by ruffrey »

Seems cool. After many years on node, and even writing a deployment service once (paastor) - just plain VPS, nar to make an executable, then scp onto an Ubuntu server, and scp a logrotate and upstart conf - that's all you need man.

Re: Now: realtime Node.js deployments

#105

Post by simula67 »

scriby wrote: post #65

I used to use a project called now on npm that was abandoned a few years ago ( https://github.com/Flotype/now ). I was curious how this new project was using the same name on npm as the previous now that I had used. Looking at the npm release history, versions <= 0.8.1 are the old project, and the new project picked up at 0.9.0 (should have been 1.0.0 I guess). This is consistent with npm's statements about package n…

There should be at least some warning on the page that an earlier project with similar name was replaced with this package.

People make fun of Java's namespace conventions [1], but it goes to show the advantages of not having to have a central authority to decide on these matters.

https://docs.oracle.com/javase/tutorial/java/package/namingp...

Re: Now: realtime Node.js deployments

#107

Post by smt88 »

gkoberger wrote: post #101
mmaunder wrote: post #94

Earlier quoted context omitted.

Why not just upload node files to a server?

For PHP, you upload index.php, go to yoursite.com/index.php, and it works. Node isn't like that at all. For example, here's the "Hello World" guide for getting Node started: https://www.digitalocean.com/community/tutorials/how-to-set-... This is basically the problem `now` is solving... "what if Node was as easy as PHP?"

> For PHP, you upload index.php

That's not inherent to PHP. It's just how most hosts are set up. The only major difference is the order in which things are done (and the necessity to have shell access to the host.)

The real comparison is this:

# PHP # 1. Install a server 2. (Possibly optional) Install a process manager 3. (Possibly optional) Configure the process manager 4. Configure the server 5. Start the server 6. Upload files

# Node # 1. Install Node 2. Upload files 3. Start the server

Re: Now: realtime Node.js deployments

#108

Post by yefim »

Rauchg wrote: post #68
yefim wrote: post #22

Are these zero downtime deployments?

Yes. There's no downtime whatsoever because you don't overwrite or take down anything. Your architecture is immutable. You manage "upgrades" by changing pointers (aliases and DNS). We'll be exploring this in upcoming posts.

It'd be so nice to have it automatically swap the DNS records over. Please consider that as you keep building.

Re: Now: realtime Node.js deployments

#110

Post by egeozcan »

andrewingram wrote: post #90
williamcotton wrote: post #87

Earlier quoted context omitted.

That you can't see how much of a dick you're being when you accuse someone of playing "buzzword bingo" is proof to me that you can't be anything but a god damned troll. This isn't about having different viewpoints. This is about you objectively being an asshole. Edit: Sorry, TRIGGER WARNING: Real things are being said.

If I were accused of buzzword bingo, i'd try to take it as good-natured criticism that what I said was perhaps a little too filled with lingo to have a solid meaning. It's certainly possible to read this example as a trollish remark, there's also a perfectly valid reading which interprets it as an attempt to provide useful feedback. Since I assume neither of us knows q3k, we're not in a position to know which is true…

It becomes pretty clear that it's not a troll when one puts his/her best-effort to interpret "realtime JavaScript cloud". It's a critic with a very obvious point.
Post reply on HN