From my presentation at OSCON 2014 http://www.oscon.com/oscon2014/public/schedule/detail/37779 Abstract: There’s only one way to do it here at PayPal – with a framework. Everything you’ll ever need is done if you stay inside the lines. Imagine my reaction when I joined PayPal with Scala and high hopes. We have many reasons to avoid the monolithic framework, so we were going against the grain from day 1. My team came on to “shake things up” and we’ve been doing just that. We brought Scala to PayPal, built small components to defeat “framework-itis” and generally pissed some people off. Now we want to open source the stuff we’re building. I’m going to talk about our challenges so far, and how we overcame them. I’ll have tales (both funny and sad) to tell about my experience so far, and I’ll share plenty of lessons learned along the way.

1. The Epic Battle
Scala @ PayPal
A semi-sarcastic illustrated journey

2. Sr. MTS, PayPal!
github.com/arschles!
@arschles
Aaron Schlesinger

3. PSA Slide
• I’m good at writing software
• This talk is about things I’ve noticed when I
wasn’t writing software
• All opinions are mine only

4. History
• StackMob acquired by PayPal
• We write Scala servers at scale
• We’ve felt the pain

5. It Might Suck to Code
at PayPal

7. We’re Getting Better

8. Good People
Don’t (yet) do their best work

9. If you feel like you aren’t in control of your destiny, you will
give up and accept whatever situation you are in.
Learned Helplessness
http://youarenotsosmart.com/2009/11/11/learned-
helplessness/

11. The Framework
LH @ PayPal

13. Frameworks
Do it all, one line of code!
Unless you can’t.
Then you’re f**cked.

14. Needz Moar
Frameworks

16. We Live with Failure
• Real != Ideal
• Just say no
• Walk away

18. The Trump Card

20. Components
Build out

22. Unix Philosophy

23. Documentation
Explain your component in 1 sentence

24. Spring Framework
Introduction
!
The Spring Framework provides a comprehensive programming and configuration model for modern Java-based enterprise
applications - on any kind of deployment platform. A key element of Spring is infrastructural support at the application level:
Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic,
without unnecessary ties to specific deployment environments.
!
Features
!
Dependency Injection
Aspect-Oriented Programming including Spring's declarative transaction management
Spring MVC web application and RESTful web service framework
Foundational support for JDBC, JPA, JMS
Much more...
!
http://projects.spring.io/spring-framework/

26. Spray Framework
spray is an open-source toolkit for building REST/HTTP-based integration layers on top of Scala and Akka. Being
asynchronous, actor-based, fast, lightweight, modular and testable it's a great way to connect your Scala applications to the
world.
!

27. PSA Slide
Spring is a great framework that’s battle tested by a bunch of huge,
successful companies that make tons of money. It obviously has huge
value!
!
Also, there are smart people behind it and they deserve tons of
recognition for building a great framework.
!
I’m picking on Spring here for illustrative purposes.

28. Meatspace
Frameworks

29. Communication !=
Meetings

31. I Don’t Believe You
Unless it’s Working Code

32. Communicate With
Code
I want people to talk about the code they’ve written

33. InnerSource

35. Inner Source
Think outside the firewall!

36. My Trust Issues

37. Open Source

38. Kraken
krakenjs.com

39. Kraken
Glue code

40. Kraken
BYOF

42. PayPal-Isms
• Tightly coupled with Security
• Tightly coupled with Ops
• Tightly coupled with deployment
• Tightly coupled with monitoring
• Tightly coupled with logging

44. My Team Will Do
Better

45. Open Sourcing Our Scala
Stealing ideas from Kraken

46. Bundling
Stuff my team knows works, has support, has community

47. Beyond Bundling
Get experience, be opinionated

48. Being Opinionated
• Enforce Style Guidelines
• Use the Type System
• Enforce Compiler Warnings
• Make Failing Builds Critical
• Use the Best Testing Frameworks
• Have Real Time Statistics
• Demand Non-Blocking I/O
• Use Akka Properly (that’s another talk)
• Profile Regularly

49. Being Opinionated
My team is being “confident” on purpose.
We’re ready to be wrong.

51. I Want
To have a voice in the Scala Community

52. I Want
The community to make my team better

53. I Want
Fame and fortune for me and my colleagues

54. That’s it

55. github.com/arschles
@arschles
arschles.github.io
I exist in person too

56. Logistics
In case you care

57. Scala
$NAME