API World 2017 - Building Large Scale Web Apps and Platforms
1 like•1,120 views
This document discusses architectural patterns for building large scale web platforms. It outlines eight patterns: 1) Separating out the initial renderer, 2) Implementing microservices for core operations, 3) Using a facade to abstract operational concerns, 4) Employing asynchronous communication where possible, 5) Strategically caching data, 6) Managing state at the client or facade layer, 7) Adhering to a strict API specification, and 8) Using mocks for testing. The key takeaways are building generic APIs, separating concerns, sharing context, and enabling faster deployment cycles. The PayPal Checkout API is provided as an example of these patterns in practice.
API World 2017 - Building Large Scale Web Apps and Platforms
- 1. Building Large Scale Web Apps and Platforms ©2017 PayPal Inc. Confidential and proprietary. Anurag Sinha • 09/26/2017
- 2. ©2017 PayPal Inc. Confidential and proprietary. Twitter - @anuragS28 LinkedIn - https://www.linkedin.com/in/sinhaanurag/ ANURAG SINHA (PayPal) 2
- 3. ©2017 PayPal Inc. Confidential and proprietary. Table of contents Platform Centric Approach Architectural Patterns Key TakeAways PayPal APIs 3
- 4. ©2017 PayPal Inc. Confidential and proprietary. Platform Centric Approach 4 Single Page Applications Blurring line between Web Apps and APIs Reuse at Scale Truly Centralized Server Architecture Thinking in terms of Platform Capabilities
- 5. ©2017 PayPal Inc. Confidential and proprietary. 5 Platform Architecture Patterns – Name and Title
- 6. ©2017 PayPal Inc. Confidential and proprietary. Pattern 1 - Separate Out Initial Renderer 6 Renderer Renderer A Renderer B Browser or UI Client Initial Request Angular Experience Initial Request React Experience Core Services User Service Cart Service Payment Service Other Clients API Operations
- 7. ©2017 PayPal Inc. Confidential and proprietary. Pattern 1 - Separate Out Initial Renderer ✓ Serve different front ends while reusing core biz logic ✓ Isolate experience state to initial renderer ✓ Enforce homogenous contract for core services ✓ Unified platform to serve experiences and APIs
- 8. ©2017 PayPal Inc. Confidential and proprietary. Pattern 2 - MicroServices Create Read Update Delete Operations User Cart Payment Resources Data Store Cart PaymentUser Services User Cart Payment
- 9. ©2017 PayPal Inc. Confidential and proprietary. Pattern 2 - MicroServices Design core operations as Micro-Services Spectrum of Concerns: From Resource to Operations Stateless Services Good Ole’ SRP (Single Responsibility Principle)
- 10. ©2017 PayPal Inc. Confidential and proprietary. Pattern 3 - Facade Abstracts Operational Concerns User Cart Payment Services Facade Auth Logging Resource Mapper ✓ Generic concerns such as Authorization, Validation and Logging abstracted by a facade ✓ Maps resources for internal vs external clients and APIs ✓ Orchestrate calls to multiple core services ✓ Act as a robust layer to keep core platform generic
- 11. ©2017 PayPal Inc. Confidential and proprietary. Pattern 4 - Async where you can Sync where you must! ✓ Non blocking communication ✓ Increase decoupling in the stack ✓ Lessen impact of errors in ✓ Act as a robust layer to keep core platform generic ✓ Preserves autonomy Cart Service User Service Async Callbacks
- 12. ©2017 PayPal Inc. Confidential and proprietary. Pattern 5 - Cache Strategically ✓ Front end clients ✓ Facade layer ✓ Core services design UI Client Facade UI data Styles, images etc. Orchestration data Common Business Objects User Service Cart Service User data Cart data
- 13. ©2017 PayPal Inc. Confidential and proprietary. Pattern 6 - State Management 13 Stateful UI Flow State Orchestration Context Context sharing Cart Operation Payments OperationsUser Operations Interface Context sharing Interface User Service Cart Service Payments Service UI Client Facade
- 14. ©2017 PayPal Inc. Confidential and proprietary. Pattern 6 - State Management ✓ Manage state at the client or facade layer ✓ Context sharing between core services can happen via shared request interfaces ✓ Statelessness enables generic use and decreases points of failures ✓ React.js and Angular.Js allow pushing state to the client
- 15. ©2017 PayPal Inc. Confidential and proprietary. Pattern 7 - Adhere to a spec ✓ Enforces strict contract ✓ Make each service independently testable and deployable ✓ Makes the whole stack framework/language agnostic ✓ Spec frameworks provide a lot of the tools out of the box
- 16. ©2017 PayPal Inc. Confidential and proprietary. Pattern 8 - Use Mocks 16 Facade UI Client Layer Cart Service Payment Service Mock APIs Cart/Payments Mock Downstream Mock Payments Mock Downstream Mock Cart Mock
- 17. ©2017 PayPal Inc. Confidential and proprietary. Pattern 8 - Use Mocks ✓ Mock stubs at each layer ✓ Lesser dependence on environment for testing ✓ ECI pipelines run and certify all use cases ✓ Front end clients ✓ End to End stack regressions
- 18. ©2017 PayPal Inc. Confidential and proprietary. Key Takeaways Build Generic APIs Kill State Seperation of Concerns and Resources Context Sharing Scalable and Faster Deployment Cycles
- 19. ©2017 PayPal Inc. Confidential and proprietary. PayPal Checkout API - Built on Platform Architecture Patterns 19 Checkout APIs https://developer.paypal.com/docs/ api/orders