If You plan to use JSON Rest API and something like Backbone.js - then maybe it's a good fit. If on the other hand You want something like traditional site with lots of forms and server-side templates - node won't be a good fit.
It looks more like a specialized high performant server, not a high productivity tool for building sites. For its high performance You'll pay with degraded development productivity. P.S. Does anyone really estimated how much will be losses in case of some (0.00...X) transactions lost due to lack of transactional support in mongo? I mean in stores like amazon - it's not a question, losses are huge, but in case of an ordinary e-shop? Are they really so big? One developer cost about 100 / per-year, so, mongo allows to build product faster and thus save cost on development time (although, it's also subject to question). The question is - what's higher - cost of development or lost transactions. -- 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
