The city’s license API must introduce a breaking change to the permit payload. Independently deployed mobile and kiosk clients still call the current contract. What is the sound migration approach?
Select an answer to reveal the explanation.
Short Explanation
Think of renaming a street while people still have the old address on their mail. You post the new street name but keep delivering to the old one until everyone updates—then retire the old route.
Full Explanation
Breaking changes punish independently deployed consumers if applied in place. Publish a parallel contract (new path or major version) and keep the prior version available until callers move. Surprise in-place breaks defeat the independent-deployability microservices promise.