Hyrum's Law and API Design and Management | What does it mean?

blog.axway.com · 542 words · saved by 1 readers

This article discusses Hyrum's Law and what it means for API Design and Management. Hyrum's Law is named after Google software engineer Hyrum Wright.

The promise and challenges of loose coupling One of the main aspects of APIs is that they should provide loose coupling , meaning that providers and consumers of services have more independence and autonomy to evolve than in more tightly coupled approaches. The obvious advantage of this is that it requires less time-consuming coordination, and thus providers and consumers can evolve independently. However, when providers and consumers can evolve independently, there always is the risk of breaking changes . If an API changes, do existing API consumers have to adapt and change? Or can they keep

Hyrum's Law and API Design and Management | What does it mean?

related reading