I agree with Eric and Paul. The following is moving off topic a little, since it talks about concurrency performance of Node vs PHP.
Node seems to be the cool kid on the block nowadays in Silicon Valley. It could be a fad, but I think there might be more to it.
Paul, I'm trying to understand why Node may not good for scaling and/or concurrency. Maybe it's just not as good as Scala? Here are some resources that illustrate why it may be a good contender:
1. This link points to some potential
upsides for Node over PHP, specifically concerning user concurrency. Does this only hold true for concurrency of < 1000 users?
2. You
may have implied that after some threshold of concurrency (maybe >> 10k users), it may not make sense to use Python / Node or Ruby? If this is so, this link seems to say that Node can indeed handle a
large amount of concurrency. This leads me to believe that for scaling, Node may be a good contender?
Unfortunately, since I've never actually implemented a Node server with high concurrency myself, most of my ammunition on this position is academic.
On Fri, Apr 5, 2013 at 4:29 PM, Paul Mooring
<paul@opscode.com> wrote:
I currently work mostly in the web-ops SaaS space and just wanted to throw in my 2 cents here. Ruby, Python and node.js are all in the same performance class. Ruby is perfectly capable of handling a full-scale SaaS app, twitter just goes a bit beyond
full-scale. We (Opscode) recently migrated off running our main code base in Ruby as well. While twitter and opscode both still run a fair amount of ruby in their infrastructures there's one import thing you missed in your reply, they certainly are not moving
to python or node.js because that won't help for real scale. We moved to Erlang and Twitter to Scala, notice those are both functional, concurrent languages using the actor model for concurrency.
I bring this up not to discourage using Ruby, Python or Node.js (well maybe I would discourage node.js a little ;) ), but to bring up that for 95% of the SaaS business out there the performance of the language/framework will always be irrelevant and if
they have less than millions of users performance issues are probably in their code rather than their tech stack.
--
Paul Mooring
Systems Engineer and Customer Advocate
From: Eric Cope <
eric.cope@gmail.com>
Date: Friday, April 5, 2013 3:41 PM
Subject: Re: PHP lifespan
I don't see PHP going away for a long time, unless the PHP core developers fly off into left field and make some crazy decisions.
If I was going to learn new languages, I'd learn:
Ruby - because its becoming ubiquitous, but its too slow for full-scale SaaS stuff, just ask Twitter :)
Python, node.js - for performance.
Just my two cents.
Eric
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
--
Vimal (rhymes with Kimmel) Shah
Front-End / Infrastructure Engineer
Sokikom
Mobile: (480) 752-9269
Email: vimals@sokikom.com