EXPLORE THE TAG
Modernising legacy systems without a risky rewrite: the strangler fig pattern for replacing capabilities behind a routing layer, a reference architecture for adding an LLM beside a legacy core, and a staged sequence from inventory and read-only pilot to shadow mode and write-back.
Showing · #Legacy Modernization
The strangler fig pattern replaces a legacy system one capability at a time behind a routing layer. Here's how to choose the first slice, give every data set one owner during the transition, and plan each cutover and its recovery path.
Adding an LLM to a legacy application is mostly a boundary problem: where the model runs, whose identity it uses, which tools it may call and how changes reach your records. This reference architecture makes each boundary explicit.
Add an LLM to a legacy system in controlled stages: inventory touchpoints and data owners, pilot a read-only feature, run it in shadow mode, widen a routed rollout with rollback ready, and add write-back last.
