Downloaded 472 times
Uploaded byAkana
API Adoption Patterns in Banking & The Promise of Microservices
The document discusses the adoption of APIs and microservices in banking, emphasizing their role in breaking data silos, fostering internal innovation, and enhancing security. It highlights unique traits of API adoption in banks and contrasts monolithic and microservices architectures, pointing out the benefits and challenges associated with transitioning to microservices. Ultimately, it calls for the creation of digital ecosystems and scalable infrastructures to improve agility, reliability, and security in banking.
More Related Content
Similar to API Adoption Patterns in Banking & The Promise of Microservices
![Devfest Harare 2025 Slides [GDG Harare] - Combined Slide Deck](https://cdn.slidesharecdn.com/ss_thumbnails/ilovepdfmerged12-251029161756-3b829161-thumbnail.jpg?width=640&height=640&fit=bounds)
API Adoption Patterns in Banking & The Promise of Microservices
- 1. API ADOPTION PATTERNS IN BANKING & THEPROMISE OF MICROSERVICES? Sachin Agarwal
- 2. Digital Disruption inBanking Mobile Cloud Customer Centric Block Chain Payments FinTech
- 3. Traditional Bank’s Challenges RegulationSecurity Infighting Mainframes Slow Vision
- 4. What is HinderingBanks from going Digital? Multichannel Cloud Consumer Preferences Block Chain Fintech Speed
- 5. APIs are keyto Competitive Dynamics But there are some specifics traits and adoption patterns unique to banks
- 6. APIs Adoptors inBanking
- 7.
- 8.
- 9. Data Services PackagedApps Mainframes Break Data Silos Create Customer Centric Views Expose as APIs Unlock Data from Legacy Applications
- 10. 1. Unlock Data 2.Share APIs
- 11. Learn to Walk,Before you Run Learn to share Internally
- 12. APIs Foster InternalInnovation and Efficiency • Securely publish, share and use common services • Improve discoverability of internal services • Create internal communities to foster innovation
- 13. Internal API Catalogs •100’s and 1000’s of APIs unlike a few external APIs • Searchable • Policy Based View • Internal Hackathons
- 14. 1. Unlock Data 2.Share APIs 3. Security
- 15. Realizing End-to-End Security Managingthe User Experience Securing the App - PII, PHI Enabling Easy Developer Access Securing the Channel Securing the Backend
- 16. Major API SecurityConcerns
- 17.
- 18. Relevance to PCICompliance • APIs are now part of e-commerce • Card payments pass through API • The infrastructure underlying the API?
- 19. 1. Unlock Data 2.Share APIs 3. Security 4. External APIs
- 20. Open APIs orPrivate APIs?
- 21. 90% Private/PartnerAPIs Customized Contracts/SLA App Provisioning/Security API Federation Why Private APIs?
- 22. 1. Unlock Data 2.Share APIs 3. Security 4. External APIs 5. Step Away from Monolithic Apps
- 23. Monolithic vs Microservices •Unscalable • Hard to manage • Hard to learn • Slow to deploy • Scalable • Easier to manage • Easier to learn • Quick to deploy
- 24. Why should Bankscare? • Benefits – Improved agility – Better reliability, elasticity – Global scalability • Challenges – Restructuring the IT organization – Agile, DevOps – Investments in new frameworks & platforms – Greenfield vs. Re-architecting – New skills development • Design • Development • Testing
- 25.
- 26.
- 27.
- 28. Key Aspects ofDigital Banking • Create Digital eco-systems with APIs • Integrate data and applications to create a digital value chain • Secure your digital interactions • Create a scalable hybrid microservices infrastructure
- 29.
Editor's Notes
- #25 DevOps Orchestration Microservices framework 3 people that understand microservices