Why Node is becoming the go-to technology in Enterprise

http://www.nearform.com/nodecrunch/node-js-becoming-go-technology-enterprise/

by unheaped • 12 years ago

32 53 12 years ago

jf22• 12 years ago

If I was the CTO of Walmart I'd fire somebody for doing a deployment on Black Friday.

Even if I was 99% certain everything would go fine that's just too much of a risk to take.

Unless some kind of show stopping issue was happening I'd wait until after cyber monday or plan the release way before hand.

sehr• 12 years ago

Where did you get the idea they deployed for the first time on Black Friday? They had it out and ready well before then.

AjithAntony• 12 years ago

The quoted tweet "... we decided middle of black friday is perfect time for a release"

kiernan• 12 years ago

Where did you get the idea it was the first time? Their point is it's a pretty risky day for any deployment.

jmspring3• 12 years ago

The article lost me at quotes like this one (both for content and persons position when talking enterprise) -- “Why go to Facebook and do PHP when you can go to PayPal and do Node.js” - Bill Scott – Dir UX PayPal

fennecfoxen2• 12 years ago

Clearly you haven't suffered the misfortune of having to program in PHP recently. Alternatively, you may have Stockholm syndrome.

(I mean, Node's okay, not my favorite, but PHP is still as much "training wheels without the bike" as it ever was.)

drakaal8• 12 years ago

Hip Hop, and "PHP" don't really share that much. Wordpress templating is what a lot of people think PHP is like. Zend Framework too. But saying PHP and Hip Hop are the same is kind of like saying Shakespeare and Flavor Flav both speak English.

Sure they both do a lot of Rhyming, but you'd have a hard time getting the two to understand one another.

(I don't like PHP particularly, but calling what FB does "php" is inaccurate)

arbuge• 12 years ago

Misfortune because you have to code in PHP? Seems like a bit of an exaggeration to me...

nivla• 12 years ago

Is "Stockholm Syndrome" becoming the goto plug reply to anyone who doesn't agree with the hivemind? I have been noticing it a lot lately.

Clearly you haven't suffered the misfortune of having to program in PHP recently.

If anything PHP has become a lot better than what it was half a decade ago. Clearly you haven't used it recently.

I find amazing that despite PHP being popular than all the other mainstream web languages combined, comments such as "Does anyone still use PHP?", "PHP is so bad no one ever uses it." show up. Its akin to close your eyes and what you don't like goes away.

I am not rooting for PHP, but comments like these are silly and adds no value to discussion.

jmspring3• 12 years ago

In the past year, I've touched on Erlang, C/C++, C#, Python, Javascript (NodeJS) and PHP.

I take issue with a quote from a Director of UX being used to back up how NodeJS is taking over the Enterprise.

ams6110• 12 years ago

My thought at that was "great, in 12-18 months PayPal will have a bunch of devs saying "why stay here and do Node.js when I can go to company Foo and do <current trendy language du-jour>."

drakaal8• 12 years ago

Ok, so let's start with. No.

For a number of reasons. "Web Scale deployments" like Linked-in and Pay-Pal aren't actually what most people call Enterprise. The line blurs a bit, but because they are Massive Scale Single Task solutions they aren't what the industry defines as enterprise.

Second. Node is use primarily in two places, Private Cloud. (like pay pal and linked in) where you want to run on hardware as a commodity, but don't want the overhead of a true VPS, instead you run in an "Engine" which is hardware independent. That's great if you are Huge. But it makes less sense in traditional enterprise... Which is why we come to number 3....

Third. Node isn't secure enough for Enterprise. Enterprise runs on well tested, secure, solutions, with strong support, because... You can't get hacked, you can't deal with your developer quitting, and you can't deal with the solution is no longer supported.

This piece is marketing hype, not "white paper fact" or even "Case study support"

Yes I expect lots of downvotes, happens every time I say something bad about node. But the truth of it is that Node is for Hackers, not for production. It is tech born from a poorly conceived language, running in an engine that was designed for clients not servers, and unless you have a team of security guys, and a strong proxy, and a bunch of other things, it is not "production safe".

briantakita9• 12 years ago

Node is "production safe". The many deployments and success stories override your fud.

It's time for you to move on and bash a newer, emerging, "unproven" technology.

In the mean time, have fun with cobol, cause that's the only "proven" technology out there :-,

drakaal8• 12 years ago

Number of deployments doesn't equate to secure, or Windows 95 would have been considered Secure in 1996. (It's in good shape these days)

Most companies get Node to be "secure" by putting a Proxy in front of it. Doing a lot of packet inspection, and limiting interactions with the server to validated requests.

If you set something like this up you can make anything secure. But most people can't do this, they don't know how. Most enterprise don't do this because setting up packet inspection for validation requires a lot of planning, and so unless you are massive scale it isn't worth, so this remains in the realm of things only banks and financial institutions do.

kyrra• 12 years ago

For work I've done, NodeJS would have to be proxied behind something like Apache. Specifically for being FIPS 140-2 compliant and tested[0].

[0] http://en.wikipedia.org/wiki/FIPS_140-2

buckbova2• 12 years ago

We're dedicated to Node.js nearForm was founded in 2011 by Richard Rodger and Cian Ó Maidín with the vision to help Node.js to become a mainstream technology.

http://www.nearform.com/about-us

Explains the article. And founding a company to promote a development stack? I don't get it.

jarjoura• 12 years ago

If all you're building is a service proxy to a database, node will get you very far really fast. Its thin layer will allow you write a clean REST api that consumers can reliably call.

Javascript does not scale well though when a project grows to hundreds of thousands of lines of code, but that shouldn't stop you from investigating TypeScript, Dart, or even Coffeescript.

lowboy2• 12 years ago

I am a proponent (and user) of CoffeeScript, but it won't help you very much with maintainable architecture. It's mostly just syntactic sugar over normal JavaScript.

lightblade2• 12 years ago

I work on a large web application that sits currently at 50k lines of CoffeeScript and spans 10+ feature branches at all time.

No, it does not scale. Especially true when the project also spans that many branches. Everyone merging up and down the branches. You get to have backend people merging frontend codes without much problem because it's all dynamic. Then you found out it was a bad merge in production because CoffeeScript doesn't care.

The fact that CoffeeScript makes braces optional causes a lot of problem because when it fails, it fails silently. Bad merge happens, but you'll want it to fail loudly when it does happens.

Out of Dart, TypeScript and CoffeeScript, I recommend TypeScript for large scale projects. Dart is good if you have a lot of man power to build in house components, but it has a very closed ecosystem that does not play well with other JavaScript libraries.

beejiu• 12 years ago

What are you basing "Javascript does not scale well" on? If you are careful about delegating to worker nodes and avoid blocking, Node.js scales quite well for CPU intensive problems. If you have a really CPU intensive problem, you can invoke an external program to do heavy calculations for you.

drakaal8• 12 years ago

Node.js is asynchronous, not Non-blocking. Don't use the two interchangeably, because they aren't interchangeable.

Not understanding this leads to pain and suffering on a massive scale.

rpedela• 12 years ago

I think the OP meant maintaining a large code base not application performance.

BTW did you mean to say "Node.js scales quite well for CPU intensive problems."? If so, that is very incorrect. I/O intensive yes, CPU intensive no.

briantakita9• 12 years ago

commonjs modules are a great abstraction. I have a codebase in the 10^5 magnitude of LoC. It's a pleasure to work with. I don't see any code maintenance issues with scaling 1 or 2 orders of magnitude. Maybe memory issues? But then, it probably makes sense to break up your services.

briantakita9• 12 years ago

Node.js, with browserify, is great for client side development. That alone makes it a good fit for any web programming shop.

bowlofpetunias• 12 years ago

Selling Node.js like snake oil with hollow marketing BS is seriously going to backfire very, very soon.

I have no strong feelings about Node either way, but people who value Node should downvote stuff like this into oblivion.

I've seen more substance in copy for a Herbalife ad.

programminggeek• 12 years ago

If Node is taking over the enterprise, we are going to have a lot of broken Enterprise apps that are wildly unmaintainable in a few short years.

jfoutz• 12 years ago

Yeah. That'll be very different from, say, Thursday.

briantakita9• 12 years ago

Because good programmers get turned into bad programmers by node.js.

And bad programmers get turned into good programmers with the mainstream technology X.

thirsteh• 12 years ago

Call me when the average node.js programmer picks up Haskell. We'll be better off in nearly every conceivable way.

jmspring3• 12 years ago

Honest question - this is like the 4th NodeJS related article to make it to the first page in the last couple of days after a period of quiet. Is there something in the Node ecosystem prompting this?

carsongross• 12 years ago

Thank goodness!

I never thought I'd live to see it, but, finally, after all these years... A silver bullet has been found, gentlemen!

philosophus• 12 years ago

"becoming the go-to technology in Enterprise[y]"

Hmm, I work for a company that processes insurance claims. That's enterprisey, right? Let me tell you you'll get a blank/'are you crazy' type stare if you suggest node.js here (rightly or wrongly). We use programs written in COBOL running on AS/400. That's insurance/banking enterprise software. The very thought of running some trendy hipster WWW-popup-box-turned-server-side "programming language" like JavaScript for anything -- anything at all -- is likely to be met with disgust. Like I said, this might not actually be the right attitude to take, but rest assured the "nobody ever got fired for buying IBM" attitude still prevails in the truly enterprisey enterprise.

Why Node is becoming the go-to technology in Enterprise

Related Stories