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.

2

https://w3-03.ibm.com/finance/finsubp.nsf/WebPages/N01FF08SoftwareRevenueRecognitionGuidelinesRelatedtoProductDisclosures

Please Note:

3

• 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.

© 2015 IBM Corporation4 1

STSM, IBM Runtime Development

@Chris__Bailey

@seabaylea

5

+

Node.js and Java

6

Developer Productivity

7

API Package Support

● Node.js growth: ● 371 packages/day

● Java growth: ● 92 packages/day

8

Open Source Projects

9

Open Source Projects

10

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

11

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….

12

● 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

13

● 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

14

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) {});

15

0

500

1000

1500

2000

2500

3000

regex-dna

n-body

binary-trees

spectral-norm

fannkuch-redux

reverse-compliment

k-nucleo>de

fasta

VolumeofCod

e

Node.js

Java

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

Code required to implement benchmarks

16

“Fullstack” Development

17

● 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....

18

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

19

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

20

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

21

Variable Types

22

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

> 8

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

var a = 5; var b = 3;

add(a, b);

> node app.js

> 8

23




add(a, b); }


> 8


var a = 5; var b = 3;

add(a, b);

> node app.js

> 8

24




add(a, b); }


> 8


var a = 5; var b = 3;

add(a, b);

> node app.js

> 8

25




add(a, b); }


> 8


var a = 5; var b = 3;

add(a, b);

> node app.js

> 8

26




add(a, b); }


> 8


var a = 5; var b = 3;

add(a, b);

> node app.js

> 8

27



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

add(a, b); }


> 8


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

add(a, b);

> node app.js

> 8

28




add(a, b); }


> 8


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

add(a, b);

> node app.js

> 8

29




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

> 8

30




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

> 53

31

JavaScript Calculations

> 5 + 3 8

> '5' + 3 '53'

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

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

> '5' + + '4' 54 // Multiple +'s are ok

> 'Hello' + 'World' 'HelloWorld' // Ok, that's expected

> 'Hello' + + 'World' 'HelloNaN' // ...but that isn't

32


> 5 + 3 8

> '5' + 3 '53'

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


> '5' + + '4' 54 // Multiple +'s are ok



33


> 5 + 3 8

> '5' + 3 '53'

> '5' – 3 2 // String is converted to a number for subtraction


> '5' + + '4' 54 // Multiple +'s are ok



34


> 5 + 3 8

> '5' + 3 '53'



> '5' + + '4' 54 // Multiple +'s are ok



35


> 5 + 3 8

> '5' + 3 '53'


> '5' – '4' 1 // Both Strings converted to number for subtraction

> '5' + + '4' 54 // Multiple +'s are ok



36


> 5 + 3 8

> '5' + 3 '53'



> '5' + + '4' 54 // Multiple +'s are ok



37


> 5 + 3 8

> '5' + 3 '53'



> '5' + + '4' 54 // Multiple +'s are ok



38


> 5 + 3 8

> '5' + 3 '53'



> '5' + + '4' 54 // Multiple +'s are ok



39


> 5 + 3 8

> '5' + 3 '53'



> '5' + + '4' 54 // Multiple +'s are ok



40


> 5 + 3 8

> '5' + 3 '53'



> '5' + + '4' 54 // Multiple +'s are ok



41


> 5 + 3 8

> '5' + 3 '53'



> '5' + + '4' 54 // Multiple +'s are ok


> 'Hello' + + 'World' 'HelloNaN' // Multiple plus must cause String to number conversion

42


> '5' + - '5' '5-2' // I can just about see that works

> var x = 3 undefined > '5' – x + x 5 // Ok, that makes sense

> var x = 3 undefined > '5' + x - x 50 // What???

43



> var x = 3 > '5' – x + x 5 // Ok, that makes sense

> var x = 3 undefined > '5' + x - x 50 // What???

44



> var x = 3 > '5' – x + x 5 // Ok, that makes sense

> var x = 3 > '5' + x - x 50 // What???

45

Performance

● JSON serialization of a newly instantiated object

● Maps - Key of message - Value of Hello, World!

● Example response:

46Results from TechEmpower.com Round 9 tests (2014-05-01)

JSON Serialisation

● JSON serialization of a newly instantiated object

● Maps - Key of message - Value of Hello, World!



JSON Serialisation

Java

JavaScript

48

-100

-80

-60

-40

-20

0

20

40

-75

Node.js Performance

(Compared to Java)

JSON Serialization

%ag

e of

Jav

a P

