Re: [nodejs] Is nodejs ready for Production?

1,601 views
Skip to first unread message

Ben Noordhuis

unread,
Aug 23, 2012, 6:47:23 AM8/23/12
to nod...@googlegroups.com
On Thu, Aug 23, 2012 at 7:42 AM, Hitesh Joshi <hitesh....@gmail.com> wrote:
> I know this question have been asked many times, but my concern is , Is
> nodejs ready for Heavy programming networking applications? For other than
> real time things.
>
> Like for an app with features : user, wall, friends, friends of friends,
> user blog, groups, pages etc..
>
> Should I go with ROR for now ?

In my opinion, all node.js is good for is writing 'Hello, world' HTTP
servers and chat apps. I hear PHP is nice.

On a slightly more serious note: people are deploying large scale
node.js apps and have been for a while, where large means 100,000s of
users, millions of requests each day, etc. I would say it's pretty
battle hardened.

Adam Reynolds

unread,
Aug 23, 2012, 6:53:10 AM8/23/12
to nod...@googlegroups.com

If you need real world examples, the big one I can think of is LinkedIn use it.

--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Nuno Job

unread,
Aug 23, 2012, 6:53:32 AM8/23/12
to nod...@googlegroups.com
> I know this question have been asked many times, but my concern is , Is
> nodejs ready for Heavy programming networking applications?

This is the mantra of Node.js - heavy networking applications. I work
in a nodejs PaaS, and most of the inquiries we get are from telcos and
such.

However, I have never in my life heard of using RoR to connect phone
calls, or to build a smarter DNS server :)

Nuno

José F. Romaniello

unread,
Aug 23, 2012, 7:48:13 AM8/23/12
to nod...@googlegroups.com

2012/8/23 Nuno Job <nunojo...@gmail.com>

This is the mantra of Node.js

I think is a mantra for all software, and specially opensource software.

"is ready for production" could means different things for different people 

I think the real question should be "is node.js ready for my needs?", like "is CRuby ready for doing multi threading for real?" or something alike. And If is not ready for your needs you can try fixing it or using something completely different.

Scott González

unread,
Aug 23, 2012, 8:02:44 AM8/23/12
to nod...@googlegroups.com
On Thu, Aug 23, 2012 at 7:48 AM, José F. Romaniello <jfroma...@gmail.com> wrote:

2012/8/23 Nuno Job <nunojo...@gmail.com>
This is the mantra of Node.js

I think is a mantra for all software, and specially opensource software.

He didn't mean that "production ready" was the mantra, he meant that "heavy programming network applications" was the mantra.

José F. Romaniello

unread,
Aug 23, 2012, 8:06:23 AM8/23/12
to nod...@googlegroups.com
oh sorry!! too early in the morning for me to make comments :)
thanks
2012/8/23 Scott González <scott.g...@gmail.com>

--

greelgorke

unread,
Aug 23, 2012, 8:43:35 AM8/23/12
to nod...@googlegroups.com
trello.com reached 500k users and growing. based on node+express

Rohit Singh

unread,
Aug 23, 2012, 11:53:37 AM8/23/12
to nod...@googlegroups.com
Looking at your requirement, you better go with RoR. NodeJs is battle hardened, true.
But there is a slightly steeper learning curve than RoR. And nodejs is under heavy
development, so things change pretty fast, mostly with packages.

On Thursday, 23 August 2012 11:12:00 UTC+5:30, Hitesh Joshi wrote:
I know this question have been asked many times, but my concern is , Is nodejs ready for Heavy programming networking applications? For other than real time things. 

Mark Hahn

unread,
Aug 23, 2012, 12:28:32 PM8/23/12
to nod...@googlegroups.com
 so things change pretty fast, mostly with packages. 

I don't find this a problem.  It is your choice when you upgrade a package.  NPM is excellent at controlling versions.  Each module of your code has access to its own set of package versions which don't change.

I've bne

--

Murvin Lai

unread,
Aug 23, 2012, 8:44:05 PM8/23/12
to nod...@googlegroups.com
I think after 0.6, it is good for production, as long as you understand what's stable, what isn't.   Of course, you gotta do a lot of test and load testing before putting into production.

I have the node REST service on production even since 0.4 and It already gave amazing result in terms of performance.  The daily users are over 100K, and sometimes spike up 5 folds.   So, I truly believe and trust that node.js (now. 0.8.8) can use for any web / app / service in production. :)

Filipe

unread,
Aug 24, 2012, 12:11:06 AM8/24/12
to nodejs
There's a stock market broker here in Brazil called Clear that uses
Node.js + Socket.io and did an amazing job.

On Aug 23, 9:44 pm, Murvin Lai <murvin...@gmail.com> wrote:
> I think after 0.6, it is good for production, as long as you understand
> what's stable, what isn't.   Of course, you gotta do a lot of test and load
> testing before putting into production.
>
> I have the node REST service on production even since 0.4 and It already
> gave amazing result in terms of performance.  The daily users are over
> 100K, and sometimes spike up 5 folds.   So, I truly believe and trust that
> node.js (now. 0.8.8) can use for any web / app / service in production. :)
>
>
>
>
>
>
>
> On Thu, Aug 23, 2012 at 9:28 AM, Mark Hahn <m...@hahnca.com> wrote:
> > >   so things change pretty fast, mostly with packages.
>
> > I don't find this a problem.  It is your choice when you upgrade a
> > package.  NPM is excellent at controlling versions.  Each module of your
> > code has access to its own set of package versions which don't change.
>
> > I've bne
>

Kevin Liu

unread,
Aug 24, 2012, 1:20:34 AM8/24/12
to nod...@googlegroups.com
Yes, Klout.com, a large-scale consumer website, is running on Node. I'm the lead frontend developer.

Jeff

unread,
Aug 25, 2012, 11:36:26 AM8/25/12
to nod...@googlegroups.com
We've been using Node at Factual since 3.x (we used to use Ruby/Sinatra).  Our node stack (minus the data store) can push about 800 req/sec on an EC2 medium.  After one small hitch early on (a slow socket leak when making client requests), its been rock solid.  The community and support, while not as vast as Ruby's, has been awesome and growing very rapidly.

Without getting into too much detail about trade-offs:
We actually use RoR for a lot of our internal CRUD; Rails is just great these kinds of things.  For your app, if you need a lot of concurrency, quick response times and need to play tricks like chatting and other socket.io-ish things, I would say that Node is a compelling choice.  

-Jeff

Hitesh Joshi

unread,
Sep 17, 2012, 2:12:34 PM9/17/12
to nod...@googlegroups.com
Kevin,

What else does klout.com use other than node for http ? Do you using some filter like nginx and proxy to node?

Just want to know best method to make a node app full of security and no holes.

Nice to know you are lead frontend developer.

Hitesh

Mikeal Rogers

unread,
Sep 17, 2012, 2:25:01 PM9/17/12
to nod...@googlegroups.com
Voxer's entire backend. Linkedin's mobile site. Microsoft Bing's mobile site. I think node is ready, are you ready?

Dav Glass

unread,
Sep 17, 2012, 2:27:25 PM9/17/12
to nod...@googlegroups.com
Don't forget Yahoo's mojito stack, we have several production
deployments running Node :)

--
Dav Glass
davg...@gmail.com
blog.davglass.com


+ Windows: n. - The most successful computer virus, ever. +
+ A computer without a Microsoft operating system is like a dog
without bricks tied to its head +
+ A Microsoft Certified Systems Engineer is to computing what a
McDonalds Certified Food Specialist is to fine cuisine +
Reply all
Reply to author
Forward
0 new messages