Change-resilient APIs

There are certain principles in designing interfaces that prevent unnecessary breaks. For example, introducing new, optional payload data should not break the contract. Technology should be resilient as far as it can continue to work if all necessary data is provided. This matches the idea of being conservative in what you do and liberal in what you accept.

Therefore adding new, optional functionality or data should be possible without breaking clients. But what if existing logic changes?

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.128.198.59