apidays New York 2023 - Building API Platforms at Scale, Irakli Nadareishvili, JPMorgan Chase & Co

apidays New York 2023
APIs for Embedded Business Models: Finance, Healthcare, Retail, and Media
May 16 & 17, 2023

Building API Platforms at Scale, Best practices and lessons learned
Irakli Nadareishvili, Managing Director, Global Banking Platform at JPMorgan Chase & Co

------

Check out our conferences at https://www.apidays.global/

Do you want to sponsor or talk at one of our conferences?
https://apidays.typeform.com/to/ILJeAaV8

Learn more on APIscene, the global media made by the community for the community:
https://www.apiscene.io

Explore the API ecosystem with the API Landscape:
https://apilandscape.apiscene.io/

Transcript

1. Building API Platforms at Scale Irakli Nadareishvili Managing Director, Global Banking Platform JPMorgan Chase & Co 2023
3. APIs Don’t Matter • They are just interfaces to platforms • It’s building useful platforms that benefit business
4. Meet Michelle – a brilliant CIO
5. SEED(s) Process “APIs First” approach alone, won’t deliver business value. “Reinventing the wheel” risks and ensuing chaos are all too real.
6. SEED(s) Process We need full platforms, aligned with business needs, that drive reuse and standardization. E.g.: customer, sales, billing, accounting platforms.
7. SEED(s) Process But, wait! Reuse is a double-edged sword!
8. Total Cost of Reuse (TCR) In Time Far too often benefits of reuse are assessed at fixed, starting point of time. This is misleading. The long-term implications of coordination costs, created as the side-effect of standardization and centralization, to achieve reuse, must also be forecasted. Init Change 1 Change 2 Change 3 Change 4 … Benefit Cost Cost Cost Cost
9. Frequency of Change – Litmus Test The best value-predictor for the benefits or detriment in Total Cost of Reuse is the frequency of change. Slow-changing shared capabilities are safe for centralization and reuse, while frequently-changing ones usually are not, even if they represent shared needs.
10. Core Principles of Platforms TCR evaluation and appreciation of long-term coordination costs also leads to three main principles of building resilient API-driven platforms at scale that keep platform / consumer separation: 1. Platforms must not be arbiters of “common behavior” for consumers built on top of those platforms 2. Platforms must never orchestrate calls to other platforms on behalf of consumers 3. Platforms may never implement consumer-specific logic
11. And Only then we start writing microservices