Open source at PayPal

PayPal Open-source

Stuff that we learned when we opened up

@saranyan | PayPal Engineering

Hi!

I work at PayPalI run infrastructure and platforms

[email protected] @saranyan

Engineer Experimenter Hacker

mailto:[email protected]


At PayPal we are trying build platforms that don’t look like this


1. Challenges at PayPal 2. What we learned from those 3. How we are turning things around


Understanding open source


We assume - Open source is using stuff that is openly available and submitting pull requests for

enhancements


It is a culture of collaboration and transparency


Legacy Stacks

Challenge #1


Poor building blocks


Challenge #2It is costly to pivot

Business demands

Learning curve

Lack of understanding


Case Study PPaaS


PPaaS

How can we build better REST services?


PPaaS

Services should be easy to build, test and get visibility on Should be easy to deploy


PPaaS

Metrics, infrastructure, testing and monitoring tools


Lay of the land

Some challenges that we deal with at scale @PayPal {metrics/data, technology, deployment)


CAL - eBay’s logging infra logs around 5.7TB worth of data everyday.


Companies need to create a culture where we act as enablers

Learning #1


Empower others to build the features they need without us having to do it.

Learning #1


Organizational structure

Challenge #2


Recognize that we are moving from an ecosystem of support to self-service

Learning #2


On creating open-source

30%

70%

Organizational Technology


On adopting opensource

60%

40%

Organizational Technology


More learnings #3


Creating/adopting Open source

Environment that is supportive of transparency (+tools) Culture of experimentation Rigorous communication

Culture of sharing Federated organizational structure


Things that we are doing


Case study

Solving environment and VM issues


How services talk

Vault

Crypto

DB

DB


Integration/Testing challenges

VM/Stages Reliability


Docker

Our ongoing journey towards having reliable service containers


Docker

- Collaboration with Platform Infra teams and Site Reliability teams

- Prototyping semi-complex services on docker and sharing the builds with other teams

Mesos + Docker registry @PayPal for few services


Case study 2

GENIO


GENIO

SDK autogeneration Ruby


GENIO

- Picking a language/tool with low barrier to entry - Seeding the tools with use cases that are immediately

relevant

Genio is currently used for generating parts of PayPal SDK


Collaboration

Team 1 Team 2


Team 1 Team 2

Visible to team 2 Visible to team 1


Team 1 Team 2

Visible to team 2 Visible to team 1

Medium like Github helps here


For developing a culture of collaboration, it is important to tailor an environment via tools and processes


Our Journey into Node

Krackenjs http://paypal.github.io/


Democratization of individual teams is impossible if core technology is not open


Changing a culture is not just accomplished by technology, but it is a wonderful catalyst

Closing thoughts


Engineers are pragmatic dreamers, excited by possibilities of great things, and work well with a lot of freedom

Closing thoughts


Questions?

I work at PayPalI run infrastructure and platforms

[email protected] @saranyan

mailto:[email protected]