Saltar al contenido principal
Oscar Renalias
Getting started with Node.js
October 11, 2013

Organizers

Top Media Partner

Media Partner

Supporter
About me

@oscarrenalias
github.com/oscarrenalias
oscar.renalias@accenture.com

oscar@renalias.net
Server-side
Javascript
•

Dynamically typed

•

Supports functions/closures

•

Object-oriented with prototype-based inheritance

•

Standardized as ECMAScript
V8: High Performance JavaScript Engine
•

JIT to native: x86, ARM and MIPS

•

On-the-fly recompilation of “hot” functions with an
optimizing compiler

•

ECMAScript compliant
Single threaded??
Asynchronous, Event-based

Event
producers

Event
Event

Event

Callbacks
Single threaded, asynchronous, event-based!

Wait for
callback

Wait for
I/O

Wait for
I/O

Callback
ready
Event callbacks
Sequential callbacks?
So why are async and events good?
•

Easier to write

•

Scales better

•

Lower memory, CPU overhead
Rapid prototyping, rapid development
RESTful services with no effort
No-fuss, native JSON handling
Awesome Package management

•

Gets out of the way

•

Support for internal and public modules

•

Kiss problems with transitive dependencies goodbye
Community modules
http://npmjs.org
Interesting Projects: Express
•

Minimal web application framework

•

Additional features are provided as modules or
middleware: template engines, models, authentication
and authorization, etc
Interesting Projects: Socket.io
•

Provides support for server-initiated push events using
WebSockets, Ajax polling, Iframe, JSONP or Flashbased channels

•

Transparent for both clients and servers

•

Can run standalone or integrated with Express

SERVER

CLIENT
Interesting Projects: Meteor
•

Next-gen framework for real-time collaborative web
applications

•

Live page updates

•

Support for offline databases with subsequent
synchronization
When to use Node.js
•

REST+JSON APIs

•

Backend for single-page web apps: same language in
client and server

•

Real-time web apps with Socket.io and Meteor

•

Quick prototyping

•

Rapidly evolving applications: media sites, marketing,
etc
When not to use Node.js
•

CPU-bound tasks

•

Multi-threaded applications

•

Applications that have to process large amounts of
data

•

Boring CRUD-type web apps
Ready for the Enterprise?
Maturity
•

Under development since 2008

•

Node.js 1.0 around the corner

•

Nearly 40000 modules available via npm

•

Awesome community

•

Commercial support
Lightweight Architecture Enabler
Does it Scale?
Performance

Test: multiple database queries per request, serialized as JSON
responses
More Performance

Test: return a response as a simple serialized JSON object
Source: http://www.techempower.com/benchmarks/
Not the fastest; does it always
matter?
Javascript

Weird
shit

Like Java, with
simple syntax
and no types
JavaScript is quirky different
•

Prototype-based inheritance

•

“==“ versus “===“

•

The meaning of “this”

•

Call, apply and bind in Function.prototype

And more.
Solid development toolset
Toolset
•

Large selection of testing libraries: unit testing,
functional testing, BDD

•

Static code analysis (JsHint)

•

IntelliJ IDEA, Eclipse (Nodeclipse) integration:
highlighting, refactoring, debugging

•

Integration with Jenkins/Hudson, Node.js specific CI
servers

•

NPM supports internal module repositories
Architects have a little bit of extra work
Node.js currently lacks standards; extra effort and
care must be paid to
•

application architecture,

•

development lifecycle,

•

code quality,

And many more.
Big teams, big codebases
Where does it run?
Is it commercially supported?
Joyent is the corporate
steward of Node.js, the
world’s best runtime for
today's data-intensive,
real-time applications.
Joyent offers exclusive
debugging and
performance analysis
tools for Node.js
applications.
Anybody using it?