Flower chanting white striped \ / channel service: [331,575,644], staging music withdrawal, XIN mention card seconds ,, to staging, ease flowers, wayward pay various threshold withdrawals, flower chanting, white bars \ / Service letter: [315756443] professional second back section quickly, the operation can be face to face, a remotely operable! Quick and simple payment process, operating without professional card to get a few minutes alone!
Basic micro Services Architecture (MSA) is to develop a single application for a group of small independent services, these independent service runs in its own process, separate development and deployment.
In most definitions of micro Services Architecture, which was interpreted as a whole in the services available for the isolation of a group of independent service process. However, in my opinion, not just to split the overall micro-services available in service as a separate service.
The key idea is that by looking at the overall functionality provided, we can determine the operational capacity required. Then, those business functions can be implemented as a fully independent, fine-grained and (micro) service self-contained. They may be implemented on top of a different technology stack, and each service for a very specific and limited business scope.
Therefore, we top online retail scene interpretation system can be achieved through micro-service architecture, as shown below. Is implemented as a set of services through micro-micro-services architecture, retail software applications. So, as you can see below it, according to business needs, there is an overall service is created from the original set of services as a whole exists. Thus, it is clear that the use of micro-services architecture is beyond the scope of the entire split service.
Micro Services Architecture
Let's delve into the key structural principles of the system of micro-services and, more importantly, let's focus on how to use them in practice.
Micro Design Services: The size, scope and functions
that you may be using Microservices Architecture software application built from scratch, or possibly existing applications / services to convert micro-services. Either way, the right to determine the size, scope and function of micro-services are very important. This is probably the most difficult thing when you first encountered the micro-service architecture to achieve in practice.
Let's discuss some of the key practical problems and misunderstandings size, scope and function of micro-related services.
· Line / size of the team is bad indicators: discussion on micro-scale service (ie two pizza teams) determined based on team size or line of code to achieve a lot. However, these indicators are considered very unrealistic and bad indicators, because we can still use less code / two pizza teams to develop services, but completely contrary to the principles of micro-services architecture.
· "Micro" is a misleading term: Most developers tend to think that they should try to make the service as small as possible. This is a misconception.
· SOA context: In the context of SOA, services are often implemented as a whole and supports dozens of operations / functions. Therefore, SOA has a similar service and renamed Micro Services does not give you any good micro-services architecture.
So, how should we properly design services in the micro-service architecture?