Something I don't remember having seen anywhere is some understanding of why these Java migratees (if that's a word!) decided to look elsewhere in the first place - ie what were the pain points that the business saw in their Java infrastructure that warranted an examination of how and where Node.js could potentially help.
In large corporates such as Walmart, the maxim "if it ain't broke, don't fix it" tends to reign supreme, so I'd be interested to hear about what was broke for them to be bothered to look elsewhere beyond Java. So far it seems that it's mainly a recognition that having front-end folks writing JavaScript and back-end folks writing in Java creates an inefficient and artificial boundary. It also seems that the broader benefits (performance, productivity, etc) of using Node.js emerge once the initial tests and evaluation exercises are performed. Perhaps it's also because these organisations try to keep abreast of new technologies and assess if and how they might benefit them, and, in the case of Node.js, realised, once they played about with it in earnest, that it had potential benefits over aspects of their Java infrastructure that they previously hadn't considered as "broke". Anyway, I'd be interested to read any thoughts on this angle Rob -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/5bfa7981-cbad-4733-8a9a-79740bfe8e0c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
