Extend Your APIs Safely
So far, we’ve strongly advocated building many small components and managing those components through dependencies. When this strategy is working well, it simplifies your job by limiting the scope of what you need to understand to make any given change.
This strategy can go to a special hell fueled by cascading dependencies in a hurry, if you’re not careful with how you build your APIs. Specifically, maintaining a healthy ecosystem is difficult if each release of an API breaks compatibility to old versions of the API. Breaking changes have several different forms:
-
An API can add requirements to input parameters such as adding a new required field to our Quiz.
-
An API can change the shape of the output such as changing ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access