Preface

Microservice architecture has emerged as a common pattern of software develop‐

ment from the practices of a number of leading organizations. These practices
includes principles, technologies, methodologies, organizational tendencies, and cul‐
tural characteristics. Companies taking steps to implement microservices and reap
their benefits need to consider this broad scope.

Who Should Read This Book

You should read this book if you are interested in the architectural, organizational,
and cultural changes that are needed to succeed with a microservice architecture. We
primarily wrote this book for technology leaders and software architects who want to
shift their organizations toward the microservices style of application development.
You don’t have to be a CTO or enterprise architect to enjoy this book, but we’ve writ‐
ten our guidance under the assumption that you are able to influence the organiza‐
tional design, technology platform, and software architecture at your company.

What’s In This Book

This book promotes a goal-oriented, design-based approach to microservice architec‐
ture. We offer this design-centric approach because, as we talked to several companies
about their programs, we discovered one of the keys to their success was the willing‐
ness to not stick to a single tool or process as they attempted to increase their compa‐
ny’s time-to-market while maintaining—even increasing—their systems’ safety and
resilience.
The companies we talked to offered a wide range of services including live video and
audio streaming service, foundation-level virtual services in the cloud, and support
for classic brick-and-mortar operations. While these companies’ products vary, we
learned that the principles of speed and safety “at scale” were a common thread. They

xi