Web API Design Maturity Model
This was an informal/draft talk on establishing a maturity model for API interface design models. It outlines four levels of design, each providing a greater degree of de-coupling from service internals and, therefore, more abstraction). The four levels are:
Data Model as the API
Object Model as the API
Resource Model as the API
Affordance Model as the API
The takeaway from this talk:
"Your data model is not your object model is not your resource model is not your affordance model."
Speaker : Mike Amundsen
Director of API Architecture, API Academy, CA Technologies
An internationally known author and lecturer, Mike Amundsen travels throughout the world consulting and speaking on a wide range of topics including distributed network architecture, Web application development, and other subjects.
In his role of Director of Architecture for the API Academy, Amundsen heads up the API Architecture and Design Practice in North America. He is responsible for working with companies to provide insight on how best to capitalize on the myriad opportunities APIs present to both consumers and the enterprise.
Amundsen has authored numerous books and papers on programming over the last 15 years. His last book was a collaboration with Leonard Richardson titled "RESTful Web APIs" published in 2013. His 2011 book, “Building Hypermedia APIs with HTML5 and Node”, is an oft-cited reference on building adaptable Web applications. He is currently working to complete a new book - "RESTful Web clients" due out from O’Reilly in summer 2016.