PayPal has evolved from using a monolithic architecture to a microservices-oriented architecture in order to scale the rapidly growing company. In this talk, We will take a look at how PayPal was architected in the past, some of the issues that we ran into with a monolithic architecture, and how PayPal evolved over time to create a more robust and scalable approach to service deployment by leveraging Postman and implementing a microservices architecture.

2. A Short History of PayPal’s
Microservices Architecture
Matt Cole, Senior Integration Engineer
September 12, 2019

3. Pre-History
© 2019 PayPal Inc. Confidential and proprietary.

5. © 2018 PayPal Inc. Confidential and proprietary.

6. Issues With Deploying New Releases on the Monolithic Architecture
• Package replication happened on the primary network
• Releases had to happen during off-peak hours
• Required a lot of coordination from a lot of cross-functional teams
• Triaging bugs was difficult
• Required a lot of support from technical support teams
© 2019 PayPal Inc. Confidential and proprietary.
Or: “Let this be a lesson to you”

7. ASF
Early Problems and Solutions
Release Architecture
CIPRO
Pimp
No Open Source Code
Isolated Releases
Pimp Breakup
Ok...you can use open
source code

8. Acceleration Continues
(I couldn’t find a logo for this
one)
© 2019 PayPal Inc. Confidential and proprietary.

10. Where are we today?
>700 APIs
Part of PPaaS
16
Functional areas of PayPal contributing
to PPaaS
>2500 Services
Part of PPaaS