Shulou(Shulou.com)06/02 Report--

This article mainly explains "what is the difference between SOA architecture and micro-service architecture". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what is the difference between SOA architecture and micro-service architecture".

The difference between SOA architecture and micro-service architecture

First of all, there is a level of SOA and micro-services architecture, while for ESB and micro-services gateways, one is about architectural styles and methods, and the other is about implementing tools or components.

1.SOA (Service Oriented Architecture) "Service-oriented Architecture": it is a design approach that consists of multiple services that ultimately provide a series of functions through interdependence. A service usually exists in an operating system process in an independent form. Each service is called through the network.

two。 Micro-service architecture: in fact, similar to SOA architecture, micro-service is the sublimation of SOA. One of the key points of micro-service architecture is that "business needs to be thoroughly componentized and serviced". The original single business system will be split into multiple mini applications that can be developed, designed and run independently. These small applications interact and integrate with each other through services.

Micro service architecture = Meituan real time logistics distributed system architecture design 80% SOA service architecture idea + 100% component architecture idea + 80% domain modeling idea ESB and micro service API gateway.

1.ESB (Enterprise Service bus): to put it simply, ESB is a pipe that connects each service node. In order to integrate services of different systems and protocols, ESB does the work of message translation, interpretation and routing, so that different services can be interconnected.

2.API Gateway: the API Gateway is a server and the only entry to the system. From the perspective of object-oriented design, it is similar to the appearance pattern.

The API gateway encapsulates the internal architecture of the system and provides a customized API for each client. It may also have other responsibilities, such as authentication, monitoring, load balancing, caching, request fragmentation and management, and static response processing. Why do microservices have to have gateways? I recommend you to read this one.

The core point of the API gateway approach is that all clients and consumers access micro-services through a unified gateway and handle all non-business functions at the gateway layer. Typically, the gateway is also an access API that provides REST/HTTP. The server registers and manages the service through API-GW.

Features of 3.SOA architecture

System integration: from a system point of view, solve the communication problems between enterprise systems, and sort out the original scattered and unplanned network structure into a regular and manageable star structure between systems. this step often requires the introduction of some products, such as ESB, technical specifications and service management specifications; the core problem solved in this step is [order]

The service of the system: from the point of view of function, the business logic is abstracted into reusable and assembled services, and the rapid business regeneration is realized through the choreography of services. purpose: to transform the original inherent business functions into general business services, to achieve rapid reuse of business logic; the core problem solved in this step is [reuse]

Service-oriented business: from the point of view of the enterprise, abstract enterprise functions into reusable and assembled services; transform the original functional enterprise architecture into service-oriented enterprise architecture to further enhance the external service capability of enterprises; "the first two steps are to solve the problems of system call and system function reuse from the technical level." The third step is to encapsulate a business unit into a service with a business driver. The core problem solved in this step is [efficiency]

Features of microservice architecture 1. Implement componentization through services

Developers no longer need to coordinate the impact of other service deployments on this service.

two。 Divide service and development teams by business capability

Developers are free to choose development technologies and provide API services

3. Decentralization

Each microservice has its own private database to persist business data.

Each microservice can only access its own database, but not the databases of other services.

In some business scenarios, multiple databases need to be updated in a single transaction. In this case, it is not possible to directly access the databases of other micro-services, but through the operation of micro-services.

The decentralization of data further reduces the coupling between microservices, and different services can adopt different database technologies (SQL, NoSQL, etc.). In complex business scenarios, if multiple micro-services are included, they are usually handled on the client or in the middle tier (gateway).

4. Infrastructure automation (devops, automated deployment)

Java EE deployment architecture packages WARs through the presentation layer, divides the business layer into JARs and finally deploys it into a large package of EAR, while micro services open this black box and split the application into a single service. It applies Docker technology, does not rely on any server and data model, and is a full-stack application that can be deployed independently through automation.

Each service runs in its own process and is contacted through lightweight communication mechanisms, often based on HTTP resource API. These services are built on business capabilities and can be managed centrally (because there are too many services, it is impossible to DevOps without centralized management).

5. Main differences: thank you for reading, the above is the content of "what is the difference between SOA architecture and micro-service architecture". After the study of this article, I believe you have a deeper understanding of what is the difference between SOA architecture and micro-service architecture. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.