Implementing Adaptable Microservices

Implementing Adaptable Microservices

A Methodology for Loosely-Coupled Components

When pursuing a microservice approach, it’s not enough to design and build small components. The aim is to build a system that can adapt over time to changes in business needs and technology advancements without incurring high cost, risking system stability, or introducing added complexity and brittleness. If done right, the microservice model can not only deliver quality software but also reduce cost, improve stability, and increase implementation speed.

During this presentation, Mike Amundsen, Director of API Architecture, API Academy, looks at a handful of examples of microservice styles and focuses on a key aspect of they all share?providing system-level adaptability. Along the way we’ll review how lessons from DevOps IT is affecting software design, leveraging Conway’s law for teams and the Property→Constraint→Best Practice implementation pattern.

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.