2280 Evolution of API Architecture_V1.pdf

《2280 Evolution of API Architecture_V1.pdf》由会员分享，可在线阅读，更多相关《2280 Evolution of API Architecture_V1.pdf（11页珍藏版）》请在三个皮匠报告上搜索。

1、October 21-24,2024Mandalay Bay Convention CenterLas Vegas,NevadaSession Code 2280Sancor Seguros-Evolution of API ArchitectureMartin Javier BoettoSancor Seguros Architecture LeaderGrupo Sancor SegurosAgenda0102030405Our CompanyOld ArchitectureFirst Architecture with IBMCurrent API ArchitectureSome nu

2、mbers about our ApisIBM TechXchange|2024 IBM Corporation#IBMTechXchange3IBM TechXchange|2024 IBM Corporation“Argentinas No.1 Insurance Group”Main Business Verticals Sancor Seguros ART Prevention Health Prevention Banco del SolPrecence Argentina Brasil Uruguay Paraguay#IBMTechXchange4ConsCons-Each te

3、am deployed the technologies they knew-There were no catalogs of what was exposed-Duplicity of endpoints with the same functionalities-Direct access to the core databases-Cross-domain integration was the clients responsibility-There was no governance between each domains integrationsProsPros-There w

4、ere not many needs for exposing services-Little need for integration between domains#IBMTechXchange5ConsCons-There were not many needs for exposing services-Little need for integration between domainsProsPros-We started to have more governance of the integrations and services that were exposed-Integ

5、ration between domains mediated by the ESB-We stopped having direct connections from the exposed services to the core databases,it was done through the ESB-Service catalog with Registry-Standardization and canonization of integrations is achieved#IBMTechXchange6ProsPros-Each domain development cell

6、owns its business components and integrations in the ESB and APIs are exposed in APIC-Greater agility for the delivery of a solution-With the API Manager we gain everything that makes up the life cycle of the solution,from development,testing,deployment,in addition to the feature