2618 - Sales Proccess Modernization with Openshift on IBM POWER.pdf

《2618 - Sales Proccess Modernization with Openshift on IBM POWER.pdf》由會員分享，可在線閱讀，更多相關《2618 - Sales Proccess Modernization with Openshift on IBM POWER.pdf（24頁珍藏版）》請在三個皮匠報告上搜索。

1、Diego Nakamura:CTO Compaa Financiera Argentina(Customer)Adolfo Billinger:CTO Baloon Technology(IBM Partner Gold)A Success Story in a Financial CompanyImplementation of Red Hat OpenShift on IBM POWER9 for Sales Process ModernizationAgenda1.Introduction2.About CFA3.A bit Story4.Project Context5.Projec

2、t Objectives6.Legacy Arquitecture7.Technologies Used8.Project Phases9.Results10.Challenges and Solutions11.Business Impact12.Conclusion13.Q&AIntroductionDiego Nakamura:CTO Compaa Financiera ArgentinaAdolfo Billinger:CTO Baloon Technology(IBM Partner Gold)About Compaa Financiera Argentina S.A.Interbo

3、no S.A.was founded in 1982GFG acquired CFA in 2008AIG acquired CFA in 1998GG acquired CFA in 2017In 1994,Interbono was renamed to1994 Establishment of the Efectivo S brandAbout Compaa Financiera Argentina S.A.Efectivo S has“60 branches”across the countryOfferavarietyoffinancialproducts,suchasloans,i

4、nsurance,investments,etc.Before the quarantine:The customer used to go in person to the branchesEfectivo Si had“100 branches”(2020)A bit storyThe Covid came:The Argentine governmentdecidedtoconfinethepopulationathomeandshutdowntheformaleconomy.The Citizens had to changetheir mindset and startedusing

5、 digital platforms likedigital wallet,e-commerce,online banking,apps,etc.A bit storyProject ContextThe quarantine was over:The Government lifted the restrictions and people did not go to thebranches in mass anymore and today we have a mixed economy ofservices(digital and PtoP)The consequences Efecti

6、vo S closed 40 branchesWith the rise of digital fraud and attacks,we need to think differentlyabout business.Project ContextIBM Power9 E980 platform(2)AS/400CRM(Siebel)ScoringMiddleware monolithic servicesRed Hat OpenShiftOld Middleware to interface with external entities like bureaus,central bank,e

7、tc.Legacy Platform Power 9 E980SOA:Monolithic Complex architecture Identifying problems Modifying parts of the code Deployment Freezing service(out of services)A difficult problem in trace analysis Etc.Continuous training of young developers The code is complex Architecture Old platform security Bac

8、kup/Restore BCP Etc.Additional issues:Project Objetives Our primary goal for the project was to:Reduce the time to develop and deploy the new servicesImprovement of security in the codeIncorporate DevSecOps functionStandardize code,platform and deliveryProvide the 24x7 window of time for the service

9、Improve scalability,resilience and overall efficiency for the systemEnhance our ability to efficiently handle peak loadsTechnologies Used IBM POWER 9 E980-High performance and reliability IBM FlashSystem:Low latency and high throughput storage Red Hat:Enterprise Linux for IBM Power Premium:Enhanced

10、security,performance,and scalability OpenShift Container Platform for IBM Power Premium:Simplified application scaling and management Container Registry(OCR):Integrated registry for storing and distributing container images Keycloak OAuth:Authorization framework for secure,delegated Access Istio:Ser

11、vice mesh to manage microservices communication,security,and monitoring Prometheus:Monitoring and alerting toolkit for collecting and analyzing metrics Jenkins:CI/CD automation server to streamline software development processes Velero for backup:Data protection and disaster recoveryProject PhasesPh

12、ase 1:Initial MigrationSurvey and AnalysisSizing and PlanningSetup and ConfigurationPhase 2:Migrating Sales ProcessContainerizationReengineering IntegrationsPhase 3:Migrating ESB ServicesService TransformationAdoption of MicroservicesPhase 1:Sizing and initial MigrationSizingAnalysis of collected in

13、formation.Creation of a document with proposed architecture and necessary resourcesEvaluating Current(applications,WAS,ESB,DB)Measure Current ResourcesMeasure Transactions per Second(TPS)and Response TimesInitial Sizing for OpenShiftDivide into PodsNodes ConfigurationPhase 2:Migrating Sales ProcessC

14、ontainerized Engine,Internal References,and Credit EvaluationsTransformed integrations to microservicesExample:Credit Evaluation microservice breakdown Application ContainerizationApplication AnalysisDockerizationExample:of a DockerfileAdaptation to IBM POWER9 ArchitectureRecompilation for IBM POWER

15、9Stages of the Jenkins PipelineExample:Deployment in OpenShiftPod Deployment in OpenShiftYAML ManifiestsExample:Phase 3:Migrating ESB ServicesRe-architected services to function independentlyLeveraged OpenShifts CI/CD pipelinesCreated new integration developments as microservices On-Premise Arquitec

16、tureReference:https:/ ResultsScalable and Resilient Architecture:improvement in system uptime,reductionin downtime incidentsImproved Time to Market:Deployment times reduced from days to hoursEnhanced Performance:decrease in transaction processing timeCost reductionChallenges and SolutionsLack of Doc

17、umentation:-Conducted workshops and training sessionsComplex Integration Requirements:-Broke down integrations into manageable microservicesEnsuring Data Consistency:-Used advanced storage replication and backup strategiesNext ProjectsACS and ACM Implementation on IBM CloudPOWER Infraestructure ModernizationPlaying Calmly,but Walking FastThanks!