A waste-collection routing API adds a new optional ETA field for newer mobile clients but also renames a required stop-id field that older kiosk clients still send. Which evolution practice keeps independent deployability real?
Select an answer to reveal the explanation.
Short Explanation
Contracts are like bus route numbers posted around town: adding a new optional stop sign is usually fine, but renaming the route overnight strands last year’s maps. Backward-compatible evolution keeps independent deployability real. Breaking renames need deliberate versioning.
Full Explanation
Independent deployability depends on evolving published interfaces without stranding older callers. Additive optional fields are typically safe; renaming or removing required fields is a breaking change that needs a versioning strategy. Lockstep caller deploys or nightly contract deletion recreate coordinated releases. API Gateway deployment objects are Domain 3 concerns.