| Concern | Weave Strategy | |---------|----------------| | | Legacy contracts are immutable; adapters handle transformation | | Resilience | Circuit breakers on calls to/from legacy | | Observability | Correlate trace IDs across greenfield and brownfield | | Deployment | Legacy deploys separately; integration tests ensure weave integrity | | Knowledge retention | Document “weave points” – every connection between old and new |

Traditional options— big bang rewrite or strangler pattern —often fail. Rewrites lose hidden logic; stranglers can leave isolated, unmaintained fragments. offers a third path: incremental, bidirectional integration where legacy components are actively preserved and connected, not just bypassed. 2. The Metaphor of Weaving | Weaving Term | Software Analogy | |--------------|------------------| | Warp (vertical, continuous) | The legacy application – long-lived, stable, foundational | | Weft (horizontal, interlacing) | New services, APIs, cloud functions – built iteratively | | Loom | Integration middleware / enterprise service bus / API gateway | | Selvedge (finished edge) | Stable public interfaces (APIs) of the new system | | Tension | Operational governance – balancing change vs. stability |

Author: [Your Name/Institution] Date: April 2026 Abstract Legacy applications are often viewed as technical debt—brittle, outdated, and costly. However, they frequently contain irreplaceable business logic, unique data relationships, and validated operational stability. This paper proposes a paradigm shift: instead of “rewriting or replacing,” organizations should adopt a weaving metaphor. By treating the legacy system as a warp thread—a continuous, foundational strand—modern services (microservices, APIs, event-driven components) act as weft threads, creating a new, resilient fabric. This paper outlines techniques, risks, and governance models for weaving legacy applications into contemporary architectures. 1. Introduction Legacy applications (mainframe COBOL, Visual Basic 6, early .NET/J2EE) still power core functions in finance, healthcare, logistics, and government. Estimates suggest over 70% of enterprise transactions touch a legacy system. Yet the pressure to modernize is intense: cloud migration, DevOps, and AI integration.