erfo

rman

ce

Node.js Web App Performance vs. Java

● Fetches single row from simple database table

● Row serialized as JSON



Single Query

● Fetches single row from simple database table

● Row serialized as JSON



Single Query

Java

JavaScript

51

-100

-80

-60

-40

-20

0

20

40

-75

Node.js Performance

(Compared to Java)

JSON Serialization

%ag

e of

Jav

a P

erfo

rman

ce


-100

-80

-60

-40

-20

0

20

40

-60.5

Node.js Performance

(Compared to Java)

JSON SerializationSingle Query

%ag

e of

Jav

a P

erfo

rman

ce

52


● Fetches multiple rows from a simple database table

● Rows serialized as JSON



Multiple Queries

● Fetches multiple rows from a simple database table

● Rows serialized as JSON



Multiple Queries

Java

JavaScript

-100

-80

-60

-40

-20

0

20

40

-60.5

Node.js Performance

(Compared to Java)

JSON SerializationSingle Query

%ag

e of

Jav

a P

erfo

rman

ce

55


56


-100

-80

-60

-40

-20

0

20

40

-18

Node.js Performance

(Compared to Java)

JSON SerializationSingle QueryMultiple Queries

%ag

e of

Jav

a P

erfo

rman

ce

● Fetches multiple rows from a table ● Converts rows to objects and

modifies one attribute of each object ● Updates each associated row and

serializes as JSON ● Example Response:


Data Updates

● Fetches multiple rows from a table ● Converts rows to objects and

modifies one attribute of each object ● Updates each associated row and

serializes as JSON ● Example Response:


Data Updates

Java

JavaScript

59


-100

-80

-60

-40

-20

0

20

40

-18

Node.js Performance

(Compared to Java)

JSON SerializationSingle QueryMultiple Queries

%ag

e of

Jav

a P

erfo

rman

ce

60


-100

-80

-60

-40

-20

0

20

4028

Node.js Performance

(Compared to Java)

JSON SerializationSingle QueryMultiple QueriesData Updates

%ag

e of

Jav

a P

erfo

rman

ce

61


-100

-80

-60

-40

-20

0

20

4028

Node.js Performance

(Compared to Java)

JSON SerializationSingle QueryMultiple QueriesData Updates

%ag

e of

Jav

a P

erfo

rman

ce

More Computation

More I/O

6217*IBM created open sourced benchmark, being considered for endorsement by Node Foundation

Node.js Web App Performance

• Results from Acme Air*: − Flight booking benchmark that includes large I/O component − https://github.com/acmeair/acmeair

https://github.com/acmeair/acmeair

63

● JIT Compilers thrive on certainty ● Allows functions to be implemented as efficiently as possible

● Dynamic typing forces the JIT to do more work: ● Variables could be function, or data ● Variables must be tested to determine how to handle them ● Variable types can change over time

Variable Typing and Just-In-Time (JIT) Compilation

64

Just-In-Time (JIT) Compilation: The ‘+’ operator

int add(int a, int b) { return (a + b); }

65



Add Instruction

66



Add Instruction

Return Result

67


var add = function (a, b) { return (a + b); }

68



Check type of

A

69



Check type of

AString Number

70



Check type of

AString NumberString

Check type of

B

Num

ber

71



Check type of


Check type of

B

Num

ber

Concatenate

72



Check type of


Check type of

B

Num

ber

Concatenate

Concatenate

73



Check type of


Check type of

B

Num

ber

Concatenate

Concatenate

StringCheck type of

B

Num

ber

74



Check type of


Check type of

B

Num

ber

Concatenate

Concatenate

StringCheck type of

B

Num

ber

Concatenate

75



Check type of


Check type of

B

Num

ber

Concatenate

Concatenate

StringCheck type of

B

Num

ber

Concatenate

Floating Point orNormal

NormalFloat

76



Check type of


Check type of

B

Num

ber

Concatenate

Concatenate

StringCheck type of

B

Num

ber

Concatenate


NormalFloat Add Instruction

77



Check type of


Check type of

B

Num

ber

Concatenate

Concatenate

StringCheck type of

B

Num

ber

Concatenate


NormalFloat Add InstructionFloat Calculation

78

Dynamically vs. Statically Typed Languages

-70

-60

-50

-40

-30

-20

-10

0

Dynamic vs Statically Typed Language Performance

JSONSingleMultiUpdates

Bes

t dyn

amic

com

pare

d to

bes

t sta

tic a

s ba

selin

e

● Best statically typed language much better than best dynamic

