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.
Mike will take part in Office Hours on Tuesday, April 12 at 12:15 PM in the Mercury Complex. Come by and meet him!
Mike Amundsen is an internationally known author and speaker who travels the world discussing network architecture, web development, and the intersection of technology and society. He’s helped companies large and small capitalize on the opportunities provided by APIs, microservices, and digital transformation. He’s authored numerous books and papers and contributed to the O’Reilly book Continuous API Management. He’s the author of RESTful Web Clients and coauthor of Microservice Architecture. His latest book is Design and Build Great APIs (Pragmatic Publishing).
©2016, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org