Mike Amundsen

Mike Amundsen

An internationally known author and speaker, Mike Amundsen travels the world discussing network architecture, Web development, and the intersection of technology and society. He works with companies large and small to help them capitalize on the opportunities provided by APIs, Microservices, and Digital Transformation.

Amundsen has authored numerous books and papers. He contributed to the O'Reilly book, "Continuous API Management" (2018). His "RESTful Web Clients", was published by O'Reilly in February 2017 and he co-authored "Microservice Architecture" (June 2016). His latest book -- "Design and Build Great APIs" -- for Pragmatic Publishing is scheduled for release in late 2019.

• http://amundsen.com
• http://github.com/mamund
• http://twitter.com/mamund
• http://linkedin.com/in/mamund

Proposed Talks

Below are some talk topics/ideas for this year's event.

HTTP, the Web, and REST for API Developers

Thinking Clearly about APIs

A short review of the open standards and common practices that have helped make the internet itself and the Web in particular a great place to build and publish APIs. And how we can apply the concept of "Cepration of Concerns" to clarify our thinking on all these things.

Links mentioned in the talks:

• Edsger W. Dijkstra
• RFC7540
• HTTP methods registered w/ the IANA
• WWW proposal by Tim Berners-Lee at CERN (1989)
• Architectural Styles and the Design of Network-based Software Architectures by Roy Fielding (2000)
• Slides

Hypermedia Patterns Featured-Talk

Code Patterns and Best Practices for Building Autonomous Clients

The speed of feature release for web and mobile apps continues to increase, but it can grow costly and time consuming to constantly rebuild and redeploy client applications—especially through app stores, where updates can take more than a week to appear. What if you could add new features to an existing client without repeatedly installing new versions of the application? What would the code look like? What changes are needed to create a client that can adapt to changes in the service API? How much change is reasonably possible when both the client and API are able to evolve over time?

An Introduction to Application-Level Profile Semantics (ALPS) Five-In-Five

This is a short straightforward into into ALPS and attempts to answer the questions: "What is ALPS? and why would someone want to use it?"

• InfoQ Article on ALPS by Mark Foster
• ALPS Draft Spec
• Slides (TBD)