Many people talk about " microservices " and are grappling with an old problem more than 20 years ago ; Particle size "; What is the " granularity" of microservices partitioning ?
More than 20 years , many people are taking a " Standard answer " ; particle size Span style= "font-family: ' Helvetica Neue '"; In doing software development. Unfortunately, when you have been using the so-called " Standard answer in software development You are always using the so-called " wrong answer " The is doing software development.
How to identify " microservices "that can adapt to change, focusing not on what is " atom "? What is not " atom "? The real focus is to have methodology, practice from the following two facing to think, the depth of thinking ; Instead of just taking the surface of the definition of a hard sleeve ...
① If you've decided to use Docker to host your microservices, you need to understand the limits of how Docker is running. where's Docker's pit ? This information (knowledge) will be the input you need to design your microservices architecture.
② according to the external user's perspective, divide the " core business Span style= "font-family: ' Helvetica Neue '" > "bounded Context" . According to core business Span style= "font-family: ' Helvetica Neue '" > bounded Context with The schema constraint obtained by ① identifies " core business microservices .
In each PI , according to the core business micro-services in operations and external business changes, the continuous " Evolution " of more micro-services.
Software development is always a process of Evolution (learning) . Software development, never a standard answer ...
Therefore, software development even in the era of micro-services, it must be the continuous " Evolution " of the way , the depth of thinking , how to build a micro- service architecture ...
Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.
The first step in building microservices: Where does microservices come from?