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

61–70 of 121 posts

Re: Now: realtime Node.js deployments

#61

Post by williamcotton »

williamcotton wrote: post #57
q3k wrote: post #53

Earlier quoted context omitted.

> Our focus is on empowering the realtime JavaScript cloud with its rich module ecosystem. I'm sorry, but that's just meaningless buzzword bingo.

Actually, I think the issue is that you just don't understand the meaning of those words. The "rich module ecosystem" he is speaking of refers to npm. With node and npm it is trivial to install a few modules from the command line, write up a custom server, and very quickly have yourself a dynamic web page or API. The "realtime JavaScript cloud" is basically any node application running on a service like Heroku or wit…

I'm gonna go further: that is actually a fantastic mission statement!

I believe that it is very important to have goals that are simple in definition. It can really help the cause if the ultimate meaning is somewhat allusive. The act of interpreting the mission statement bakes in a dynamic element that can help keep an organization from getting stuck in place.

That I can interpret this mission statement in a verbose, complicated and applied manner is an example of its utility.

Re: Now: realtime Node.js deployments

#62

Post by q3k »

williamcotton wrote: post #57
q3k wrote: post #53

Earlier quoted context omitted.

> Our focus is on empowering the realtime JavaScript cloud with its rich module ecosystem. I'm sorry, but that's just meaningless buzzword bingo.

Actually, I think the issue is that you just don't understand the meaning of those words. The "rich module ecosystem" he is speaking of refers to npm. With node and npm it is trivial to install a few modules from the command line, write up a custom server, and very quickly have yourself a dynamic web page or API. The "realtime JavaScript cloud" is basically any node application running on a service like Heroku or wit…

I do understand them exactly the way you explained.

However, they're still a buzzwordful, dodging, non-answer to the relative parents' very simple question. They're a reiteration of the most basic, marketing-level bulletpoints on why node.js and microservices are so wonderful! that barely scratch the surface of real-world software complexity.

Re: Now: realtime Node.js deployments

#63

Post by travjones »

This looks very promising for the node community. I was wondering which cloud infrastructure service they went with to power this. According to the FAQ, they don't rely on just one. Very cool, and if implemented correctly, more resilient.

  Multi-cloud.
  We don't depend on a single specific cloud provider, but abstract them instead.
P.S. Is the markdown parsing broken on the FAQ? Or is that part of the look they're going for?

Re: Now: realtime Node.js deployments

#65

Post by scriby »

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 name transfers during the leftpad debacle, but there's just something weird about reusing package names for totally different projects...

Re: Now: realtime Node.js deployments

#66

Post by axelfontaine »

yefim wrote: post #22

Are these zero downtime deployments?

No. For zero downtime deployments on AWS with blue/green deployments behind EIPs & ELBs, we at Boxfuse (https://boxfuse.com) offer a very easy solution for both Node.js and JVM apps based on immutable infrastructure.

Re: Now: realtime Node.js deployments

#67

Post by chadscira »

joeblau wrote: post #27
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.

http://ngrok.com - is pretty good for that, if the person you're sharing it with is available.

Re: Now: realtime Node.js deployments

#68

Post by Rauchg »

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.

Re: Now: realtime Node.js deployments

#70

Post by js4all »

js4all wrote: post #52
phelm wrote: post #50

Earlier quoted context omitted.

Not received my confirmation email yet, it has been > 10 minutes

Same here. There seem to be problems with the current spike.

I got mine now. It took nearly an hour. Despite that, my early tests ran solid. The apps got hosted on AWS us-west-1.
Post reply on HN