IBM InterConnect: Java vs JavaScript for Enterprise WebApps

© 2015 IBM Corporation
AAI-1915: Java vs JavaScript
for Enterprise Web Applications
Chris Bailey: STSM, IBM Runtime Monitoring
Andrew Low: STSM, IBM Containers

3
Java JavaScript Both
0
20
40
60
80
100
120
PercentageofAudience
What languages do you use?

4
Server Java Applets JS in Browser Node.js Rhino Nashorn Avatar.js
0
20
40
60
80
100
120
PercentageofAudience
What runtimes do you use for them?

5

Chris Bailey
STSM, IBM Runtime Monitoring and Diagnostics Architect
- 14 years working with Java and JVM technologies
- 1 year working with Node.js and V8
- 6 months working with Ruby and Python

Recent work focus:
- Java monitoring, diagnostics and troubleshooting
- Java integration into the cloud
- JavaScript monitoring, diagnostics and troubleshooting

My contact information:
- baileyc@uk.ibm.com
- http://www.linkedin.com/in/chrisbaileyibm
- http://www.slideshare.net/cnbailey/
- @Chris__Bailey
Introduction to the Speakers

6

Andrew Low
STSM, IBM Containers Technical Lead, Master Inventor
Previous: JavaScript (Node.js) Technical Lead and J9VM Technical Lead
- 17 years working with Java and JVM technologies
- 2 years working with Node.js and V8

Recent work focus:
- Bluemix and IBM Containers

My contact information:
- Andrew_Low@ca.ibm.com
Introduction to the Speakers

7

Language Adoption

Deployment Modes

Asynchronous IO

WebApplication Performance

Under the Hood

Enterprise Deployments

IBM and Node.js
Agenda

10
GitHub Adoption: JavaScript

13
Ratings based on the number of skilled engineers, courses and third party vendors.
Tiobe Community Programming Index

14
Indeed.com Job Trends: Java

15
Indeed.com Job Trends: JavaScript

17

JavaScript has a large developer base
- #1 on GitHub with 45% more active repositories than Java
- #1 on modulecounts.com with 29% more NPM modules than Maven
- #1 used language by StackOverflow survey responders
- #6 language on the Tiobe index

Java remains hugely relevant, particularly on the server
- #2 on GitHub with 52% more active repositories than the next language
- #3 on modulecounts with 73.8% more modules than the next language
- #2 language on the Tiobe index
- #1 on indeed.com for developer jobs
Language Adoption

19

JavaScript is ubiquitous in the browser
- Supported in every browser
- Full 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…
Usage in the browser

20

Java has a long history on the server
- JPE launched in 1998

Java has rich platform support:
- Linux x86, Linux POWER, zLinux
- Windows, Mac OS, Solaris, AIX, z/OS

JavaScript is a nascent language on the server
- Limited platform support – although its growing
- No API support to interact with the OS

Part of the browser security model
- Frameworks like Node.js have changed that.
Usage on the server

21

Single Threaded Event based JavaScript framework
– Uses non-blocking asynchronous I/O

Wraps the Chrome V8 JavaScript engine with I/O interfaces
– Libuv provides interaction with OS/system

Designed to build scalable network applications
– Suited for real time delivery of data to distributed client

Available on a growing set of platforms
- Windows, Linux x86, Linux ARM, Mac OS, Solaris
- Linux POWER, zLinux, AIX
libuvV8
Node Bindings
Node Standard Library
C
JavaScript
Server Side JavaScript: Node.js

23

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

Number of concurrent customers
determined by number of depot workers

Additional customers wait in a queue
with no response
Typical approach to I/O

24

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

Number of concurrent customers
determined by how fast the food
Server can work

Or until the kitchen gets slammed
Asycnhronous Non-Blocking I/O

25

Tasks must execute quickly to avoid blocking the event queue
- Analogous to work done under a lock
- Stick to the right jobs, eg, I/O
- Delegate CPU bound tasks to back end processes

Easy to run out of memory
- No direct bound on amount of parallel work
- Holding state for each piece or work means unbounded memory usage
Drawbacks of Asynchronous I/O

26

JavaScript is already event based in the browser
- eg. onClick and onMouseOver events

First class functions and closures fit well with events
- Easy to create and pass function callbacks
- Easy to execute callbacks in the context of the event

Node.js execution is based on an event loop
- Asynchronous I/O built in from the ground up

Node.js execution uses a single thread
- No need to worry about locking or shared data
- Most machines are now multi-CPU, so cluster capabilities are provided
JavaScript and Asynchronous I/O

