2105 Telefonica- A Case Study Journey Describing our API Connect.pdf

1、*Este documento est clasificado como PUBLICO por TELEFNICA.*This document is classified as PUBLIC by TELEFNICA.Javier TinaoDigital Backend and Integrations ChiefOctober 2124,2024Mandalay Bay,Las VegasTelefonica Argentina:A Case Study Journey Describing our API Connect Architecture and Deployment Evo

2、lution Between 2023-2024.*Este documento est clasificado como PUBLICO por TELEFNICA.*This document is classified as PUBLIC by TELEFNICA.AgendaIBM TechXchange|2024 IBM Corporation01 Evolution of our API Connect core architecture02 Strategies and techniques for evolving our APIC v5 compatible APIs to

3、APIC v10.03 ACE and ApiConnect levering 04 Datapowers X3 native V10.(slide 9)05 Breanchmarking06 Monetization of APis*Este documento est clasificado como PUBLICO por TELEFNICA.*This document is classified as PUBLIC by TELEFNICA.*Este documento est clasificado como PUBLICO por TELEFNICA.*This documen

4、t is classified as PUBLIC by TELEFNICA.API Conectarchitecturein TelefonicaIBM TechXchange/2023 IBM CorporationOur architecture:Managed,Cloud and On-prem deployments across a single API Management solution *Este documento est clasificado como PUBLICO por TELEFNICA.*This document is classified as PUBL

5、IC by TELEFNICA.*Este documento est clasificado como PUBLICO por TELEFNICA.*This document is classified as PUBLIC by TELEFNICA.4in Telefnica(Lo dejamos)API Connect ecosystemIBM TechXchange/2023 IBM CorporationAPI ConnectAPI ConnectSecureOptimizeControleCommerceAPPWEBCRM*Este documento est clasificad

6、o como PUBLICO por TELEFNICA.*This document is classified as PUBLIC by TELEFNICA.API Connect Architecturein TelefonicaAppliance X3We worked during 2023 on the technological replacement of our infrastructure from DatapowersX2 to X3.Not only were we at Back Level but we also had capacity problems and