79

Language Selection

80

“Do one thing, and do it well”

● Services are small and targeted to their task ● Services are organized around capabilities ● Services are self contained, storing their own data

Microservices Paradigm

81

Choosing the Right Language for the Service

82


0

500

1000

1500

2000

2500

3000

regex-dna

n-body

binary-trees

spectral-norm

fannkuch-redux

reverse-compliment

k-nucleo>de

fasta

VolumeofCod

e

Node.js

Java

83

Node.js

0

- 4x

+ 1/3x

Nod

e.js

Per

form

ance

Rel

ativ

e to

Jav

a

CPU Bound I/O Bound

* based on TechEmpower benchmark results

Application Performance (higher is better)


0

500

1000

1500

2000

2500

3000

regex-dna

n-body

binary-trees

spectral-norm

fannkuch-redux

reverse-compliment

k-nucleo>de

fasta

VolumeofCod

e

Node.js

Java

84

Node.js

0

- 4x

+ 1/3x

Nod

e.js

Per

form

ance

Rel

ativ

e to

Jav

a

CPU Bound I/O Bound

* based on TechEmpower benchmark results

Application Performance (higher is better)


0

500

1000

1500

2000

2500

3000

regex-dna

n-body

binary-trees

spectral-norm

fannkuch-redux

reverse-compliment

k-nucleo>de

fasta

VolumeofCod

e

Node.js

Java

Error: incompatible types ClassCastException

85

● Higher performance for I/O ● Easier async programming ● Fullstack/isomorphic development


86


● Higher processing performance ● Type safety for calculations ● Rich processing frameworks

87

● Highly performant, scalable rich web applications ● Highly performant, reliable transaction processing ● Self-contained micro-service components


+

88

EmergingArchitectures

89

Rich Web Applications

90


91


HTTP

92


HTTP

Load

Bal

ance

r

93


HTTP

Load

Bal

ance

r

94

Operations and Management

Admin Analytics

Load

Bal

ance

r

HTTP


95


Admin Analytics

Load

Bal

ance

r

HTTP


96


Admin Analytics

Load

Bal

ance

r

HTTP


97


Admin Analytics

Load

Bal

ance

r

HTTP


Load

Bal

ance

r

98

MicroServices and API Economy

99


Admin Analytics

Load

Bal

ance

r

HTTP


Load

Bal

ance

r

100


Admin Analytics

Load

Bal

ance

r

HTTP


Load

Bal

ance

r

101


Admin Analytics

Load

Bal

ance

r

HTTP


Load

Bal

ance

r

102


Admin Analytics

Load

Bal

ance

r

HTTP


Load

Bal

ance

r

103


Admin Analytics

Load

Bal

ance

r

HTTP


104


Admin Analytics

Load

Bal

ance

r

HTTP


105


Admin Analytics

Load

Bal

ance

r

HTTP


Services

106


Admin Analytics

Load

Bal

ance

r

HTTP


Services

107


Admin Analytics

Load

Bal

ance

r

HTTP


Services

108


Admin Analytics

Load

Bal

ance

r

HTTP


Services

109


Admin Analytics

Load

Bal

ance

r

HTTP


Services

Client

110


Admin Analytics

Load

Bal

ance

r

HTTP


Services

Client

Delivery

111


Admin Analytics

Load

Bal

ance

r

HTTP


Client

DeliveryAggregation

Services

112

Questions?

Notices and Disclaimers

113

Copyright © 2016 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission from IBM.

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM.

Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE USE OF THIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT OR LOSS OF OPPORTUNITY. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided.

Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice.

Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary.

References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business.

Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation.

It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law

Notices and Disclaimers Con’t.

114

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

The provision of the information contained h erein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual property right.

IBM, the IBM logo, ibm.com, Aspera®, Bluemix, Blueworks Live, CICS, Clearcase, Cognos®, DOORS®, Emptoris®, Enterprise Document Management System™, FASP®, FileNet®, Global Business Services ®, Global Technology Services ®, IBM ExperienceOne™, IBM SmartCloud®, IBM Social Business®, Information on Demand, ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®, PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, Smarter Commerce®, SoDA, SPSS, Sterling Commerce®, StoredIQ, Tealeaf®, Tivoli®, Trusteer®, Unica®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.

http://www.ibm.com/legal/copytrade.shtml

Thank YouYour Feedback is Important!

Access the InterConnect 2016 Conference Attendee Portal to complete your session surveys from your

smartphone, laptop or conference kiosk.