Talk about micro-service _ Architecture

Source: Internet
Author: User
Brief introduction

A micro-service architecture is an architectural model that advocates the division of a single application into a small set of services that are coordinated and mutually
Match. Each service runs in its own separate process, using lightweight communication mechanisms between services and services
Collaborate with each other (usually the restful API based on the HTTP protocol). Each service is built around a specific business and can be
Standalone deployment. In addition, for specific services, should be based on the business context, choose the appropriate language
Words, tools to build it. (The development pattern of many component combinations and the way of service construction)

Generally in the initial stage of the project, the use of monomer architecture will be more efficient, but as the project evolves, more and more areas to join, more and more complex functions, at this time if the use of micro-service architecture will be more appropriate. However, if you consider service splitting at this time, the schema migration will obviously cost much more than the initial use of the micro-service architecture. Characteristics of the micro-service API Gateway

Unify the gateway or go to the center to build, provide the client access interface. Service split

The rationality of service splitting will determine the service quality and even success (business split ability) of this architecture. Core business and Non-core business need to be demolished. Relatively independent business, and business change frequency difference is large, scaling demand differences, proposed dismantling service registration and discovery

Eureka, ribbon components in Zookeeper, Consul, spring Cloud. Communication mode

RESTful API, RPC, message based. Consistent and reliable event pattern

Based on event-driven architecture, when a domain object changes, it reaches the Subscriber by message and completes the related business operation. The focus of this model is to ensure reliable event delivery and avoid duplication of consumption. Business Compensation Model

The coordination service calls each of the micro services sequentially, and if a micro service invocation exception (including business exceptions and technical exceptions) cancels all previously invoked micro services. TCC Mode

A perfect version of the compensation pattern. A complete TCC model consists of one main business service and several from business services, the main business service initiates and completes the entire business activity, and the TCC mode requires three interfaces from the service: Try, Confirm, Cancel reliability

Current limit, isolation, service demotion, reasonable timeout, fuse (interface success rate) Other features

Deployment mode, security, unified configuration, monitoring, testing common micro-service framework

Spring Cloud

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.