27
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);
}
HTTP Server Example

28
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);
}
HTTP Server Example with Clustering

29

Very little time spent with events on the Event Loop

Provides good scalability, so should provide great performance
for IO bound apps

Like WebApplications...
JavaScript and Asynchronous I/O

31

JSON serialization of a
newly instantiated
object

Maps
- Key of message
- Value of Hello, World!

Example response:
Results from TechEmpower.com Round 9 tests (2014-05-01)
JSON Serialization

32

JSON serialization of a
newly instantiated
object

Maps
- Key of message
- Value of Hello, World!

Example response:
JSON Serialization
JavaScript
Java

33
JavaScript WebApp Performance
-100
-80
-60
-40
-20
0
20
40
-75
Node.js Performance
(Compared to Java)
JSON Serialization
%ageofJavaPerformance

34

Fetches single row from
simple database table

Row serialized as JSON

Example response:
Single Query

35

Fetches single row from
simple database table

Row serialized as JSON

Example response:
Single Query
JavaScript
Java

36
-100
-80
-60
-40
-20
0
20
40
-60.5
Node.js Performance
(Compared to Java)
JSON Serialization
Single Query

37

Fetches multiple rows
from a simple database
table

Rows serialized as
JSON

Example response:
Multiple Queries

38

table

Rows serialized as
JSON

Example response:
Multiple Queries
JavaScript
Java

39
-100
-80
-60
-40
-20
0
20
40
-18
Node.js Performance
(Compared to Java)
JSON Serialization
Single Query
Multiple Queries

40

table

Converts rows to objects
and modifies one
attribute of each object

Updates each
associated row and
serializes as JSON

Example Response:
Data Updates

41

table

Converts rows to objects
and modifies one
attribute of each object

Updates each
associated row and
serializes as JSON

Example Response:
Data Updates
JavaScript
Java

42
-100
-80
-60
-40
-20
0
20
40
28
Node.js Performance
(Compared to Java)
JSON Serialization
Single Query
Multiple Queries
Data Updates

43

Computation speed is (much) slower than Java

I/O speed is higher than Java
-100
-80
-60
-40
-20
0
20
40
-75 -60.5 -18
28
Node.js Performance
(Compared to Java)
JSON Serialization
Single Query
Multiple Queries
Data Updates
More
Computation
More
I/O

45
Class pointer
Locks
Flags
int
Class pointer
Locks
Flags
int
Class pointer
Locks
Flags
int
Class pointer
Locks
Flags
int
Class pointer
Locks
Flags
10
Integer Object
Field Table
Constant Pool
Object Offsets
...
Integer Class

Java objects are fixed in size and shape
●
Values associated with objects are fixed and typed (known what and where it is)

Methods associated with objects are fixed and typed (parameters and return types)
Object Representation: Java
provides type name
Method Table
Super Class

46
Object Representation: JavaScript

JavaScript objects are dynamic in size and shape

Values associated with objects are dynamic and un-typed

Methods associated with objects are dynamic and un-typed
– 32 “slots” exist for method and values with overflow arrays if this is not enough
– Every “slot” is 64bits as any type of data could be stored there
Map
Elements
Extra Props
1: 10
JSObject
2: intValue()
3:
32:
Map
provides “type” value: 1
Map
1:
Length
2:
Fixed Array
Map
1:
Length
2:
Fixed Array
intValue(): 2

47
Object Representation: JavaScript

Order in which methods and fields are added matters

Objects are equivalent and equal, but have different Maps and layouts
Map
Elements
Extra Props
1: 10
JSObject
2: intValue()
3:
32:
Map A
value: 1
Map
1:
Length
2:
Fixed Array
Map
1:
Length
2:
Fixed Array
intValue(): 2
Map
Elements
Extra Props
1: intValue()
JSObject
2: 10
3:
32:
Map B
value: 2
Map
1:
Length
2:
Fixed Array
Map
1:
Length
2:
Fixed Array
intValue(): 1

48

Functions are stored in JavaScript objects as fields
– No fixed set of methods for an object

Objects are not typed, so data much be checked to determine how to handle it
eg. the '+' operator:
• number + number → addition
• string involved? → concatenation
• objects involved? → convert to primitives then addition or
concatenation
eg. property load:
• Load prototype object
• Load getter method
• Load callback function

Therefore not possible to determine what instructions to use just from the source code
JIT Compilation

50
Nashorn and Avatar.js

Nashorn JavaScript engine delivered in JDK8
– Utilizes new JVM level features
for performance

