Curb your Enthusiasm: Sustainable Scaling of APIs API Days Melbourne 2023 

2 Sathyakhala Anantharajan API Platform Leader, Medibank Mathangi Vijayshankar API Chapter Lead, Medibank 

Integrations & APIs  Integrations history dates back since 1970  Post Pandemic disruptions 3 

No content

Many Key Scaling Challenges Persist 5 50% 57 % 70 % 59 % Increased in Integration Development time Slow to roll out new products Failed due to pre- mature Scaling Delivery delays Poor Dx & inadequate Documentation Poor Communication Pre-Mature Scaling Security concerns 

Scaling Considerations 6 Organisationa l Strategy /alignment Effective Team Scaling API Governance & Design Technology choices Team Culture & Speed bumps Observability & Measuring success 

Organizational Strategy & Alignment  Often Company goals are articulated at a very high level and have many disjointed strategies.  The need to have an aligned Partner, Digital and API strategy with Clearly defined Missions and Goals, in line with the corporate strategy is essential.  These Missions & Goals should be:  Clear & Strategically grounded  Valuable and measurable  Holistic in scope 7 

 APIs scattered across  Not up to date or Not defined at all - Standards, Guidelines and Principles not up to date or not defined at all.  More Provider- Driven APIs  Inconsistent API Documentation  API Ownership lacking or non- existent 8 API Governance & Design 

9 API Governance & Design Provide Guidelines as early as possible. Inbuilt governance into your automation as much as possible. APIs should talk business language & should be system agnostic. Always have a hybrid Design review model in place Consistency and Repeatability is the Key 

10 Technology Choices  API Infrastructure  API Development Platform 

11 Technology Choices  API Security  API Gateway  API Developer Portal 

12 Technology Choices  Test Automation  Monitoring and Alerting 

13 Observe and Fine tune 

14 Observe and Fine tune Security Metrics DORA Metrics API/Platform/Team Metrics  Level Of Preparedness  Number of Incidents  Mean Time to Detect  Mean Time to Resolve  Access Management  Company Vs Peer Performance  Deployment Frequency  Lead Time For Changes  Time to Restore Service  Change Failure Rate  Active use of APIs  Most Heavily Used APIs  Reuse of APIs  Speed to market an API  Cost to build & run an API  Code Quality + Automated tests Coverage 

15 Team Culture & Principles  Build for Reuse Automate, Automate & Automate Curiosity & Innovation Continuous Improvement 

16 Speed Bumps Knowledge Gaps Manual Activities Code Quality Interfacing Systems 

Effective Team Scaling 17 Distributed Teams Recruitment 

Scaling Considerations 18 Organisationa l Strategy /alignment Effective Team Scaling API Governance & Design Technology choices Team Culture & Speed bumps Observability & Measuring success Organisationa l Strategy /alignment API Governance & Design Technology choices 

19 Key Take aways  Align Your API strategy  Provide an inbuilt Governance as early as possible  Bring APIs as products and cultivate Outside in Thinking  Choose the right Technology for future Scaling  Choose the right team topology based on your API Landscape maturity and organisation Operating model  Measure and Fine Tune  Adapt for change 

No content

21 Thank you ! STAY CONNECTED Sathyakhala Anantharajan Mathangi Vijayshankar https://www.linkedin.com/i n/mathangi-vijayshankar/ https://www.linkedin.com/i n/sathyakhala- anantharajan/