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

Case study: How & why to build consumer apps with Node.js

venturebeat.com

Post reply on HN
Print view View original

1–10 of 16 posts

Re: Case study: How & why to build consumer apps with Node.js

#3

Post by stephth »

With PHP and PostgreSQL we could scale up, but it felt really hard and gave us many sleepless nights. Using Node.js with a MongoDB backend scaling up is quick and easy; but because Node can handle more traffic, you don’t need to as quickly.

It's interesting to read an experience where Node's performance largely pays off when building traditional sites. I've often read that Node's performance really only pays off when building realtime apps. Maybe I misinterpreted, perhaps it was meant more as the large set of features provided by frameworks like Rails/Django transcend Node's performance boost?

Re: Case study: How & why to build consumer apps with Node.js

#4

Post by tedsuo »

stephth wrote: post #3

With PHP and PostgreSQL we could scale up, but it felt really hard and gave us many sleepless nights. Using Node.js with a MongoDB backend scaling up is quick and easy; but because Node can handle more traffic, you don’t need to as quickly. It's interesting to read an experience where Node's performance largely pays off when building traditional sites. I've often read that Node's performance really only pays off when…

In short, even "traditional" apps now actually have to do quite a lot of IO, and the ability to cram a large number of requests into a single process can have a dramatic increase in efficiency. If your ruby/php applications are memory bound, you might see a huge increase in availability by switching to node (or any shared-memory concurrency model).

There is no Rails equivalent in node, and in general I would say the community is focused on writing code at a slightly lower level than the high level frameworks you might be used to. But if you feel like you've internalized the RESTful MCV design, you may find the performance increase worth the lack of handrails.

Re: Case study: How & why to build consumer apps with Node.js

#5

Post by tikhonj »

AdrianRossouw wrote: post #2

We pivoted from being a Drupal shop to being a Node.js shop just over a year ago. I don't think a single one of us has regretted that decision.

Aren't Drupal and Node at vastly different levels of abstraction? I gather that Drupal is vaguely akin to a souped-up WordPress while Node is a fairly low-level server.

Did you start writing lower-level code, or are you using some sort of extensive stack on top of Node?

Re: Case study: How & why to build consumer apps with Node.js

#6

Post by danielhunt »

AdrianRossouw wrote: post #2

We pivoted from being a Drupal shop to being a Node.js shop just over a year ago. I don't think a single one of us has regretted that decision.

Having worked quite a bit in the Drupal world, since 4.6, I demand more info :)

Node and Drupal are completely different beasts. Did you write a new system built on Node, that duplicates what you get with Drupal? Is any of your code public, so others can look into it?

Re: Case study: How & why to build consumer apps with Node.js

#7

Post by peterhunt »

Come on, let's stop the Node.js ridiculous hype already.

1. It's JavaScript! JavaScript is a terrible language. The fact that you need to read "JavaScript: The GOod Parts" in order to use the damn thing is an indicator of that.

I don't care that it's supposedly "lispy."

2. Code re-use at every level

Does any project actually do this? Is there any sort of front-end library that actually works both in Node and in the browser? It seems like more of a pipe dream to me. An awesome idea, for sure, but never actually implemented in practice.

3. Strong, responsive and enthusiastic community

This is moot if there aren't good libraries available. There are, but other platforms have far better ones available and I wouldn't count this as a plus for Node.

Maybe you're talking about Reddit or HN headlines, though.

4. Large productivity gains in HTML & CSS using Jade & Stylus

Never used them, but finding a library or framework that works for you is awesome.

5. Wealth of hosting options: No.de, Joyent’s SmartMachine, Heroku, Nodejitsu

You can say the same thing about PHP too. That doesn't make it a good reason to use it.

6. Make your developers famous

Seriously?

7. Developer happiness

HN fame?

Re: Case study: How & why to build consumer apps with Node.js

#8

Post by tomjen3 »

peterhunt wrote: post #7

Come on, let's stop the Node.js ridiculous hype already. 1. It's JavaScript! JavaScript is a terrible language. The fact that you need to read "JavaScript: The GOod Parts" in order to use the damn thing is an indicator of that. I don't care that it's supposedly "lispy." 2. Code re-use at every level Does any project actually do this? Is there any sort of front-end library that actually works both in Node and in the b…

I too hate Javascript, but mostly because it is not a language suited to go above a few houndred lines of code -- it is awesome to quickly add some interaction to a website.

That said, Node.js is really well designed. I just wish it was done with some other less dynamic language.

Re: Case study: How & why to build consumer apps with Node.js

#9

Post by threepointone »

peterhunt wrote: post #7

Come on, let's stop the Node.js ridiculous hype already. 1. It's JavaScript! JavaScript is a terrible language. The fact that you need to read "JavaScript: The GOod Parts" in order to use the damn thing is an indicator of that. I don't care that it's supposedly "lispy." 2. Code re-use at every level Does any project actually do this? Is there any sort of front-end library that actually works both in Node and in the b…

Regarding point 2: http://developer.yahoo.com/blogs/ydn/posts/2011/11/yahoo-ann... http://geddyjs.org/ and _many_ other diy projects (search for backbone code reuse, for eg).

The rest if it; yeah... well that's just like, your opinion, man.

Post reply on HN