Minimizing Design Time Coupling in a Microservice Architecture

Delivering large, complex software rapidly, frequently and reliably requires a loosely coupled organization. DevOps teams should rarely need to communicate and coordinate in order to get work done. Conway's law states that an organization and the architecture that it develops mirror one another. Hence, a loosely coupled organization requires a loosely coupled architecture.  

In this presentation, you will learn about design-time coupling in a microservice architecture and why it's essential to minimize it. I describe how to design service APIs to reduce coupling. You will learn how to minimize design-time coupling by applying a version of the DRY principle. I describe how key microservices patterns potentially result in tight design time coupling and how to avoid it.


Chris Richardson

Creator of; Author of Microservices patterns & Java Champion
Chris Richardson is a developer and architect. He is a Java Champion, a JavaOne rock star and the author of POJOs in Action, which describes how to build enterprise Java applications with frameworks such as Spring and Hibernate. Chris was also the founder of the original, an... Read more Find Chris Richardson at:

Thursday May 20 / 11:10AM EDT (40 minutes)

TRACK Microservice - The First Decade TOPICS MicroservicesArchitecture ADD TO CALENDAR Calendar IconAdd to calendar

From the same track

View full Schedule