Designing evolvable APIs
Another aspect of designing an evolutionary architecture is the proper design of the API. We cannot anticipate what changes may become necessary for an API. Message contracts that are used to communicate with an API may require modifications as a software system adapts to change. Some examples of the changes that can be made to an API include the amount of information that is sent or received, the names or data types of individual pieces of data, and the introduction of new representations of data to support different types of client.
Maintaining a system that can evolve requires that changes made to an API, particularly once it has been published, are given proper consideration. Your APIs should be designed to support ...
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