Core micro-architecture services

Definition: Micro service is an architectural style, was first proposed by Martin in his blog post;
characteristics: 1. a set of small independent service 2. 3. lightweight process level communication protocols (ie http) 4. Based on the operational capacity 5. 6. no separate deployment of centralized management
challenges: 1. the complexity of distributed data consistency 2. 3. 4. test the complexity of the operation and maintenance complexity
Conway rule: the company's organizational structure should be consistent with the development of the system architecture so can improve the efficiency of research and development;
the applicability of the introduction of micro services: when the system is more complex, if a single system can lead to reduced productivity, so you can consider the introduction of micro services, according to the practice of a hundred people in the team can be used micro-service architecture; system is not recommended for new one up on the use of micro-service architecture, which involves investment in infrastructure, such as splitting services;
organize the introduction of micro service: when the micro-services architecture components cross-functional micro-services team, platform approach to the delivery;
Ali micro service desk strategy: including technology in Taiwan (IaaS, PaaS), business units (micro-service capabilities), business prospects;
service stratification : The industry has no uniform standard, some three to four points, and some not hierarchical; a relatively simple breakdown of hierarchical way: can be divided into two layers, the first layer is the basic service layer (core areas of service , public services, the service intermediate layer), aggregation service (service adaptation, the boundary service)
technology architecture: infrastructure, service platform, the service support, business service layer (micro-services), gateway layer and access layer;
service discovery mechanism: 1. the traditional load balancing, load balancing drawback is that this way is a single point, there is the performance overhead; 2. load balancing Daemonize integrated within the consumer, there is no single point of load balancing, but this approach is required depending on the language development
API service gateway and its main role include: reverse routing, security certification, current-limiting fuse, log monitoring