Tag Archives: legacy modernisation

Re-Legacy: The Debt of Deferred Structure

Cloud migration often preserves rather than eliminates legacy when structural redesign is deferred. Re-legacy occurs when outdated domain boundaries, embedded behavioural coupling, and implicit integrations are rehosted under modern infrastructure abstractions. This compounds structural debt, financialises complexity, and stabilises fragility under the banner of transformation. True modernisation requires deliberate structural intervention (redefining boundaries, clarifying state ownership, and reducing coupling) not merely upgrading the substrate.

Continue reading

Data Is a Symptom of Function: Migrating RDBMS Estates Is Not Transformation

Migrating legacy RDBMS estates to the cloud is often framed as a transformation, but relocating data rarely modernises systems. Data is a symptom of underlying business function, encoded behaviour, and dense integration. Without upstream redesign (defining capabilities, decomposing behaviour, clarifying boundaries, and extracting embedded logic) cloud migration preserves complexity, creating “re-legacy” at scale rather than true modernisation.

Continue reading