Scribd Logo
Upload

Welcome to Scribd!

  • 22 views

    No Dej S Presentation

    Uploaded by

    cyberpune
    Node.js is an open-source JavaScript runtime environment for building scalable server-side web applications. It was created in 2009 and uses non-blocking I/O and event-driven architecture, making it ideal for data-intensive real-time applications. Node.js relies on Google's V8 JavaScript engine and libuv library for asynchronous I/O operations. It uses a single-threaded event loop model that handles requests sequentially for improved performance and scalability.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    No Dej S Presentation

    Uploaded by

    cyberpune
    22 views24 pages
    Node.js is an open-source JavaScript runtime environment for building scalable server-side web applications. It was created in 2009 and uses non-blocking I/O and event-driven architecture, making it ideal for data-intensive real-time applications. Node.js relies on Google's V8 JavaScript engine and libuv library for asynchronous I/O operations. It uses a single-threaded event loop model that handles requests sequentially for improved performance and scalability.

    Original Description:

    node js

    Original Title

    No Dej s Presentation

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Node.js is an open-source JavaScript runtime environment for building scalable server-side web applications. It was created in 2009 and uses non-blocking I/O and event-driven architecture, making it ideal for data-intensive real-time applications. Node.js relies on Google's V8 JavaScript engine and libuv library for asynchronous I/O operations. It uses a single-threaded event loop model that handles requests sequentially for improved performance and scalability.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    22 views24 pages

    No Dej S Presentation

    Uploaded by

    cyberpune
    Node.js is an open-source JavaScript runtime environment for building scalable server-side web applications. It was created in 2009 and uses non-blocking I/O and event-driven architecture, making it ideal for data-intensive real-time applications. Node.js relies on Google's V8 JavaScript engine and libuv library for asynchronous I/O operations. It uses a single-threaded event loop model that handles requests sequentially for improved performance and scalability.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 24

    Benjamin San Souci & Maude Lemaire

    introduction
    What is Node.js anyway?
    a complete software platform for scalable server-side
    and networking applications
    open-source under the MIT license
    comes bundled with a JavaScript interpreter
    runs on Linux, Windows, Mac OS & most other
    major operating systems

    timeline
    2009

    Created by Ryan Dahl


    Version 1 in 2009 to revolutionize web applications
    Inspired by Ruby Mongrel web server

    2010

    Joyent sponsors Node.js development

    2011

    First released version of Node.js available to the public


    Initial version only available for Linux.
    Microsoft partners with Joyent to provide Windows
    support

    2012

    Complete rewrite of central libraries

    ...
    2014

    Latest release v0.10.26


    Still several improvements away from a stable v0.12
    and a finalized v1.0

    huge success

    why?
    Up until recently, the web was a stateless environment.
    Interactive features were encapsulated within Flash or
    Java Applets
    Node establishes real-time, two-way connections!

    how it works
    Built on Chrome's V8 JavaScript runtime for easily
    building fast, scalable network applications
    Uses an event-driven, non-blocking I/O model that
    makes it lightweight and ecient, perfect for dataintensive real-time applications that run across
    distributed devices

    overall structure
    Two major components:
    Main core, written in C and C++
    Modules, such as Libuv library and V8 runtime engine, also written
    in C++

    overall structure
    Main Single Thread

    All requests handled by the Main


    Single Thread

    API

    API in JavaScript
    Node bindings allow for server
    operations

    Node Bindings
    (socket, http, etc)

    V8

    Asynchronous
    I/O
    (libuv)

    Event
    Loop
    (libuv)

    DNS
    (c-ares)

    Crypto
    (OpenSSL)

    Relies on Googles V8 runtime


    engine
    Libuv responsible for both
    asynchronous I/O & event loop

    v8 runtime engine
    Just in Time compiler, written in C++
    Consists of compiler, optimizer, and garbage
    collector

    libuv
    Responsible for Nodes asynchronous I/O operations
    Contains fixed-size thread pool

    major influences
    Heavily influenced by architecture of Unix operating
    system
    Relies on a small core and layers of libraries and other
    modules to facilitate I/O operations

    major influences
    Built-in package manager contributes
    to the modularity of Node

    major features
    1. Single threaded

    Most other similar web platforms are multi-threaded

    With each new request, heap allocation generated

    Each request handled sequentially

    major features
    2. Event Loop

    Typically implemented using library sand a block call, but Node is


    non-blocking throughout!

    Implemented using language construct

    Automatically terminated

    Tightly coupled to V8 engine

    major features
    3. Non-blocking I/O

    All requests temporarily saved on heap

    Requests handled sequentially

    Can support nearly 1 million concurrent connections

    how it works
    A simple example: accessing data from a database
    1. HTTP
    Request
    Mobile Client

    Node.js
    Single thread

    3. Data
    Database

    Web Server
    4. Response in
    JSON format
    via callback

    2. Async
    Data Query

    * Here Node.js, acknowledges the request right away before writing any data to the database.

    how it works
    A generic model of Node.js

    NodeJS
    Main Event Loop
    Initialize

    Run V8

    Event
    Loop

    Exit

    Stop
    Stop

    Thread n
    Create Thread

    Delegate Task
    Idle

    Perform Task

    I/O Operation

    Exit

    how it works
    A closer look at the Event Loop
    Thread 1

    Thread 2

    Thread n

    (function,
    callback)

    Task 1
    Task 2

    Node.js
    Application

    Event Loop
    (Libuv)
    Callback 1

    Task 3
    Return 1
    Task 4

    major architectural styles

    Distributed
    Hierarchical
    Data Flow
    Implicit Asynchronous

    critical analysis
    Benefits:

    Because of its single-threaded, non-blocking scheme, Node can


    support nearly 1 million concurrent connections

    Asynchronous, event-based scheme allows for scalability, lower


    memory usage & CPU overhead

    Can be used to implement an entire JavaScript-based web application

    Requests are acknowledged quickly due to asynchronous nature

    Native JSON handling

    Easy RESTful services

    Speedy native bindings in C

    Due to its real-time nature, its possible to process files while they are
    being uploaded

    critical analysis
    Best suited for:

    REST + JSON APIs

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

    Quick prototyping

    Rapidly evolving applications: media sites, marketing, etc.

    Chat applications

    Ideal for computing and orchestration tasks divided using worker


    processes

    critical analysis
    Limitations:

    Node & V8 runtime engine are tightly coupled

    Because it is single-threaded, it has a single point of failure for all


    requests (low fault-tolerance)

    Developers beware of exception handling

    Currently lacking standards regarding code quality

    Without a complete v1.0, backwards-compatibility is bogging down


    code base

    critical analysis
    Not suited for:

    CPU-bound tasks

    Applications needing to process large amounts of data in parallel,


    unless using worker processes

    the future of node

    Larger clients are seeking to integrate Node.js into their


    mobile platforms.
    Increasing enterprise influence vs. popularity among
    autonomous developers
    v1.0 release expected by the end of 2014

    You might also like