CN108924243A - Data distribution and processing method based on micro services framework - Google Patents

Abstract

The invention discloses a data distribution and processing method based on a micro-service architecture, the micro-service architecture includes a client for displaying a UI interface or a related service to a user, for providing a unified access to a client call, and for micro-service The service gateway implemented by the orchestration of the service instance, multiple independent microservice instances, the data layer supporting the related data of the microservice instance, and the third-party SPI interface; the method includes: receiving the same class from the client multiple data requests; distribute the data requests to multiple microservice instances for processing, and obtain processing results; forward the processing results to corresponding service components for further processing. After receiving the data request, this method will distribute the same type of data request to multiple microservice instances for processing. A problem with one service has no impact on the whole, avoiding that once a service has a problem under the traditional SOA architecture, it may cause the entire The problem of the collapse of the system.

Description

Data distribution and processing method based on microservice architecture

technical field

The invention belongs to the technical field of computers, and in particular relates to a data distribution and processing method based on a microservice architecture.

Background technique

Most of the current data distribution and processing processes use enterprise service bus technology to receive data requests and then call services for data processing or distribution. The overall architecture is based on the SOA architecture. In the SOA architecture, all requests must pass through the enterprise service bus, which will create a single point. The services invoked by the enterprise service bus are in the same application, interdependent and affecting each other. Once a service has a problem, it may cause the entire system to fail. Crash.

Contents of the invention

In order to solve the above-mentioned problems in the prior art, the present invention provides a data distribution and processing method based on a microservice architecture.

Technical scheme of the present invention is as follows:

A data distribution and processing method based on a microservice architecture, the microservice architecture includes a client for displaying a UI interface or related services to a user, for providing unified access for client calls, and for orchestrating microservice instances The implemented service gateway, a plurality of independent microservice instances, a data layer supporting relevant data of the microservice instances, and a third-party SPI interface; the method includes:

receiving multiple data requests of the same class from said client;

Distributing the data request to multiple microservice instances for processing, and obtaining processing results;

The processing result is forwarded to the corresponding service component for further processing.

Preferably, the service component includes an external system and a database.

Compared with the prior art, the technical solution provided by the present invention has the following beneficial effects or advantages:

The data distribution and processing method based on the micro-service architecture provided by the present invention, after receiving the data request, will distribute the same type of data request to multiple micro-service instances for processing, and each micro-service instance is independent and isolated from each other. A problem with a service has no impact on the whole, effectively avoiding the problem that once a service has a problem under the traditional SOA architecture, it may cause the collapse of the entire system; and in the present invention, the number of microservice instances can be expanded at any time according to the amount of requests, automatically For load balancing, it has strong scalability and high performance.

Description of drawings

Fig. 1 is a flow chart of the method of the embodiment of the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

Those skilled in the art can understand that, unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which this invention belongs. It should also be understood that terms, such as those defined in commonly used dictionaries, should be understood to have meanings consistent with the meanings in the context of the prior art, and will not be used in an idealized or overly formal sense unless specifically defined to explain.

First, the background technology of the present invention is introduced.

The current data distribution and processing process mostly adopts the technology of enterprise service bus, and enterprise service bus (Enterprise Service Bus, ESB) is the product of the combination of traditional middleware technology and XML, Web service and other technologies. ESB provides the most basic The connection center of the enterprise is a necessary element to build the nervous system of the enterprise.

The concept of ESB is developed from Service Oriented Architecture (SOA), and its overall architecture is based on SOA architecture. In the original SOA architecture, all requests have to go through the ESB, and the ESB can be imagined as a scaffolding that connects all enterprise-level services. Through service broker, it can convert different data formats or models into canonical format, convert XML input into CSV and send it to legacy services, convert SOAP 1.1 services into SOAP 1.2, etc. It can also route one service to another, and centralize business logic, rules, validation, and more. There may be complex dependencies between services.

Since the services invoked by the enterprise service bus are in the same application, they depend on each other and affect each other. Once a problem occurs in one service, it may lead to the collapse of the entire system.

In order to overcome the above problems, an embodiment of the present invention provides a data distribution and processing method based on a microservice architecture, the microservice architecture includes a client for displaying a UI interface or related services to the user, and a client for providing Invoke unified access and the service gateway implemented by the orchestration of the microservice instance, multiple independent microservice instances, the data layer supporting the relevant data of the microservice instance, and the third-party SPI interface; the method is shown in Figure 1 shown, including:

Step S1: receiving multiple data requests of the same type from the client;

Step S2: distributing the data request to multiple microservice instances for processing, and obtaining processing results;

Step S3: Forward the processing result to the corresponding service component for further processing.

In a specific implementation process, the clients in the microservice architecture in the embodiment of the present invention include APP, H5, WEB, and Internet of Things devices, etc., which are not limited here.

In the specific implementation process, after receiving multiple data requests of the same type from the client, they will be forwarded to the data service components in the application in the SOA architecture, and only one component can handle the same type of data requests, that is, In other words, the data requests can only be processed one by one in turn, which will lead to low data processing efficiency, and once a problem occurs in one service, the entire system may collapse. However, in the embodiment of the present invention, the data requests of each type are automatically forwarded to multiple service instances (service components) of the service, and multiple service instances are isolated from each other without interfering with each other, and each The service processing capabilities of each of the service instances are the same, and starting multiple service instances to process the data requests can greatly improve the processing capabilities of concurrent data requests.

In the specific implementation process, after completing the processing of the data request, there are three subsequent processing methods in the embodiment of the present invention, which can be sent to other systems through the third-party SPI interface, or stored in the database, or You can call other service instances for further processing.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems, or computer program products. Accordingly, the present invention can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and equivalent technologies thereof, the present invention also intends to include these modifications and variations.

Claims (2)

1. A data distribution and processing method based on a microservice architecture, characterized in that, the microservice architecture includes a client for displaying a UI interface or a related service to a user, for providing unified access to a client call and A service gateway realized by the orchestration of microservice instances, a plurality of independent microservice instances, a data layer supporting relevant data of the microservice instances, and a third-party SPI interface; the method includes: receiving multiple data requests of the same class from said client; Distributing the data request to multiple microservice instances for processing, and obtaining processing results; The processing result is forwarded to the corresponding service component for further processing. 2. The data distribution and processing method based on the microservice architecture according to claim 1, wherein the service components include external systems and databases.