InfoQ Homepage Legacy Code Content on InfoQ
-
/articles/pipeline-language-migrations/en/smallimage/a-pipeline-approach-to-language-migrations-thumb-image-1759158012773.jpg)
A Pipeline Approach to Language Migrations
Automated language migrations can be made reliable and maintainable by structuring them as pipelines with clear, testable stages. This avoids the pitfalls of big-bang rewrites while providing transparency and modularity. The pipeline approach ensures idiomatic code, preserves legacy business logic, and supports large-scale transformations from outdated systems.
-
/articles/zero-downtime-cloud-upgrades/en/smallimage/zero-downtime-cloud-upgrades-thumbnail-1754398638654.jpg)
Zero-Downtime Critical Cloud Infrastructure Upgrades at Scale
Engineers can avoid common pitfalls in large-scale infrastructure upgrades by studying others' experiences. The article provides lessons learned from big firms like eBay and Snowflake, offering solutions for legacy systems, performance validation, and rollback planning. It emphasizes systematic preparation and clear communication to handle challenges and ensure zero-downtime upgrades at scale.
-
/articles/digital-banking-products/en/smallimage/digital-banking-products-thumbnail-1752561787405.jpg)
From Legacy to Value: Building Digital Banking Products across Central and Eastern Europe
This article shares practical experiences and concrete examples from multi-site teams that built a single solution and delivered value to customers across various European markets. It provides real-life stories and lessons learned from developing two banking products, Lending and Foreign Exchange (FX), and their evolving architecture over time.
-
/articles/AI-legacy-modernization/en/smallimage/AI-legacy-modernization-thumbnail-1746528855677.jpg)
AI Interventions to Reduce Cycle Time in Legacy Modernization
In this article, we share our experiences and insights on how large language models (LLMs) helped us uncover and enhance the conceptual constructs behind software. We discuss how these approaches address the inherent complexity of software engineering and improve the likelihood of success in large, complex software modernization projects.
-
/articles/architecting-real-time-systems-around-mainframe/en/smallimage/thumbnail-1745312950914.jpg)
Legacy Modernization: Architecting Real-Time Systems around a Mainframe
At its heart, our transformation journey is about breaking dependencies at multiple levels. Many enterprises face similar challenges with legacy systems: tightly coupled architectures that are difficult to scale, change, or maintain. For us at National Grid, the solution came through four complementary paradigms that worked together to enable different forms of decoupling.
-
/articles/fundamentals-of-transforming-legacy-architecture/en/smallimage/thumbnail-1745224504518.jpg)
Renovate to Innovate: Fundamentals of Transforming Legacy Architecture
Rashmi Venugopal explores the inevitability of legacy systems in successful companies and the importance of transforming legacy systems to accelerate innovation. Rashmi discusses various strategies to tackle such technical renovation initiatives, like evolutionary architecture, deprecation-driven development, and intentional organization design.
-
/articles/transforming-legacy-healthcare-systems/en/smallimage/transforming-legacy-healthcare-logo-small-1731055590401.jpg)
Transforming Legacy Healthcare Systems: a Journey to Cloud-Native Architecture
Discover how Livi navigated the complexities of transitioning MJog, a legacy healthcare system, to a cloud-native architecture, sharing valuable insights for successful tech modernization. Our experience illustrates that transitioning from legacy systems to cloud-based microservices is not a one-time project, but an ongoing journey.
-
/articles/moldable-development/en/smallimage/logo-1663947983331.jpg)
Moldable Development: Guiding Technical Decisions without Reading Code
Developers spend most of their time reading code. Moldable Development challenges reading as a means to gather information from the system, by creating custom tools that show the problem in a way that makes it comfortable to understand. The solution typically follows quickly afterward. Glamorous Toolkit is a moldable development environment designed to decrease the cost of custom tools.
-
/articles/mvp-mva-legacy/en/smallimage/logo-1660735098327.jpg)
Chipping Away at the Monolith: Applying MVPs and MVAs to Legacy Applications
Legacy applications actually benefit the most from concepts like a Minimum Viable Product (MVP) and its related Minimum Viable Architecture (MVA). Once you realize that every release is an experiment in value in which the release either improves the value that customers experience or doesn’t, you realize that every release, even one of a legacy application, can be thought of in terms of an MVP.
-
/articles/communicating-engineering-work-business/en/smallimage/logo-1643971643396.jpg)
Talking Like a Suit - Communicating the Importance of Engineering Work in Business Terms
This article explores how to construct engineering work as a story, including clearly presenting a problem, offering a solution, and showing the business a path to success that solves their problem and avoids failure. By presenting your case in this way, you significantly increase your chances of getting these engineering problems addressed, while also becoming a better partner for the business.
-
/articles/upgrading-legacy-solutions/en/smallimage/5-things-to-remember-when-upgrading-your-legacy-solution-small-1636369934577.jpg)
Five Things to Remember When Upgrading Your Legacy Solution
Legacy software is still employed, even though it frequently fails to meet critical demands and core business operations. By choosing the right modernization strategy and software development teams, you can easily cut down on high legacy software maintenance costs and increase productivity.
-
/articles/series-debt-guide-agile-journey-2/en/smallimage/Technical Debt-s-1623850162647.jpg)
‘Debt’ as a Guide on the Agile Journey: Technical Debt
In this article in a series on how ‘debt’ can be used to guide an agile journey, we will provide two examples of smells that are related to technical debt, explain the symptoms, the impact on the business and in our organization, outline the experiments (countermeasures) that we have introduced in an effort to try to remove the smell, and provide some specific advice for you to be inspired.