A few random thoughts...
Unless you have specific inter-operability requirements, or something else,
I would consider looking at different database solutions. Mongo melds
nicely to JavaScript - natively dealing with json data transport (bson
internally) and processing js functions internally. But there are also a
plethora of lucene based solutions. There are SQL modules for node, but
generally that isn't the best tool for the job.
Last time I looked there was no way of creating an xls file (I don't recall
xlsx but since a good portion of the world is office <2010 its moot for
me). You can make an rpc API or use a preexisting one (gearman comes to
mind) and use the excellent perl module for this (and I hear there's a Ruby
one as well).
There are no good classic MVC frameworks for node. You can define a single
view with express and jump into middleware to pump out json, XML, binary,
etc but you've got to try to keep things nice when you do this. There is
also railway and a nodejitsu framework that look like they might be awesome
in a year (but I'd dev with express at this point).
Node isn't as mature as PHP - its getting there quickly though. I never got
into rails much, but it seems that node is moving much faster than rails
ever did (in all aspects). Node development and adoption is surely moving
faster than PHP ever did. My only worry is that people will get too
comfortable with node and nosql DBs and forget basic security and make
vulnerable sites which might give node bad press (I hope medeor has had
improvements since I last looked - that scared me).
Don't write server side js like you write client side js. I use it because
it removes one language or DSL from my app. But I can tell whether I'm
looking at my server side code vs client side code from across the room
(not sure if this makes sense to anyone else or if I'm not doing things
correctly, but to me the code just looks different).
Since node is a standalone server, I think you'll notice a smaller
footprint (than mod_php in Apache) though I'd still run production behind
nginx (just because of mod_security, offloading static file server, and
load balancing).
On Oct 10, 2012 3:42 AM, "Wil Moore" wrote:actually my hosting provider has fixed 256MB RAM for one application mysql
will be handled by other ram. so what do you think how much request nodejs
can service in a month in this ram?
That will be fine initially.
@WIL MILLER why dont you share your experience about how to actually do
async compact & maintainable code in js
Quick tips:
1 - Learn how to create modules asap.
2 - Test drive your code.
3 - Read this:
https://github.com/rwldrn/idiomatic.js.4 - Learn about constructors, prototype chain, and prototypal inheritance.
That should get you going.
--
Job Board:
http://jobs.nodejs.org/Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-GuidelinesYou received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to
nodejs@googlegroups.comTo unsubscribe from this group, send email to
nodejs+
unsubscribe@googlegroups.comFor 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-GuidelinesYou received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to
nodejs@googlegroups.comTo unsubscribe from this group, send email to
nodejs+
unsubscribe@googlegroups.comFor more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en