The document discusses PayPal's adoption of Node.js for their web applications. It describes identifying customer needs like unifying teams around JavaScript, conducting a pilot project building an account overview app in both Java and Node.js, and showing that the Node.js version was built faster, with fewer lines of code, and could handle more requests. While adoption was not always smooth, with challenges around mindsets and frameworks, the pilot was successful and more apps are now being built on Node.js at PayPal.

1. Release the Kraken
A story of node.js in the enterprise
Jeff Harrell

2. 1. Identify customer impact
In other words, why you want to adopt node.js

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. 2. Choose a pilot project
Start small and don't boil the ocean

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. 3. Show data
Numbers are hard to argue

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. Problems along the way
Node.js adoption at PayPal wasn’t always smooth

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. What happened in the end
Customer impact + pilot project + data = ?

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. Questions
Twitter @juxtajeff
We’re hiring!