0
Release the Kraken
A story of node.js in the enterprise

Jeff Harrell
1. Identify customer impact
In other words, why you want to adopt node.js
Our customer: Paypal engineers
•

Unify web and server teams

•

Modern web developers ♥ JavaScript

•

Less compile time ...
2. Choose a pilot project
Start small and don't boil the ocean
Our pilot: account overview
•

Team had already started on Java

•

Two people to also build it on node.js

•

Java used i...
3. Show data
Numbers are hard to argue
Our data: apples-to-apples
•

Node.js application built 2x as fast as Java

•

Written in fewer lines of code (>33%)

•

D...
Problems along the way
Node.js adoption at PayPal wasn’t always smooth
Our problems
•

Enterprise mindsets – JavaScript is not a toy

•

Moving teams from Java to JavaScript

•

Adopting unix /...
What happened in the end
Customer impact + pilot project + data = ?
The conclusion
•

Java/Spring app shut down; node.js app live!

•

Engineers are excited to move to node.js

•

12+ additi...
Questions
Twitter @juxtajeff

We’re hiring!
Upcoming SlideShare
Loading in...5
×

Node Summit - Release the Kraken

2,239

Published on

A story of node.js in the enterprise.

Published in: Technology, Education
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,239
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
17
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Transcript of "Node Summit - Release the Kraken"

  1. 1. Release the Kraken A story of node.js in the enterprise Jeff Harrell
  2. 2. 1. Identify customer impact In other words, why you want to adopt node.js
  3. 3. Our customer: Paypal engineers • Unify web and server teams • Modern web developers ♥ JavaScript • Less compile time === faster iterations • Node.js for prototypes was well accepted
  4. 4. 2. Choose a pilot project Start small and don't boil the ocean
  5. 5. Our pilot: account overview • Team had already started on Java • Two people to also build it on node.js • Java used internal framework based on Spring • Node.js used kraken.js
  6. 6. 3. Show data Numbers are hard to argue
  7. 7. Our data: apples-to-apples • Node.js application built 2x as fast as Java • Written in fewer lines of code (>33%) • Double the requests / second • 35% decrease in response time (↓200ms)
  8. 8. Problems along the way Node.js adoption at PayPal wasn’t always smooth
  9. 9. Our problems • Enterprise mindsets – JavaScript is not a toy • Moving teams from Java to JavaScript • Adopting unix / open source philosophies • Large teams with node.js frameworks (kraken.js)
  10. 10. What happened in the end Customer impact + pilot project + data = ?
  11. 11. The conclusion • Java/Spring app shut down; node.js app live! • Engineers are excited to move to node.js • 12+ additional web apps currently being built • All future web applications built on node.js !
  12. 12. Questions Twitter @juxtajeff We’re hiring!
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×