An existing system contains decisions visible in the code and others that emerge only in operation. Before replacing it, identify which behaviors support everyday work, which exceptions it handles and which information must not be lost.
Separate capability from implementation
Recording a payment, issuing a document and reconciling a transaction are business capabilities. A database or a library is a means of delivering them. This distinction makes it possible to discuss what needs to improve without making the replacement of a tool the project’s objective.
Choose a boundary that can be verified
Select a process whose behavior can be described and checked. Define inputs, outcomes, exceptions and responsibilities. If components will coexist, agree on which one is authoritative for each piece of data and how differences between results will be detected.
The Strangler Fig pattern describes gradual migration through a façade and highlights dependencies during coexistence [1]. It is an option to evaluate when requests can be intercepted, not a universal solution.
Prepare for recovery
Returning to the previous program does not always undo the data written by the new one. The strategy must account for compatibility, reconciliation and possible compensating actions. These actions depend on business rules and do not always restore the original state [2]. Test it before relying on it during an incident.
Use evidence to decide the next step
After each intervention, review the outcome and the cost of maintaining coexistence. Continuing, adjusting or stopping are valid decisions depending on what has been observed. Modernization makes sense when it improves a necessary capability at an acceptable cost and level of risk.
References
Read sourceSource recordAuthor notes: Adnan Khan, Ovais Mehboob Ahmed KhanReturn to text 1
Read sourceSource recordAuthor notes: MicrosoftReturn to text 1
Update history
Source-supported statements were clarified and standardized citations and references were added.