The county ERP that issues purchase orders cannot be rewritten in one release, but finance needs a new vendor-onboarding API this quarter. Which incremental modernization path should architects identify?
Select an answer to reveal the explanation.
Short Explanation
You don't demolish city hall to add a new service window. Put a Lambda or API in front, strangle off one feature at a time, and leave the old ERP running. Big-bang rewrites are how finance waits years for a form.
Full Explanation
Incremental modernization uses a strangler-fig pattern: new features such as vendor onboarding sit on AWS Lambda or containers and APIs in front of the legacy ERP, routing selected traffic to the new path while the remainder stays on the old system. That avoids a single cutover and public exposure of the ERP database. Freezes and holiday big-bang rewrites delay value and increase risk.