Two municipal teams plan to integrate a license-renewal service with a payments service. They intend to code both implementations first and “document the URLs later.” Which API-first correction should they make?
Select an answer to reveal the explanation.
Short Explanation
API-first is like agreeing on the permit form fields before either office builds its counter workflow. The contract is the integration surface. Coding first and documenting later hides coupling and breaks callers on every release.
Full Explanation
API-first design settles the contract early so implementations can evolve independently behind a stable interface. Code-first “document later” produces hidden coupling and release-time breakages. Merging into one binary, private in-process calls, and traffic scraping avoid the published-contract stance. Configuring API Gateway objects is a later-domain concern.