WHY NODE.JS
A quick introduction
WHY?
- JavaScript in the server and client
- Unifies language and data (JSON)
- Ease of development and code reuse
- Speedy and efficient
- Built on the fast Google V8 JavaScript engine
- Non-blocking, event driven I/O flow allows for single threaded processes to be quick
- Web server accepts the request, spins it off to be handled, and then goes on to service the next web request
- Each request doesn't require a new thread from the server (more RAM), making it able to handle scalability issues
MoRE
- Great for:
- Real-time web applications
- Applications employing push technology
- Large amount of concurrency
- Data intensive applications (not CPU intensive)
"Where Node really shines is in building fast, scalable network applications, as it’s capable of handling a huge number of simultaneous connections with high throughput, which equates to high scalability"
EVEN MORE
-
It’s been open source from the beginning
- Created in 2009
- Great and growing community
- Quick statistics (courtesy http://modulecounts.com/)
- npm - 139/day
- RubyGems - 58/day
- Packagist (PHP) - 60/day
- Is seeing implementation on an enterprise level (i.e. Walmart, Yahoo, Linkedin)
WHY NOT?
-
Not good for CPU intensive needs
- Works best with NoSQL-type databases,
- There are some modules and drivers that work with SQL, but is still a weak point
NODE.JS MEETUP
Thank you for coming.
We'd love your input, thoughts, ideas,
and active involvement!
WHY NODE.JS
By ralucas
WHY NODE.JS
- 363