微服务现在很火，但是怎样才能建设合适自己的微服务架构呢，这篇文章进行了很好的实践也给了实用的建议。
Key Takeaways
Microservices are not a panacea; they have their place in modern architecture, but just not any place.
Understanding the business domain is vital for assessing whether a microservices-based architecture is an adequate choice.
The Single Responsibility Principle is key to delineating the functional boundary of microservices.
Like any other architectural style, Microservices are governed by a set of tenets. It is important to understand how any deviation from these affects a given technology solution.
Microservices must be considered within the broader contexts of distributed architecture and distributed computing.
文章主要内容：
In this article we examine the potential architectural fitness of microservices in the context of Master Data Management (MDM), and the challenges a microservices-based architecture may face when solving problem domains that require compute-intensive tasks, such as the calculation of expected losses on a portfolio of unsecured consumer credit.
We will begin by introducing a meta-model for business architecture, and use its elements and their relationships to define both business and problem domains. We will then introduce the Domain-Driven Design approach as a means to apprehend complex business domains, and assist with the creation of technology solutions.
Microservices, a new architectural paradigm, will then be presented, their anatomy described, and their benefits and drawbacks briefly articulated. The possible fitness of microservices to implement an MDM Data Hub will then be presented for consideration.
Finally, we will explore the limited conditions where microservices-based architectures may or may not be suitable for computation intensive applications involving large volumes of data.
一些有意思的图：
Business Architecture Meta-Model：
Domain-Driven Design and Microservices – Conceptual View:
Anatomy of a Microservice：
文章很长，具体大家可以看原文：
https://www.infoq.com/articles/Microservices-Architectural-Fitness
