\nEnterprises have lots of legacy code running critical systems.\u00a0 And legacy code comes with its challenges.<\/p>\n
1.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Monolithic architecture \u2013 This makes maintenance extremely difficult.\u00a0 Fixing bugs, and enhancements is highly time-consuming and error-prone.<\/p>\n
2.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Scalability challenges – Legacy code cannot benefit from the advantages of horizontal scaling provided by cloud providers.\u00a0 As there is a limit to vertical scaling, the legacy code has a limit to the number of users\/load that it can support<\/p>\n
3.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Non-availability of SMEs \u2013 SMEs who understand the legacy code are in short supply<\/p>\n
4.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Non-availability of documentation – This makes the transition to new teams impossible<\/p>\n
The aforesaid problems are the prime reasons for Modernization<\/p>\n
<\/p>\n
The traditional way of modernization<\/strong><\/p>\n There have been two approaches to modernization.<\/p>\n 1.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 AS-IS Migration – The legacy code is converted syntactically to the modern language.\u00a0 There are tools available to do this automatically to a large extent.\u00a0 But this is only a quick and dirty approach to modernization.\u00a0 Even though the code is written in modern language, the architecture is still old.\u00a0 It does not give one the benefit of OOPS, microservices, micro front end, etc.\u00a0 Therefore scalability is still an issue with this approach<\/p>\n 2.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Smart Migration – To alleviate the problems of As-Is Migration, Smart Migration is desired.<\/p>\n <\/p>\n The classic approach to modernization is below.<\/p>\n a)\u00a0 \u00a0 \u00a0 \u00a0Legacy code SMEs to analyze the legacy code, and manually extract the list of entities, business rules, and interdependencies<\/p>\n b)\u00a0\u00a0\u00a0\u00a0\u00a0 Validate with the business users.<\/p>\n c)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Modern code SMEs to take the list of entities and business rules extracted in step#1, and create new generation code in modern architecture using OOPS, Microservices, Microfront end screens, NoSQL DBs and the like<\/p>\n Step #2a is extremely time-consuming and error-prone.\u00a0 This has a dependency on the skill level of the Legacy Code SMEs.\u00a0 Thus, the process is slow and buggy.<\/p>\n Similarly, Step #2c is once again time-consuming as code must be written from scratch.<\/p>\n <\/p>\n It is here that Infosys has created a modernization methodology based on Google Generative AI to cut down on step #2a and step #2c.<\/p>\n The Infosys Modernization methodology based on Google Generative AI<\/p>\n <\/p>\n The Infosys Modernization methodology uses Google Generative AI for the below steps:<\/p>\n 1.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 To automatically extract Entities, Rules, and User stories from Legacy Code<\/p>\n 2.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Extracted information is vetted by an SME.\u00a0 SME reviews, and updates the items extracted in #1<\/p>\n 3.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 To automatically generate modern code based on the entities, rules, and user stories reviewed in #2<\/p>\n 4.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Modern code SMEs, can review, and edit the newly generated code and baseline the same<\/p>\n <\/p>\n Conclusion<\/strong> Abstract:\u00a0 Legacy code is typically slow and difficult to maintain.\u00a0 Enterprises are always looking […]<\/p>\n","protected":false},"author":512,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[4],"tags":[],"coauthors":[188],"class_list":["post-1932","post","type-post","status-publish","format-standard","hentry","category-artificial-intelligence"],"acf":[],"_links":{"self":[{"href":"https:\/\/blogs.infosys.com\/emerging-technology-solutions\/wp-json\/wp\/v2\/posts\/1932","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.infosys.com\/emerging-technology-solutions\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.infosys.com\/emerging-technology-solutions\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.infosys.com\/emerging-technology-solutions\/wp-json\/wp\/v2\/users\/512"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.infosys.com\/emerging-technology-solutions\/wp-json\/wp\/v2\/comments?post=1932"}],"version-history":[{"count":8,"href":"https:\/\/blogs.infosys.com\/emerging-technology-solutions\/wp-json\/wp\/v2\/posts\/1932\/revisions"}],"predecessor-version":[{"id":1948,"href":"https:\/\/blogs.infosys.com\/emerging-technology-solutions\/wp-json\/wp\/v2\/posts\/1932\/revisions\/1948"}],"wp:attachment":[{"href":"https:\/\/blogs.infosys.com\/emerging-technology-solutions\/wp-json\/wp\/v2\/media?parent=1932"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.infosys.com\/emerging-technology-solutions\/wp-json\/wp\/v2\/categories?post=1932"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.infosys.com\/emerging-technology-solutions\/wp-json\/wp\/v2\/tags?post=1932"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.infosys.com\/emerging-technology-solutions\/wp-json\/wp\/v2\/coauthors?post=1932"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"Migration](\"https:\/\/blogs.infosys.com\/emerging-technology-solutions\/core\/uploads\/2023\/08\/Pic-for-migration-1024x577.png\")
\nThe SME effort involved in extracting entities and business rules from legacy code has been drastically reduced.\u00a0 Similarly, the effort involved in creating modernized code is reduced considerably.\u00a0 Overall, this methodology has slashed the manual effort in the range of 50%-70%.<\/p>\n","protected":false},"excerpt":{"rendered":"