Multilingual cloud compilation-based dynamic micro-service calling method and apparatus

Abstract

The invention provides a multilingual cloud compilation-based dynamic micro-service calling method and apparatus. After a preset server receives a call request of calling a first micro-service, a corresponding first micro-service instance is searched for in the preset server and runs, or a first script code corresponding to the corresponding first micro-service is searched for in a micro-service script warehouse, the first micro-service instance runs after the first script code is compiled to form the first micro-service instance, and a running result is fed back to a terminal. Therefore, the problem in the condition that the server still can execute a preset task to ensure normal running of a business system when the business system is upgraded or has a fault is solved, and the flexibility, openness, maintainability and expandability of system function expansion are effectively improved.

Description

technical field [0001] The invention belongs to the field of computer technology, and in particular relates to a method and device for invoking dynamic microservices compiled by multi-language cloud. Background technique [0002] With the emergence of object-oriented design patterns and enterprise architecture patterns, a system is usually divided into three levels from the perspective of function realization and code organization: presentation layer, business logic layer, and data access layer. The presentation layer is based on Html Web The page is rendered by fetching data through RestAPI; the business logic layer is the core code of the application system, which is usually used to implement system business rules; the data access layer is the intermediary for accessing databases or information; this is a common classic three-tier architecture pattern, which Although this model solves the problem of complex calls between system modules and unclear responsibilities to a cer...

AI Technical Summary

Problems solved by technology

[0004] There are the following disadvantages in the comprehensive existing technology: (1) The expansion is complicated: all the codes are in one project system, which makes the whole expansion process very complicated and cumbersome, and may destroy the structure of the original code; (2) The code reuse rate is low: The system code logic is only for the current development and coupled to the system, which reduces the code reuse rate;

(3) Long development cycle and low efficiency: When expanding or adding new requirements, developers need to re-develop, compile, test, upload, configure, package, and deploy the system offline, which makes the development cycle very long and inefficient

(4) Difficult to maintain: System developers and technology applications may have been iterated countless times, and the mutual calls and mutual coupling between codes in the system are also intricate. People who do not know the system well dare not act rashly

With more and more requirements and functions of the system, the team is getting bigger and bigger, and the corresponding communication costs, development costs, and management costs will increase exponentially. When the system has defects, it will also cause analysis problems, positioning problems, and repair problems The time is longer; as the amount of code increases, it may also lead to a vicious cycle of "more fixes, more defects"; a small change in the system requires redeployment of the entire application system

(5) Development language limitations: If the application system is developed in a certain language, it must be extended with this language when it needs to be expanded again, and it is impossible to try a new programming language or framework, which is currently impossible to use in reality. Technology platform or solution to solve all problems

(6) High hardware cost and difficult horizontal expansion: All program codes are in the same process of the server, which will lead to difficult horizontal expansion and high cost, because different module functions in the system actually have different requirements on the server. Some are CPU-intensive computer types, which require a CPU processor with strong performance, and some require memory IO-intensive types, which require a large amount of memory for data caching. If the server infrastructure required by the system is purchased according to the same standard, the hardware cost will be very high

(7) Low reliability: All module functions run in one process. A bug in any module function, such as memory leak / CPU continues to rise, may crash or slow down the entire process, thereby affecting overall application reliability

[0006] The existing business system can only call the entire business system during the calling process. When the business system is upgraded or fails (for example, the business system crashes or the memory occupied by the CPU soars), in the server, the business The system cannot perform the corresponding functions, and the business completed through the business system cannot run normally

Images