This is not strictly a technical question on node, so please excuse if this is the wrong forum, but if you're interested, I'd like to hear your opinions on the following blog post:
http://panyasan.wordpress.com/2012/12/10/why-we-need-a-nodejs-application-server-or-writing-boilerplate-considered-harmful
--
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 nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
--
--
Panyasan, out of curiosity, what is wrong with express and the various auth libraries, etc? All of the pieces you describe exist as libraries, how exactly does this not fit the bill of having generic pieces without being a monolithic system?
That's only three existing projects, so my evidence is tiny compared to the number of projects you or others have already done. But they including the not implemented ones are all very different and have different audiences, and their backends have a lot in common, at least, however, the following three elements:
So again, what you're saying is that trying to solve thins generically is the wrong approach. It might be true for the majority of production-grade apps, but I would know exactly how to hook the application-specific requirements into this one-size-fits-all system. Ok, but enought of this. Thanks again for your thoughtful comments.
What I find interesting to debate is if your general claim (each project is radically different) really is true for everybody. It is true for you of course, and probably for the majority of people posting here. But when I look at my - admittedly anecdotal - experience, I can say that all of the major applications that I build (or would like to build) need exactly the same kind of backend.
Today though I wonder if you looking for the wrong answer, is the new application server not a PaaS API?