Cloud Application Architecture Patterns

Chapter 5. Microservice Design

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 5th chapter of the final book.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

When embarking on developing an application using a Microservices Architecture, it is important to understand how to best design the microservices that your application needs. Building a distributed architecture, such as a microservice architecture, has many challenges, and can be difficult to get right; specifically when dealing with possible failure points and dealing with distributed transactions.

When developing systems, it has been proven that designing, modeling, and building systems around the domain is a recipe for success. This is true regardless of the architectural style you are using. Understanding the requirements for a system and modeling the domain usually starts with a requirements-gathering phase to get a better understanding of the domain and the problem we are solving. Requirements gathering can elicit software requirements from various activities such as discussing user scenarios, creating user stories, looking at sequences of events for the ...