Hi River and group, Joyent does an excellent job of evangelizing node.
I work for a company that no longer considers itself a startup and meets your criteria. Here are my answers that can easily be taken out of context. We used TDD and black box QA process to build out our node backend for uploading media (photos, videos and sounds). I can't give a percentage. The external API and all uploads are backed by node. No gotchas with node. If you have a sane process in place, it will be a joy to deploy. It hasn't ever let us down... Yet. We coded the uploader using Goliath and it just took up too much CPU and memory. The name of the technology should've been a dead give away. ;) Companies: RadiumOne for the Via.Me product which is where I work, and Joyent. My only concern with node is that the wheel has to be re-invented lots but that is ok with my team since they can do their own open source projects. If you or anyone on this list wants to do Node.js for full time work, please email me. Via.Me is looking for coders. Cheers, Jim On Jan 26, 2013, at 12:14 PM, River Lune <[email protected]> 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] > 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 > > > -- -- 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
