The client is a leading US digital financial services company offering financial products for consumers, businesses, automotive, and corporate clients.
Infosys is working with this client for close to 10 years now, in various business functions including account opening, retail online banking, mortgage in areas of solution design, development and testing engagements for major new development, migration, and multiple channel enablement for the various features they offer. In the latest engagement, Infosys joined hands with this client to re-architect and migrate approximately 200 APIs into microservices.
Key Challenges
- Separation of concern so that individual business functions can move independently without impacting others or being tied down to a traditional release window
- Independence from product/vendor lockdown, reduction of high licensing costs
- Optimal use of infrastructure by making it available on demand and being able to scale resources by functionality and load
Ready to experience?
TALK TO EXPERTS
The Solution
The Infosys Methodology
- Business capability-based microservices which are autonomous, modular, testable, and decoupled. Services grouped as ‘capabilities’ based on the business functionality they support
- Source repository, static and dynamic code scans, and build pipelines integrated and automated for seamless operation
- Red Hat OpenShift Platform-based solution for on-demand scaling, automated monitoring, and container management. Effective use of Red Hat OpenShift features for health monitoring, fault recovery, and auto scaling of pods based on demand
Building an Integrated Foundation Approach
- CICD pipeline with automated tests for reducing cycle time
- Automated tests using SoapUI being integrated into the Jenkins pipeline
- Roadmap for automating the release all the way to production being prepared
Benefits
De-coupled and manageable architecture with 210 microservices grouped into 33 independent business capabilities which are independently deployable and scalable
Agility and Faster Time-To-Market with release frequency increased from once a quarter to up to twice a week
This has reduced production release timeline from over 6 hours to under 30 minutes
Creating a Scalable and resilient operation with optimal use of resources with automated scaling-up and down as necessary
This has also helped enhance capabilities to monitor and resolve customer issues, with no downtime issues and reduction in risk