Avatar.js provides Node.js support on Nashorn

Results of “Octane” JavaScript benchmark*:
– Node.js is 4.8x faster
– Avatar.js is >10x larger
* Using Java 8 pre-u20

51
Nashorn and Avatar.js

Nashorn JavaScript engine delivered in JDK8
– Utilizes new JVM level features
for performance

Avatar.js provides Node.js support on Nashorn

Results of “Octane” JavaScript benchmark*:
– Node.js is 4.8x faster
– Avatar.js is >10x larger
* Using Java 8 pre-u40
Feb 12th
, 2015: Avatar is “put on hold”
https://blogs.oracle.com/theaquarium/entry/project_avatar_update

54

2013: PayPal evaluates use of
Node.js for “Account Overview”
– Implementation done in both
Java and Node.js to compare

Node.js implementation
– 50% less development effort
– 33% fewer lines of code
– 40% fewer files
– ~35% faster request response

Note: legacy Java frameworks
involved.....
PayPal and “Account Overview” Project

56

2013: Eran Hammer (WalMart) discovers 200+MB/day leak
– Increasing memory usage at 200+MB/day per server

Application improvements by Eran reduces leak to 8MB/day
– Lots of progress made
– But required months of investigation effort

Identified remaining leak related to HTTP Client Requests
– Unable to make further progress....

Node.js runtime development team required to resolve issue
– 5 core runtime developers/engineers
– 3 weeks of effort
WalMart experiences Node.js memory leak

58

Node.js Foundation Founding Member
– Alongside Joyent, Linux Foundation, Microsoft, PayPal and Fidelity

IBM SDK for Node.js v1.2
– Open source ports of Google V8 JavaScript engine
• Support for POWER and zLinux
– Runtimes available for all platforms to provide consistency
• AIX, Linux (Intel, POWER, System z, Windows, Mac OS X)
– http://www.ibm.com/developerworks/web/nodesdk/
●
IBM Monitoring and Diagnostics Tools
– Live monitoring: Health Center
– GC log analysis: GCMV
– Dump analysis: IDDE
IBM and Node.js

59

JavaScript has a large amount of interest and is growing
– Web applications with code sharing between server and browser
– Async IO and event loop makes it easy to write scalable applications
– Rich set of APIs available via the npm module ecosystem

Dynamic nature makes development easier, but introduces
challenges
– Errors typically found during compilation are found at runtime
– JIT compilation loves certainty, which is removed

Additional “enterprise-grade” capabilities needed
– Monitoring/Diagnostics, Security, Internationalization, etc
– IBM contributing via the newly announce Node Foundation
Summary

60
Related Sessions
Wednesday February 25th
08:00 – 09:00 1917A: Introduction to the IBM Monitoring and Diagnostic
Tools for Java and JavaScript)
Mandalay Bay, Mandalay Ballroom B Chris Bailey
2820A: Developing Single-Page Apps with an Enterprise
JavaScript Framework
Mandalay Bay, Reef Ballroom A Guy Theuws
12:00 – 12:50 6488A: Meet the Experts: End-to-End JavaScript
Mandalay Bay, Meet the Exports Forum #4 Andy Smith
Todd Moore
12:30 – 13:30 3371A: Enterprise JavaScript with the IBM SDK for
Node.js
Mandalay Bay, Reef Ballroom B Andrew Low
17:30 – 18:30 An End-to-End JavaScript Architecture can enable killer Mobile
Apps
Mandalay Bay, Lagoon A Andy Smith

Notices and Disclaimers
Copyright © 2015 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)
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 herein 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, Bluemix, Blueworks Live, CICS, Clearcase, DOORS®, Enterprise Document
Management System™, Global Business Services ®, Global Technology Services ®, Information on Demand,
ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™,
PureApplication®, pureCluster™, PureCoverage®, PureData®, PureExperience®, PureFlex®, pureQuery®,
pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, SoDA, SPSS, StoredIQ, Tivoli®, Trusteer®,
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.

Thank You
Your Feedback is
Important!
Access the InterConnect 2015
Conference CONNECT Attendee
Portal to complete your session
surveys from your smartphone,
laptop or conference kiosk.

IBM InterConnect: Java vs JavaScript for Enterprise WebApps

Recommended

More Related Content

What's hot (20)

Viewers also liked (7)

Similar to IBM InterConnect: Java vs JavaScript for Enterprise WebApps (20)

More from Chris Bailey (20)

Recently uploaded (20)

IBM InterConnect: Java vs JavaScript for Enterprise WebApps