<<< Previous speaker next speaker >>>

Mike Amundsen, Principal API Architect for Layer 7 Technologies

 Mike  Amundsen
As Principal API Architect for Layer 7 Technologies, Mike Amundsen’s job is to help people build great APIs for the Web. An internationally known author and lecturer, Mike travels throughout the United States and Europe consulting and speaking on a wide range of topics including distributed network architecture, Web application development, Cloud computing, and other subjects. His recent work focuses on the role hypermedia plays in creating and maintaining applications that can successfully evolve over time. He has more than a dozen books to his credit. His most recent book is "Building Hypermedia APIs with HTML5 and Node" He also contributed to the book "RESTful Web Services Cookbook" (by Subbu Allamaraju) and is currently working on a new book on programming with the Cloud9 IDE. When he is not working, Mike enjoys spending time with his family in Kentucky, USA.

Presentation: "Real-Life Stories on Building Hypermedia APIs"

Time: Wednesday 14:40 - 15:30

Location: Seacliff AB

As interest in "Web APIs" continues to rise, it’s important to know the advantages and downsides of various implementation strategies. The most common style for “Web APIs” today is based on identifying entities using URIs and applying CRUD operations against those URIs via HTTP methods. In this session, we'll explore an alternate approach to implementing APIs, based on designing messages instead of URIs and using in-message affordances (links and forms) instead of direct protocol methods.This talk provides a working definition for Hypermedia Types, identifies the H-Factors that can appear in any hypermedia type, and the four design elements used in authoring hypermedia types. The talk includes multiple working examples of hypermedia APIs. Additional topics include documenting hypermedia, extending & versioning, and registering designs for wider use on the Web. Along the way, attendees will see illustrations of implementation experience “inthe wild” along with commentary on the inherent costs and potential benefits of adopting a hypermedia style for APIs.