Hi River, Here at Autodesk we use Node both as a middleware platform and as a straight-up app-server. (If you aren't familiar with Autodesk, go look it up on Wikipedia.)
A lot of our applications involve 3d rendering, parsing geometries, and integration with 3rd party modules (like 3d printers), all of which rely upon a variety of technologies written in Python, PHP, C, C++, and various .NET versions. Node lives variously between, apart from, and/or under these layers. We've found that Node allows for pretty rapid development. While it provides its own set of challenges (as every language and platform does), the barrier for entry is very low, compared to many others, mostly due to large efforts the community has made. It also does an excellent job of breaking down the barriers between "Front-End" and "Back-End" folks. Engineers are engineers are engineers, which in my opinion, is A Good Thing. Further, the barrier between thought and expression in code seems to be low compared to many languages, edging in somewhere around Ruby in that regard. (Mostly thanks to CoffeeScript, which I was pleased to discover that I didn't hate outright.) Hope this helps! -Skyler Brungardt On Saturday, January 26, 2013, tjholowaychuk wrote: > Now that I've used node for 4 years or so I can tell you it's not much > better than anything else in my opinion, it has pretty large flaws like any > other platform I've used personally, so don't go thinking it's some magic > bullet. For me the major wins are a) it's javascript, b) the module system > is great c) npm is pretty great. Major downsides being a) isolation sucks > b) callbacks are terrible c) error handling is very > annoying/terrible/easily avoided with other approaches. The evented style > parallels the client pretty well so that makes sharing some modules easier > than it would with other concurrency patterns but that's about it. There's > a lot to take advantage of in the community as well, that's obviously > another huge strength now. Just my 2ยข > > On Saturday, 26 January 2013 12:14:45 UTC-8, River Lune wrote: >> >> hi, >> >> i'm interested in learning from anyone who works with a 100+ employee >> company (25-50 engineers) that has chosen to adopt node for any part of >> their stack. >> >> i'm with a fifteen year old company with tons of legacy software (perl, >> mostly). while everyone's interested in beginning the shift away from >> perl, we have some concerns about the bleeding-edgedness of node (and the >> innovative stuff built on top of it, e.g. express (and more frameworky >> frameworks, e.g. tower, geddy), the connect middlewares, etc.) and the >> level of industry adoption that is (or isn't?) happening... i'm making no >> assumptions that such long-standing products as my company offers can >> simply be ported to node, though there is significant interest in adoption >> server-side js -- especially for new product offerings on the roadmap. we >> need to begin somewhere, and we already have a lot of in-house js talent. >> plus, node/websockets/client mvc seems like the best direction for us to >> improve our front-end products. >> >> so, a couple of questions hopefully somebody can address: >> >> how has your team approached the process of deploying node applications >> to production (e.g. q.a./release process)? >> >> what percentage of your user-facing service is backed by node? >> >> what gotchas have you encountered in adopting/maintaining/deploying node >> applications? >> >> do you use something like express for your application infrastructure, or >> something else (geddy, tower)? >> >> what are the major companies that you know of (or have personal or >> professional contacts at), and what level of success have they had >> adopting/developing/**maintaining/releasing node in a high-availability, >> million-plus-user-base context? >> >> what concerns do *you* have using node as a server-side technology? >> >> i'm particularly interested in hearing success stories (the bigger, the >> better, naturally), but also need to know about the gotchas or weird dark >> corners from dev to qa to production release to support and maintenance. >> >> also, anybody know of a node evangelist-type gun-for-hire who could come >> in for a day (or however long) and break down serious knowledge and >> experience at this level? >> >> thanks, >> river >> > -- > -- > 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 > [email protected]<javascript:_e({}, 'cvml', '[email protected]');> > To unsubscribe from this group, send email to > [email protected] <javascript:_e({}, 'cvml', > 'nodejs%[email protected]');> > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > > > -- -Skyler -- -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- 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]. For more options, visit https://groups.google.com/groups/opt_out.
