Legacy system
A legacy system is an existing software or computing system that remains in use or must be maintained despite older technologies, designs, or constraints that can complicate change.
Google Anthos in Action
A legacy system is an existing application or technology that remains in use despite limitations from its age, design, or support model.
- How it is used
- Frames how to keep existing applications running while choosing incremental deployment, operational, and architectural improvements.
- How deep it goes
- Lays out an assessment-to-operation sequence and deployment alternatives, but does not detail each application’s refactoring implementation.
- Examples
- Uses a three-tier Java application on WebSphere or WebLogic and retained ERP or mainframe workloads to distinguish modernization paths.
- What you can do after
- Apply it via Migrate for Anthos when suitable, or select manual containerization, VM hosting, or retention for other workloads.
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
Legacy code is existing source code whose age, accumulated constraints, or structure makes it difficult to understand, modify, or replace.
- How it is used
- Frames modernization planning around persistent system constraints and the need for realistic, sustained investment.
- How deep it goes
- Examines architectural coupling, user-facing constraints, and organizational risks without providing code-level refactoring steps.
- Examples
- Illustrates a government website constrained by a legacy API and a case-entry limit enforced across an XML schema and databases.
- What you can do after
- Evaluate/understand it by tracing apparent UX problems to deeper dependencies and setting realistic modernization expectations.
Think Like a CTO
A software application built on older technology that remains in operation despite limitations in support, portability, or maintainability.
- How it is used
- Frames legacy systems as a technology-leadership priority that must be addressed without interrupting an established business.
- How deep it goes
- Explains operational risks and planning questions through scenarios, but stops short of a technical migration procedure.
- Examples
- Uses decades-old RPG and Cobol systems and Visual Basic applications dependent on unsupported libraries and older Windows versions.
- What you can do after
- Evaluate/understand it by checking business dependence, operational support, staffing, and risks before prioritizing modernization.
Learn Docker in a Month of Lunches, Second Edition
A legacy application is an existing software system built with older technologies or architectural assumptions and still relied upon for ongoing business operations.
- How it is used
- Replatforms older business-critical applications into Docker containers for consistent cloud deployment and management.
- How deep it goes
- Explains Windows-container replatforming and configuration adapters, while leaving framework-specific implementations open.
- Examples
- Uses .NET Framework XML configuration, a Java API, startup utilities, mounted override files, and Compose-managed secrets.
- What you can do after
- Operate/configure legacy applications in containers by translating file and environment overrides into their expected configuration format.
Read how Learn Docker in a Month of Lunches, Second Edition explains legacy system →
Related concepts
- strangler patternaddressed by · The strangler pattern is an incremental modernization approach that replaces a legacy system by gradually transferring its functionality to a new system until the legacy system can be retired.
- CTOaddressed by · A chief technology officer is an executive responsible for an organization’s technology direction, capabilities, and technical strategy.
- modernization initiativeused by · A modernization initiative is a planned effort to update existing software, technology, architecture, or organizational capabilities to meet current needs.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.