InterConnect2016: WebApp Architectures with Java and Node.js

Emerging Web App ArchitecturesUsing Java and Node.js

IMPORTANT info regarding IBM speaker guidelines and disclaimers

• If your presentation has forward looking content, it is mandatory that you put the forward disclaimer as slide 2 in your presentation (this is the “Please Note” slide, third slide down in this template).

• All presentations, whether they have future content or not, must include the mandatory “Notices and Disclaimers” – slides 8 and 9 in the template. Insert these slides just before the “Thank You” slide in your deck.

• Please refer to the FAQ document in the Speaker Kit regarding additional legal guidance for use of photos, logos, customer references and analyst information.

• It is recommended to have your material reviewed by Legal if you have any concerns regarding your content.

• Please submit your final presentation, using the instructions in the online Speaker Kit, by February 5th, 2016. Post your final file in native format using the following naming convention: session code.ppt (For example, 1576.ppt)

• Disclosures regarding forward guidance is embedded in the tool and also available through this link: • https://w3-03.ibm.com/finance/finsubp.nsf/WebPages/N01FF08SoftwareRevenueRecognitionGuidelinesRelatedtoProductDisclosures

• Please remove these instructions before finalizing your presentation.

Please Note:

• IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion.

• Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision.

• The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract.

• The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

• Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

STSM, IBM Runtime Development

@Chris__Bailey

@seabaylea

Node.js and Java

Developer Productivity

API Package Support

● Node.js growth: ● 371 packages/day

● Java growth: ● 92 packages/day

Open Source Projects

var cluster = require('cluster'); var cpus = require('os').cpus().length; var http = require('http');

if (cluster.isMaster) { for (var i = 0; i < cpus; i++) { cluster.fork(); } cluster.on('death', function(worker) { console.log("Worker" + worker.pid + "died"); }); } else { http.createServer(function(request, response) { response.writeHead(200, {"Content-Type": "text/plain"}); response.write("Hello World!\n"); response.end(); }).listen(8080); }

Writing a HTTP Server

var cluster = require('cluster'); var cpus = require('os').cpus().length; var http = require('http');

if (cluster.isMaster) { for (var i = 0; i < cpus; i++) { cluster.fork(); } cluster.on('death', function(worker) { console.log("Worker" + worker.pid + "died"); }); } else { http.createServer(function(request, response) { response.writeHead(200, {"Content-Type": "text/plain"}); response.write("Hello World!\n"); response.end(); }).listen(8080); }

And Clustering It….

● One thread (or process) per connection - Each thread waits on a response - Scalability determined by the number

of threads

● Each thread: - consumes memory - is relatively idle

● Concurrency determined by number of depot workers

Typical Java Approach to Scalable I/O

● One thread multiplexes for multiple requests - No waiting for a response - Handles return from I/O when notified

● Scalability determined by: - CPU usage - “Back end” responsiveness

● Concurrency determined by how fast the food server can work

Node.js approach to Scalable I/O

Node.js event based programming

var http = require('http');

var server = http.createServer(); server.listen(8080);

server.on('request', function(request, response) { response.writeHead(200, {"Content-Type": "text/plain"}); response.write("Hello World!\n"); response.end(); });

server.on('connection', function(socket) {}); server.on('close', function() {}); server.on('connect', function(socket) {}); server.on('upgrade', function(request, socket, head) {}); server.on('clientError', function(exception, socket) {});

regex-dna

n-body

binary-trees

spectral-norm

fannkuch-redux

reverse-compliment

k-nucleo>de

VolumeofCod

Node.js

● Average 45% less code required for Node.js implementation

Code required to implement benchmarks

“Fullstack” Development

● The web has moved from Web Sites to Web Applications

From Web Sites to Web Apps

● JavaScript is ubiquitous in the browser - Supported in every browser - Integration with HTML and CSS

● JavaScript is not affected by negative publicity....

Unless it is absolutely necessary to run Java in web browsers, disable it as described below, even after updating to 7u11. This will help mitigate other Java vulnerabilities that may be discovered in the future.

This and previous Java vulnerabilities have been widely targeted by attackers, and new Java vulnerabilities are likely to be discovered. To defend against this and future Java vulnerabilities, consider disabling Java in web browsers…

Programming in the Browser

FullStack JavaScript Development

● Reuse of programming skills and teams ● Reuse of skills for both client and server side code

● Reuse of “isomorphic” code components ● Reuse of code for both client and server ● Write One Run Anywhere

● Faster user experience performance ● Use of server side rendering

Server Side Rendering

● Pre-Initialisation of the client UI on the server:

● Improves time for the first elements appearing in the UI

● Has additional benefits: ● Search Engine Indexing ● Easier code maintenance

Variable Types

Simple Calculation: 5 + 3

private static void add (int a, int b){ System.out.println(a + b); }

public static void main(String[] args){ int a = 5; int b = 3;

add(a, b); }

> javac app.java > java app

var add = function (a, b) { console.log(a + b); }

var a = 5; var b = 3;

add(a, b);

> node app.js

add(a, b); }

var a = 5; var b = 3;

add(a, b);

> node app.js

add(a, b); }

var a = 5; var b = 3;

add(a, b);

> node app.js

add(a, b); }

var a = 5; var b = 3;

add(a, b);

> node app.js

add(a, b); }

var a = 5; var b = 3;

add(a, b);

> node app.js

public static void main(String[] args){ String a = new String(“5”); int b = 3;

add(a, b); }

var a = ‘5’; var b = 3;

add(a, b);

> node app.js

add(a, b); }

var a = ‘5’; var b = 3;

add(a, b);

> node app.js

add(a, b); }

> javac app.java Error: incompatible types: String cannot be converted to int add(a, b); ^

var a = ‘5’; var b = 3;

add(a, b);

> node app.js

add(a, b); }

> javac app.java Error: incompatible types: String cannot be converted to int add(a, b); ^

var a = ‘5’; var b = 3;

add(a, b);

> node app.js

JavaScript Calculations

> 5 + 3 8

> '5' + 3 '53'

> '5' – 3 2 // Weak typing, implicit conversion

> '5' – '4' 1 // String minus String = Integer??