A modernization team must expose a COBOL business service to cloud consumers with minimal rewrite. Which pattern best fits scenario 1?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Here's the deal — wrap first, rewrite later. An API façade lets cloud apps call proven mainframe logic while you modernize in slices.
Full explanation below image
Full Explanation
Incremental modernization commonly uses an API façade over existing COBOL/CICS services so consumers get modern interfaces without a risky big-bang rewrite. Overnight rewrites without tests are high risk. Email is not source control. Disabling logging harms operability. Teams should add automated tests, observability, and strangler patterns around the façade.