Thankfully, we completed the transition for this client within the six-month timeframe. Our client is now better positioned to make changes to its business processes that will drive speed to market. It also expects to achieve major benefits in terms of greater performance that will drive better user experience and more efficiency, which will improve IT staff and user experience.
The company does not yet have a clear picture of the exact cost benefits of its move to AWS, but it expects the cost reductions in the range of 25% annually over the IPaaS solution. And the company is already seeing a 25% to 30% reduction in the time needed to make system changes.
Historically, a company like this would migrate service by service at the experience layer, process layer and system layer. But that can be problematic. In our experience, almost one-third of endpoints are typically deprecated (no one uses them), but they are still present. Taking a service-by-service migration approach would mean moving endpoints that are defunct, wasting a lot of time (and therefore money).
Focus on use cases for migration
A better way is to migrate use case by use case. Use cases might range from such operational functions as “onboard new customer” to those related to the core business, such as “list all retail companies over $1 billion in revenues” or “list the top executives of XYZ company.” Focusing on use cases is much more efficient than migrating services because if there is a function that is not used in any of the use cases, then it will not be migrated to the new system.
This method, we have found, helps identify which endpoint is being used. An additional advantage: Migrated services cannot be tested in isolation, whereas migrated use cases can. This approach enables faster yet, at the same time, more gradual adoption of the new API delivery platform.
While hyper-scalers provide API delivery tools and tackles, they do not offer the ways and means for migrating integration flows from IPaaS platforms to their cloud environments. Moreover, the phased release of migrated endpoints enables migration challenges to be mitigated more manageably. This is in keeping with a “fail-fast” design philosophy of today’s minimum viable product (MVP) movement, which is critical in a time-sensitive modernization project. (Here’s a deeper dive into the technical aspects of the migration and our partnership with AWS.)
Smooth pathway from IPaaS to IaaS
Our work with this client reveals how a use case migration approach enables a smooth pathway from IPaaS to IaaS. In fact, we learned that this novel approach can be applied easily to companies across industry segments that are seeking to decrease IT operational costs and speed time to value of new business capabilities via an IPaaS to hyper-scaler cloud migration, regardless of the platforms involved.
This article was written by Dipanjan Sengupta, a Senior Director in Cognizant’s Digital Engineering Practice.
For additional insights, visit the Digital Engineering section of our website or contact us.