Creating More Resilient Systems: an Introduction to Affordances -- Interview with Micheal Hibay, pt 1

API Resilience

Michael Hibay is an API evangelist, architect and CTO at Vesti. He helps organizations to establish, evolve and mature their API strategies.

What’s the difference between an API catalogue and an affordance catalogue? What are affordances and how do they define the usability of a system? Why are affordances similar to languages?

The interview got split into 2 episodes. In this first episode, Michael argued that versionless APIs built through an affordance approach, introduce new capabilities without causing breaking changes. An affordance approach in API design also saves money by avoiding the need for new iterations and API versions.

The host is Kristof Van Tomme.