To Create An Evolvable API, Stop Thinking About URLs
The basics of API design
If you’re spending your time discussing if URLs should be in the singular
/restaurant/:idor plural/restaurants/:id, then that means you’re not creating evolvable APIs... The server may ask for all the fields in the first request, or they may acknowledge some fields and ask for the remaining ones in another request. The most important bit here is that the server responds to each interaction with the same interface.
.. This way you have no coupling between one specific URL and the response. One team can develop the client, and another team can develop the server; they only need to agree on the communication format. There’s no need to deploy both client and server at the same time in a specific order!
In Domain Driven Design, you model the architecture of the code with how the people from your business operate. With an evolvable API, it’s the same. You model the asynchronous communication between machines exactly how people in your business communicate.