November 2, 2019

265 words 2 mins read

12 patterns for hypermedia service architecture

12 patterns for hypermedia service architecture

Mike Amundsen offers 12 patterns and practices for building APIs that can safely evolve over time and client applications that can adapt to those changes without relying on explicit versioning systems or repeated redeployment.

Talk Title 12 patterns for hypermedia service architecture
Speakers Mike Amundsen (Amundsen.com, Inc.)
Conference O’Reilly Software Architecture Conference
Conf Tag Engineering the Future of Software
Location New York, New York
Date April 11-13, 2016
URL Talk Page
Slides Talk Slides
Video

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? Mike Amundsen offers 12 patterns and practices for building APIs that can safely evolve over time and client applications that can adapt to those changes without relying on explicit versioning systems or repeated redeployment. Whether you are responsible for building web frontends or APIs to serve those apps, Mike helps you identify key principles to increase the adaptability and evolvability of your web implementations. OFFICE HOURS Mike will take part in Office Hours on Tuesday, April 12 at 12:15 PM in the Mercury Complex. Come by and meet him!

comments powered by Disqus