A legacy partner still requires nightly batch file drops while modern apps consume APIs. How should the architecture treat this situation?
Select an answer to reveal the explanation.
Short Explanation
During a remodel you still use the old porch door while the new front entrance goes in. Batch for a legacy partner and APIs for modern apps can live together—as long as both paths are inventoried, contracted, and governed.
Full Explanation
Multi-speed integration is common during modernization: legacy partners may retain batch exchanges while newer consumers use APIs. Architecture should plan coexistence with clear contracts, ownership, and retirement criteria rather than pretending only one style exists. Ungoverned parallel paths recreate point-to-point sprawl; governed coexistence enables orderly transition.