CN112799803A - Micro-service architecture operation maintenance method, device, equipment and readable storage medium - Google Patents

Micro-service architecture operation maintenance method, device, equipment and readable storage medium Download PDF

Info

Publication number
CN112799803A
CN112799803A CN202110051581.1A CN202110051581A CN112799803A CN 112799803 A CN112799803 A CN 112799803A CN 202110051581 A CN202110051581 A CN 202110051581A CN 112799803 A CN112799803 A CN 112799803A
Authority
CN
China
Prior art keywords
target
micro
service
maintained
receiving thread
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202110051581.1A
Other languages
Chinese (zh)
Other versions
CN112799803B (en
Inventor
纪旭光
石耀新
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Instant Technology Co Ltd
Original Assignee
Shenzhen Instant Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Instant Technology Co Ltd filed Critical Shenzhen Instant Technology Co Ltd
Priority to CN202110051581.1A priority Critical patent/CN112799803B/en
Publication of CN112799803A publication Critical patent/CN112799803A/en
Application granted granted Critical
Publication of CN112799803B publication Critical patent/CN112799803B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The invention discloses a micro service architecture operation maintenance method, a device, equipment and a readable storage medium, wherein the method comprises the following steps: when a micro service maintenance instruction is received, a target service gateway is established through a gateway component in a micro service architecture, and a target receiving thread pool is established through a degrading component in the micro service architecture; establishing an incidence relation between a target service gateway and a micro service to be maintained, and establishing an incidence relation between a target receiving thread pool and the micro service to be maintained; intercepting a target request sent by a target micro service to the micro service to be maintained through a target service gateway, and acquiring the operation type of the target request; if the operation type of the target request is write operation, storing a target receiving thread corresponding to the target request into a target receiving thread pool; when the micro service to be maintained is detected to be maintained, the target receiving thread pool is responded to complete the maintenance of the micro service to be maintained.

Description

Micro-service architecture operation maintenance method, device, equipment and readable storage medium
Technical Field
The present invention relates to the field of micro service architecture, and in particular, to a method, an apparatus, a device and a readable storage medium for maintaining operation of a micro service architecture.
Background
The micro-service architecture is a new technology for deploying applications and services, and solves the technical problem that the original single application architecture cannot meet the requirements of the current internet product, but the micro-service architecture also has the problems of the micro-service architecture itself, when a certain micro-service in the micro-service architecture is in a maintenance state, data requests between other micro-services and the micro-service become problems, and the existing solution is that when a certain micro-service in the micro-service architecture is in the maintenance state, other micro-services in the same micro-service architecture are also in the maintenance state, which is obviously not beneficial to the operation of the micro-service architecture, so when a certain micro-service in the micro-service architecture is in the maintenance state, how to ensure the normal operation of the micro-service architecture becomes the technical problem to be solved urgently.
Disclosure of Invention
The invention mainly aims to provide a micro-service architecture operation maintenance method, a micro-service architecture operation maintenance device, micro-service architecture operation maintenance equipment and a readable storage medium, and aims to solve the technical problem of how to guarantee the normal operation of a micro-service architecture when a certain micro-service in the micro-service architecture is in a maintenance state.
In addition, in order to achieve the above object, the present invention further provides a micro service architecture operation and maintenance method, where the micro service architecture operation and maintenance method includes the following steps:
when a micro service maintenance instruction is received, a target service gateway is established through a gateway component in the micro service architecture, and a target receiving thread pool is established through a degraded component in the micro service architecture;
establishing an incidence relation between the target service gateway and the micro service to be maintained, and establishing an incidence relation between the target receiving thread pool and the micro service to be maintained;
intercepting a target request sent by the target micro service to the micro service to be maintained through the target service gateway, and acquiring the operation type of the target request;
if the operation type of the target request is write operation, storing a target receiving thread corresponding to the target request into the target receiving thread pool;
and when the micro service to be maintained is detected to be maintained, responding to the target receiving thread pool to finish the maintenance of the micro service to be maintained.
Optionally, after the step of intercepting, by the target service gateway, a target request sent by the target microservice to the microservice to be maintained, and obtaining an operation type of the target request, the method includes:
if the operation type of the target request is a reading operation, acquiring preset response time corresponding to the target request, and acquiring maintenance time of the micro service to be maintained;
if the preset response time is longer than the maintenance time, storing a target receiving thread corresponding to the target request into a target receiving thread pool associated with the micro service to be maintained;
within the preset response time after the target request is sent, if the micro-service to be maintained is not detected to be maintained completely, removing the target receiving thread from the target receiving thread pool, and sending response abnormity prompt information to the target micro-service;
when the micro service to be maintained is detected to be maintained, responding to the target receiving thread pool to complete the maintenance of the micro service to be maintained, wherein the step of completing the maintenance of the micro service to be maintained comprises the following steps:
and in the preset response time after the target request is sent, if the micro service to be maintained is detected to be maintained, responding to the target receiving thread pool to complete the maintenance of the micro service to be maintained.
Optionally, if the operation type of the target request is a write operation, the step of storing the target receiving thread corresponding to the target request into the target receiving thread pool includes:
if the operation type of the target request is write operation, judging whether the target receiving thread pool is full;
if the target receiving thread pool is full, removing a first receiving thread from the target receiving thread pool, wherein the first receiving thread is the thread with the longest storage time in the target receiving thread pool;
storing the first receiving thread removed from the target receiving thread pool into a target database corresponding to the micro-service architecture, and sending write-in exception prompt information to the target micro-service;
and if the target receiving thread pool is not full, storing the target receiving thread corresponding to the target request into the target receiving thread pool.
Optionally, the step of responding to the target receiving thread pool to complete the maintenance of the micro service to be maintained when the completion of the maintenance of the micro service to be maintained is detected includes:
screening out a second receiving thread and a third receiving thread in the target receiving thread pool and the target database when the micro-service to be maintained is detected to be maintained, wherein the operation type of the request corresponding to the second receiving thread is the reading operation, and the operation type of the request corresponding to the third receiving thread is the writing operation;
acquiring read data corresponding to the second receiving thread and write data corresponding to the third receiving thread;
sending the read data to the target microservice, and receiving the write data;
and removing the second receiving thread and the third receiving thread from the target receiving thread pool, so that the target micro-service removes the sending thread corresponding to the second receiving thread and the sending thread corresponding to the third receiving thread, and the maintenance of the micro-service to be maintained is completed.
Further, to achieve the above object, the present invention further provides a micro service architecture operation and maintenance method, where the micro service architecture operation and maintenance method is applied to a micro service architecture, the micro service architecture includes a target micro service and a micro service to be maintained, the micro service architecture operation and maintenance method is applied to the target micro service, and the micro service architecture operation and maintenance method includes the following steps:
when a request sending instruction is received, acquiring a target request corresponding to the request sending instruction, and sending the target request to a target service gateway associated with the micro service to be maintained;
storing a target sending thread corresponding to the target request into a first sending thread pool associated with the target micro service;
and when response abnormity prompt information sent by the micro service to be maintained is received based on the target sending thread, removing the target sending thread from the first sending thread pool to finish the target request.
Optionally, the step of removing the target sending thread from the first sending thread pool to complete the target request when the response exception notification information sent by the micro service to be maintained is received based on the target sending thread includes:
when response abnormity prompt information sent by the micro service to be maintained is received, a target receiving thread corresponding to the response abnormity prompt information is obtained;
and if the target sending thread is matched with the target receiving thread, removing the target sending thread from the first sending thread pool to finish the target request.
Optionally, after the step of obtaining the target receiving thread corresponding to the response exception prompting information when the response exception prompting information sent by the micro service to be maintained is received, the method includes:
acquiring a first thread number associated with the target sending thread and a second thread number associated with the target receiving thread;
and if the first thread number is the same as the second thread number, determining that the target sending thread is matched with the target receiving thread.
In addition, to achieve the above object, the present invention further provides a microservice architecture operation and maintenance device, including:
the component calling module is used for creating a target service gateway through a gateway component in the micro service architecture and creating a target receiving thread pool through a degraded component in the micro service architecture when a micro service maintenance instruction is received;
the incidence relation establishing module is used for establishing the incidence relation between the target service gateway and the micro service to be maintained, and the incidence relation between the target receiving thread pool and the micro service to be maintained;
the target request intercepting module is used for intercepting a target request sent by the target micro service to the micro service to be maintained through the target service gateway and acquiring the operation type of the target request;
a target receiving thread storage module, configured to store a target receiving thread corresponding to the target request into the target receiving thread pool if the operation type of the target request is a write operation;
and the response module is used for responding to the target receiving thread pool when the micro service to be maintained is detected to be maintained, so as to complete the maintenance of the micro service to be maintained.
In addition, to achieve the above object, the present invention further provides a microservice architecture operation and maintenance device, including: the system comprises a memory, a processor and a micro service architecture operation and maintenance program which is stored on the memory and can run on the processor, wherein when the micro service architecture operation and maintenance program is executed by the processor, the steps of the micro service architecture operation and maintenance method are realized.
In addition, to achieve the above object, the present invention further provides a readable storage medium, where a microservice architecture operation and maintenance program is stored, and when being executed by a processor, the microservice architecture operation and maintenance program implements the steps of the microservice architecture operation and maintenance method as described above.
Compared with the prior art in which a micro service needs to be maintained because other related micro services cannot normally operate when one micro service needs to be maintained, in the embodiment of the invention, when the micro service to be maintained receives a micro service maintenance instruction, a target service gateway is created through a gateway component in the micro service architecture, a target receiving thread pool is created through a degrading component in the micro service architecture, an association relationship between the target service gateway and the micro service to be maintained is established, the association relationship between the target receiving thread pool and the micro service to be maintained is established, a target request sent by the target micro service to the micro service to be maintained is intercepted through the target service gateway, and the operation type of the target request is obtained, and if the operation type of the target request is write operation, storing a target receiving thread corresponding to the target request into the target receiving thread pool, and responding to the target receiving thread pool when the maintenance of the micro service to be maintained is detected to be completed so as to complete the maintenance of the micro service to be maintained. The method comprises the steps of establishing a target gateway and a target thread pool, enabling the micro-service to be maintained to normally receive and cache requests from other micro-services during maintenance, storing the requests into the thread pool, responding to the requests in the thread pool after the maintenance of the micro-service to be maintained is completed, and ensuring the normal operation of other micro-services without the need of maintaining other related micro-services during the maintenance of the micro-service to be maintained.
Drawings
Fig. 1 is a schematic hardware structure diagram of an embodiment of a microservice architecture operation and maintenance device according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a first embodiment of a microservice architecture operation maintenance method of the present invention;
FIG. 3 is a flowchart illustrating a second embodiment of a microservice architecture operation maintenance method of the present invention;
FIG. 4 is a functional block diagram of an embodiment of a microservice architecture operation maintenance device of the present invention;
FIG. 5 is a functional block diagram of a microservice architecture operation maintenance device according to still another embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in itself. Thus, "module", "component" or "unit" may be used mixedly.
The micro-service architecture operation maintenance terminal (called terminal, equipment or terminal equipment) in the embodiment of the invention can be a PC (personal computer), and can also be a mobile terminal equipment with a display function, such as a smart phone, a tablet personal computer and a portable computer.
As shown in fig. 1, the terminal may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, a communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.
Optionally, the terminal may further include a camera, a Radio Frequency (RF) circuit, a sensor, an audio circuit, a WiFi module, and the like. Such as light sensors, motion sensors, and other sensors. Specifically, the light sensor may include an ambient light sensor that may adjust the brightness of the display screen according to the brightness of ambient light, and a proximity sensor that may turn off the display screen and/or the backlight when the mobile terminal is moved to the ear. As one of the motion sensors, the gravity acceleration sensor can detect the magnitude of acceleration in each direction (generally, three axes), detect the magnitude and direction of gravity when the mobile terminal is stationary, and can be used for applications (such as horizontal and vertical screen switching, related games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer and tapping) and the like for recognizing the attitude of the mobile terminal; of course, the mobile terminal may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which are not described herein again.
Those skilled in the art will appreciate that the terminal structure shown in fig. 1 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 1, the memory 1005, which is a readable storage medium, may include therein an operating system, a network communication module, a user interface module, and a microservice architecture operation and maintenance program.
In the terminal shown in fig. 1, the network interface 1004 is mainly used for connecting to a backend server and performing data communication with the backend server; the user interface 1003 is mainly used for connecting a client (user side) and performing data communication with the client; and the processor 1001 may be configured to call the micro service architecture operation and maintenance program stored in the memory 1005, and when the micro service architecture operation and maintenance program is executed by the processor, the micro service architecture operation and maintenance program implements the operations in the micro service architecture operation and maintenance method provided by the following embodiments.
Based on the hardware structure of the equipment, the embodiment of the micro-service architecture operation maintenance method is provided.
Referring to fig. 2, in a first embodiment of the micro service architecture operation and maintenance method of the present invention, the micro service architecture operation and maintenance method includes:
step S10, when receiving the micro service maintenance instruction, creating the target service gateway through the gateway component in the micro service architecture, and creating the target receiving thread pool through the degraded component in the micro service architecture.
The micro-service architecture operation and maintenance method is applied to a micro-service architecture, the micro-service architecture comprises a target micro-service and a micro-service to be maintained, wherein the target micro-service and the micro-service to be maintained include but are not limited to a plurality of micro-services. When the micro service to be maintained receives a micro service maintenance instruction, a target service gateway is established through a gateway component in a micro service architecture, the gateway component in the micro service is used for establishing a communication interface and a communication rule between micro services, and the target service gateway established through the gateway component is an interface called by a micro service instruction, so that the instruction received by the micro service to be maintained can be filtered, screened and classified. The micro-service architecture also comprises a degradation component used for managing the instructions received by the micro-service, when the micro-service to be maintained receives the maintenance instructions, a target receiving thread pool is created through the degradation component in the micro-service architecture, and the created target thread pool is used for caching the instructions received by the micro-service to be maintained.
Step S20, establishing an association relationship between the target service gateway and the micro service to be maintained, and an association relationship between the target receiving thread pool and the micro service to be maintained.
The association relationship between the target service gateway and the micro service to be maintained includes an instruction receiving rule of the micro service to be maintained, that is, when the micro service to be maintained receives the maintenance instruction, the target service gateway is created through a gateway component in the micro service architecture, the association relationship between the micro service to be maintained and the target service gateway is established, and a filtering and screening rule of the target service gateway for the instruction is established through the association relationship, for example, when the micro service to be maintained receives the maintenance instruction, only a writing request instruction is responded, and a reading request instruction is filtered. Meanwhile, an incidence relation between the target receiving thread pool and the micro service to be maintained and a management rule of the instructions received by the micro service to be maintained by the target receiving thread pool are established, such as the highest instruction cache number, instruction removal or deletion logic and the like.
Step S30, intercepting, by the target service gateway, a target request sent by the target microservice to the microservice to be maintained, and obtaining an operation type of the target request.
When a micro service to be maintained receives a maintenance instruction, intercepting a target request received by the micro service to be maintained through an established target service gateway, and determining an operation type of the target request, wherein the target request comprises a requested operation type and task information, the operation type of the target request comprises a write operation and a read operation, the task information refers to data requested to be read or written and data information, the data information comprises a data type, a data storage address, a data size and the like, and the target micro service cannot respond to all types of request instructions during maintenance, so that all request instructions need to be intercepted through the established target service gateway and are filtered according to the operation type of the request instruction, for example, when the micro service to be maintained is in the maintenance period, only the request instruction of the write operation type can be responded, and the request instruction of the read operation type cannot be responded, intercepting the request instruction through the target service gateway, and screening and filtering the read type request instruction.
Step S40, if the operation type of the target request is a write operation, storing the target receiving thread corresponding to the target request into the target receiving thread pool.
When the operation type of the target request received by the micro service to be maintained is write operation, storing the target receiving thread corresponding to the received target request into the established target receiving thread pool for caching, wherein the micro service to be maintained can receive but not necessarily can completely execute the request instruction during maintenance, and for the request instruction which cannot be immediately executed, the request instruction can be stored into the established thread pool for caching.
And step S50, when the micro service to be maintained is detected to be maintained, responding to the target receiving thread pool to complete the maintenance of the micro service to be maintained.
When the micro service to be maintained is detected to be maintained, for example, the micro service to be maintained executes a start instruction, it can be determined that the micro service to be maintained is maintained, a target receiving thread stored in a target thread pool corresponding to the micro service to be maintained responds, and data of the micro service to be maintained is updated by using task information in the target thread, so that maintenance of the micro service to be maintained is completed.
Specifically, steps subsequent to step S30 include:
step a1, if the operation type of the target request is a read operation, acquiring a preset response time corresponding to the target request, and acquiring a maintenance time of the micro service to be maintained.
Step a2, if the preset response time is longer than the maintenance time, storing the target receiving thread corresponding to the target request into the target receiving thread pool associated with the micro service to be maintained.
Step a3, in the preset response time after the target request is sent, if the micro-service to be maintained is not detected to be maintained, removing the target receiving thread from the target receiving thread pool, and sending response exception prompt information to the target micro-service.
The step of step S50 refinement includes:
step a4, in the preset response time after the target request is sent, if the micro service to be maintained is detected to be maintained, responding to the target receiving thread pool to complete the maintenance of the micro service to be maintained.
When the operation type of the intercepted request instruction is a read operation, acquiring preset response time of the request, wherein the preset response time of the request instruction is the response time of the request instruction defined by the micro-service sending the request instruction, the response time requirements of different micro-services on the sent request instruction are different, and the response time requirements of the same micro-service on the sent request instructions of different operation types may also be different. Therefore, it is required to obtain the preset response time of the target request of the read operation type received by the micro service to be maintained and the maintenance time of the micro service to be maintained, and compare the preset response time of the target request with the maintenance time of the micro service to be maintained, it is required to say that the micro service to be maintained is provided with the preset maintenance time, for example, "xxx year xxx month xxx day, 20:00-22: 00" in the afternoon, when the micro service to be maintained receives the request instruction of the read operation type, if the preset response time of the target request instruction is greater than the maintenance time of the micro service to be maintained, for example, the preset response time of the target request is 2 minutes, the time of the micro service to be maintained receiving the target request is "xxx year xxx month xxx day, 21:59: 30" in the afternoon, the preset maintenance time is also 30 seconds, the preset response time of the target request is greater than the maintenance time of the micro service to be maintained, the target request for that write operation type is deposited into the thread pool waiting for a response.
Furthermore, the actual maintenance time of the micro service to be maintained is not controllable, the target request includes the time information of the request transmission, after the target request is sent and stored in a thread pool established by the micro-service to be maintained, the maintenance completion of the micro-service to be maintained is not detected after the preset response time, the target request is removed from the target thread pool, and simultaneously response exception prompting information is sent to the target micro-service sending the target request, the response exception prompting information comprises request instruction information, a response result, a response exception type and the like, where the response exception types include request failure, request no response, etc., the request failure may be due to an authority problem, for example, some microservices can only write data, do not allow reading data, and request no response may be due to the microservices to be maintained failing to respond to the request, or a response timeout. And if the target request is sent and stored in the thread pool established by the micro service to be maintained and the maintenance of the micro service to be maintained is detected to be completed within the preset response time, responding the target request in the target thread pool corresponding to the micro service to be maintained and updating the data of the micro service to be maintained so as to complete the maintenance of the micro service to be maintained.
Specifically, the step of step S40 refinement includes:
step b1, if the operation type of the target request is write operation, determining whether the target receiving thread pool is full.
And b2, if the target receiving thread pool is full, removing the first receiving thread from the target receiving thread pool, wherein the first receiving thread is the thread with the longest storage time in the target receiving thread pool.
Step b3, storing the first receiving thread removed from the target receiving thread pool into a target database corresponding to the micro service architecture, and sending a write exception prompt message to the target micro service.
Step b4, if the target receiving thread pool is not full, storing the target receiving thread corresponding to the target request into the target receiving thread pool.
If the operation type of the target request received by the micro service to be maintained is a write operation, when the target receiving thread corresponding to the target request is stored in the target receiving thread pool, whether the target receiving thread pool corresponding to the micro service to be maintained is full is required to be judged, if the target receiving thread pool is full, the first receiving thread with the longest storage time in the target thread pool is removed, the first receiving thread is stored in a target database corresponding to the micro service architecture, and then write exception prompt information is sent to the target micro service sending the target request corresponding to the first receiving thread. And if the target thread pool corresponding to the micro service to be maintained is not full, storing the target request received by the micro service to be maintained into the target thread pool.
Specifically, the step of step S50 refinement includes:
step c1, when the micro-service to be maintained is detected to be maintained, screening out a second receiving thread and a third receiving thread in the target receiving thread pool and the target database, wherein the operation type of the request corresponding to the second receiving thread is the read operation, and the operation type of the request corresponding to the third receiving thread is the write operation.
And c2, acquiring the read data corresponding to the second receiving thread and the write data corresponding to the third receiving thread.
And c3, sending the read data to the target micro service and receiving the write data.
Step c4, removing the second receiving thread and the third receiving thread from the target receiving thread pool, so that the target micro-service removes the sending thread corresponding to the second receiving thread and the sending thread corresponding to the third receiving thread, and completes the maintenance of the micro-service to be maintained.
When the micro-service to be maintained is detected to be maintained, screening a second receiving thread and a third receiving thread from a target thread pool and a target database of the micro-service to be maintained, wherein the operation type of a request corresponding to the second receiving thread is reading operation, the operation type of a request corresponding to the third receiving thread is writing operation, acquiring reading data corresponding to the second receiving thread and writing data corresponding to the third receiving thread, sending the reading data to the target micro-service corresponding to the second receiving thread, receiving the writing data corresponding to the third receiving thread, removing the second receiving thread and the third receiving thread, and after removing the receiving thread from the thread pool of the micro-service to be maintained, sending a response completion instruction to the target micro-service corresponding to the removed receiving thread so that the target micro-service removes the corresponding sending thread, thereby completing data updating of the micro-service to be maintained, and clearing the cache data of the thread pool to finish the maintenance of the micro service to be maintained.
In this embodiment, when a micro service to be maintained receives a micro service maintenance instruction, a target service gateway is created through a gateway component in the micro service architecture, a target receiving thread pool is created through a degraded component in the micro service architecture, an association relationship between the target service gateway and the micro service to be maintained is established, the association relationship between the target receiving thread pool and the micro service to be maintained intercepts a target request sent by the target micro service to the micro service to be maintained through the target service gateway, and obtains an operation type of the target request, if the operation type of the target request is a write operation, a target receiving thread corresponding to the target request is stored in the target receiving thread pool, and when it is detected that maintenance of the micro service to be maintained is completed, a response is made to the target receiving thread pool, to complete maintenance of the microservice to be maintained. The method comprises the steps of establishing a target gateway and a target thread pool, enabling the micro-service to be maintained to normally receive and cache requests from other micro-services during maintenance, storing the requests into the thread pool, responding to the requests in the thread pool after the maintenance of the micro-service to be maintained is completed, and ensuring the normal operation of other micro-services without the need of maintaining other related micro-services during the maintenance of the micro-service to be maintained.
Further, referring to fig. 3, in a second embodiment of the micro service architecture operation and maintenance method of the present invention, the micro service architecture operation and maintenance method includes:
step S60, when a request sending instruction is received, a target request corresponding to the request sending instruction is obtained, and the target request is sent to a target service gateway associated with the micro service to be maintained.
Step S70, storing the target sending thread corresponding to the target request in the first sending thread pool associated with the target microservice.
Step S80, when the response exception notification information sent by the to-be-maintained microservice is received based on the target sending thread, removing the target sending thread from the first sending thread pool to complete the target request.
The same as the foregoing embodiment, the micro service architecture operation maintenance method of the present invention is applied to a micro service architecture, where the micro service architecture includes a micro service to be maintained and a target micro service, and both the micro service to be maintained and the target micro service include but are not limited to a plurality of micro services. When the target micro service receives a request sending instruction, acquiring a target request corresponding to the request sending instruction, sending the target request to a target service gateway associated with the micro service to be maintained, and sending the target request to the target service gateway associated with the micro service to be maintained includes, but is not limited to, the following two cases:
the first condition is as follows: after the target micro service acquires the target request corresponding to the request sending instruction, detecting the micro service receiving the target request according to the target request, and detecting that the micro service receiving the target request is the micro service to be maintained;
case two: and after the target micro service acquires a target request corresponding to a target instruction request sending instruction, directly sending the target request for detecting the micro service receiving the target request, and if the micro service receiving the target request is the micro service to be maintained, intercepting the target request sent by the target micro service by a target gateway established by the micro service to be maintained.
When a target request is intercepted by a target service gateway associated with a micro service to be maintained, the target micro service receives an interception instruction from the target service gateway, after the interception instruction is received, a first sending thread pool associated with the target service is established, a sending thread corresponding to the target request is stored in the first sending thread pool, if the target request corresponding to the target sending thread is a reading operation type, when response abnormity prompt information corresponding to the target sending thread is received, the target sending thread is removed from the target sending thread pool, the target request corresponding to the target sending thread can also be a writing operation type, and if the target request is the writing operation type, if the writing abnormity prompt information is received and the micro service thread pool to be maintained is proved to be full, the target sending thread corresponding to the target request needs to be stored in a target database determined by the micro service architecture, after the maintenance of the micro-service to be maintained is completed, the response can be carried out on the written data corresponding to the target thread. When the micro service to be maintained completes the response to the target request, no matter the request is a request of a write operation type or a request of a read operation type, the target micro service receives a response completion instruction from the micro service to be maintained, when the target micro service receives the response completion instruction, the first sending thread corresponding to the target request associated with the response completion instruction is removed from the first sending thread pool, and after the first receiving thread is removed from the first thread pool, the target micro service indicates that the target request is completed.
Specifically, the step of step S80 refinement includes:
and d1, when receiving the response exception prompt information sent by the micro service to be maintained, acquiring a target receiving thread corresponding to the response exception prompt information.
Step d2, if the target sending thread matches the target receiving thread, removing the target sending thread from the first sending thread pool to complete the target request.
When the target micro-service receives the response exception prompting information sent by the micro-service to be maintained, a target receiving thread corresponding to the response exception prompting information is obtained, and then a target sending thread corresponding to the target receiving thread is obtained, wherein the obtaining of the target sending thread can be according to the thread number, the storage address of the target sending thread corresponding to the target receiving thread, or the sending time of the target request, and is not specifically limited herein. And if the target sending thread is matched with the target receiving thread, removing the target sending thread from the first sending thread pool, and finishing the target request corresponding to the target sending thread after removing the target sending thread from the first sending thread pool.
Specifically, the steps after step d1 include:
and e1, acquiring a first thread number associated with the target sending thread and a second thread number associated with the target receiving thread.
Step e2, if the first thread number is the same as the second thread number, determining that the target sending thread matches the target receiving thread.
Taking number matching as an example, when a target request is sent and a target sending thread is stored in a target sending thread pool, the target request and the target sending thread corresponding to the target request are coded, the target request and the corresponding target thread have the same number, response exception prompt information sent by the micro service to be maintained and received by the target micro service comprises target request information, the number of the target request is obtained from the information of the target request, and the target sending thread corresponding to the target request is obtained according to the number of the target request. And when the target sending thread is matched with the target receiving thread, taking the acquired number associated with the target sending thread as a first thread number, taking the acquired number associated with the target receiving thread as a second thread number, and if the first thread number is the same as the second thread number, determining that the target sending thread is matched with the target receiving thread.
In this embodiment, a micro-service architecture operation maintenance method is applied to a target micro-service, when the target micro-service receives a request sending instruction, a target request corresponding to the request sending instruction is obtained, the target request is sent to a target service gateway associated with the micro-service to be maintained, a target sending thread corresponding to the target request is stored in a first sending thread pool associated with the target micro-service, and when response exception prompting information sent by the micro-service to be maintained is received based on the target sending thread, the target sending thread is removed from the first sending thread pool to complete the target request. During the maintenance of the micro-service to be maintained, the target micro-service is communicated with the micro-service to be maintained through the established sending thread pool, the target micro-service can still normally run during the maintenance of the micro-service to be maintained, the maintenance is not required to be carried out together with the micro-service to be maintained, and the normal running of the target micro-service during the maintenance of the associated micro-service to be maintained is ensured by utilizing the thread communication.
In addition, referring to fig. 4, an embodiment of the present invention further provides a micro service architecture operation and maintenance device, where the micro service architecture operation and maintenance device includes:
a component calling module 10, configured to, when a micro-service maintenance instruction is received, create a target service gateway through a gateway component in the micro-service architecture, and create a target receiving thread pool through a degraded component in the micro-service architecture;
an association relationship establishing module 20, configured to establish an association relationship between the target service gateway and the micro service to be maintained, and an association relationship between the target receiving thread pool and the micro service to be maintained;
a target request intercepting module 30, configured to intercept, through the target service gateway, a target request sent by the target microservice to the microservice to be maintained, and obtain an operation type of the target request;
a target receiving thread storing module 40, configured to store a target receiving thread corresponding to the target request into the target receiving thread pool if the operation type of the target request is a write operation;
and the response module 50 is configured to, when it is detected that the maintenance of the micro service to be maintained is completed, respond to the target receiving thread pool to complete the maintenance of the micro service to be maintained.
Optionally, the microservice architecture operation and maintenance device includes:
the time acquisition module is used for acquiring preset response time corresponding to the target request and acquiring maintenance time of the micro service to be maintained if the operation type of the target request is reading operation;
a target receiving thread storage module, configured to store a target receiving thread corresponding to the target request into the target receiving thread pool associated with the micro service to be maintained, if the preset response time is longer than the maintenance time;
a response exception sending module, configured to remove the target receiving thread from the target receiving thread pool and send a response exception prompt message to the target micro service if it is not detected that the maintenance of the micro service to be maintained is completed within the preset response time after the target request is sent;
the response module 50 includes:
and the response unit is used for responding to the target receiving thread pool to finish the maintenance of the micro service to be maintained if the maintenance of the micro service to be maintained is detected to be finished within the preset response time after the target request is sent.
Optionally, the target receiving thread storing module 40 includes:
a determining unit, configured to determine whether the target receiving thread pool is full if the operation type of the target request is a write operation;
a first receiving thread removing unit, configured to remove a first receiving thread from the target receiving thread pool if the target receiving thread pool is full, where the first receiving thread is a thread with a longest storage time in the target receiving thread pool;
an exception prompt information writing unit, configured to store the first receiving thread removed from the target receiving thread pool in a target database corresponding to the micro service architecture, and send written exception prompt information to the target micro service;
and the target receiving thread storage unit is used for storing the target receiving thread corresponding to the target request into the target receiving thread pool if the target receiving thread pool is not full.
Optionally, the response module 50 includes:
the screening unit is used for screening out a second receiving thread and a third receiving thread in the target receiving thread pool and the target database when the micro-service to be maintained is detected to be maintained, wherein the operation type of the request corresponding to the second receiving thread is the reading operation, and the operation type of the request corresponding to the third receiving thread is the writing operation;
a data obtaining unit, configured to obtain read data corresponding to the second receiving thread and write data corresponding to the third receiving thread;
the data sending and receiving unit is used for sending the read data to the target microservice and receiving the written data;
and the thread removing unit is used for removing the second receiving thread and the third receiving thread from the target receiving thread pool so that the target micro service removes the sending thread corresponding to the second receiving thread and the sending thread corresponding to the third receiving thread to finish the maintenance of the micro service to be maintained.
In addition, referring to fig. 5, an embodiment of the present invention further provides another microservice architecture operation and maintenance apparatus, where the microservice architecture operation and maintenance apparatus further includes:
a target request sending module 50, configured to, when a request sending instruction is received, obtain a target request corresponding to the request sending instruction, and send the target request to a target service gateway associated with the micro service to be maintained;
a target sending thread storing module 60, configured to store a target sending thread corresponding to the target request in a first sending thread pool associated with the target microservice;
and a target sending thread removing module 70, configured to remove the target sending thread from the first sending thread pool to complete the target request when response exception prompting information sent by the micro service to be maintained is received based on the target sending thread.
Optionally, the target sending thread removing module 70 includes:
the target receiving thread receiving unit is used for acquiring a target receiving thread corresponding to the response abnormity prompt information when receiving the response abnormity prompt information sent by the micro service to be maintained;
a matching unit, configured to remove the target sending thread from the first sending thread pool to complete the target request if the target sending thread is matched with the target receiving thread.
Optionally, the microservice architecture operation and maintenance device includes:
a thread number obtaining module, configured to obtain a first thread number associated with the target sending thread, and a second thread number associated with the target receiving thread;
and the matching judgment module is used for determining that the target sending thread is matched with the target receiving thread if the first thread number is the same as the second thread number.
In addition, an embodiment of the present invention further provides a readable storage medium, where a micro service architecture operation and maintenance program is stored on the readable storage medium, and when executed by a processor, the micro service architecture operation and maintenance program implements operations in the micro service architecture operation and maintenance method provided in the foregoing embodiment.
The method executed by each program module can refer to each embodiment of the method of the present invention, and is not described herein again.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity/action/object from another entity/action/object without necessarily requiring or implying any actual such relationship or order between such entities/actions/objects; the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
For the apparatus embodiment, since it is substantially similar to the method embodiment, it is described relatively simply, and reference may be made to some descriptions of the method embodiment for relevant points. The above-described apparatus embodiments are merely illustrative, in that elements described as separate components may or may not be physically separate. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the invention. One of ordinary skill in the art can understand and implement it without inventive effort.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the micro service architecture operation and maintenance method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims (10)

1. A micro-service architecture operation and maintenance method is applied to a micro-service architecture, the micro-service architecture comprises a target micro-service and a micro-service to be maintained, the micro-service architecture operation and maintenance method is applied to the micro-service to be maintained, and the micro-service architecture operation and maintenance method comprises the following steps:
when a micro service maintenance instruction is received, a target service gateway is established through a gateway component in the micro service architecture, and a target receiving thread pool is established through a degraded component in the micro service architecture;
establishing an incidence relation between the target service gateway and the micro service to be maintained, and establishing an incidence relation between the target receiving thread pool and the micro service to be maintained;
intercepting a target request sent by the target micro service to the micro service to be maintained through the target service gateway, and acquiring the operation type of the target request;
if the operation type of the target request is write operation, storing a target receiving thread corresponding to the target request into the target receiving thread pool;
and when the micro service to be maintained is detected to be maintained, responding to the target receiving thread pool to finish the maintenance of the micro service to be maintained.
2. The micro-service architecture operation maintenance method of claim 1, wherein the step of intercepting, by the target service gateway, a target request sent by the target micro-service to the micro-service to be maintained and obtaining an operation type of the target request is followed by:
if the operation type of the target request is a reading operation, acquiring preset response time corresponding to the target request, and acquiring maintenance time of the micro service to be maintained;
if the preset response time is longer than the maintenance time, storing a target receiving thread corresponding to the target request into a target receiving thread pool associated with the micro service to be maintained;
within the preset response time after the target request is sent, if the micro-service to be maintained is not detected to be maintained completely, removing the target receiving thread from the target receiving thread pool, and sending response abnormity prompt information to the target micro-service;
when the micro service to be maintained is detected to be maintained, responding to the target receiving thread pool to complete the maintenance of the micro service to be maintained, wherein the step of completing the maintenance of the micro service to be maintained comprises the following steps:
and in the preset response time after the target request is sent, if the micro service to be maintained is detected to be maintained, responding to the target receiving thread pool to complete the maintenance of the micro service to be maintained.
3. The micro service architecture operation maintenance method according to claim 1, wherein the step of storing the target receiving thread corresponding to the target request into the target receiving thread pool if the operation type of the target request is a write operation comprises:
if the operation type of the target request is write operation, judging whether the target receiving thread pool is full;
if the target receiving thread pool is full, removing a first receiving thread from the target receiving thread pool, wherein the first receiving thread is the thread with the longest storage time in the target receiving thread pool;
storing the first receiving thread removed from the target receiving thread pool into a target database corresponding to the micro-service architecture, and sending write-in exception prompt information to the target micro-service;
and if the target receiving thread pool is not full, storing the target receiving thread corresponding to the target request into the target receiving thread pool.
4. The micro service architecture operation maintenance method according to claim 2 or 3, wherein the step of responding to the target receiving thread pool to complete the maintenance of the micro service to be maintained when the completion of the maintenance of the micro service to be maintained is detected comprises:
screening out a second receiving thread and a third receiving thread in the target receiving thread pool and the target database when the micro-service to be maintained is detected to be maintained, wherein the operation type of the request corresponding to the second receiving thread is the reading operation, and the operation type of the request corresponding to the third receiving thread is the writing operation;
acquiring read data corresponding to the second receiving thread and write data corresponding to the third receiving thread;
sending the read data to the target microservice, and receiving the write data;
and removing the second receiving thread and the third receiving thread from the target receiving thread pool, so that the target micro-service removes the sending thread corresponding to the second receiving thread and the sending thread corresponding to the third receiving thread, and the maintenance of the micro-service to be maintained is completed.
5. A micro-service architecture operation and maintenance method is applied to a micro-service architecture, the micro-service architecture comprises a target micro-service and a micro-service to be maintained, the micro-service architecture operation and maintenance method is applied to the target micro-service, and the micro-service architecture operation and maintenance method comprises the following steps:
when a request sending instruction is received, acquiring a target request corresponding to the request sending instruction, and sending the target request to a target service gateway associated with the micro service to be maintained;
storing a target sending thread corresponding to the target request into a first sending thread pool associated with the target micro service;
and when response abnormity prompt information sent by the micro service to be maintained is received based on the target sending thread, removing the target sending thread from the first sending thread pool to finish the target request.
6. The micro-service architecture operation maintenance method according to claim 5, wherein the step of removing the target sending thread from the first sending thread pool to complete the target request when the response exception prompting message sent by the micro-service to be maintained is received based on the target sending thread comprises:
when response abnormity prompt information sent by the micro service to be maintained is received, a target receiving thread corresponding to the response abnormity prompt information is obtained;
and if the target sending thread is matched with the target receiving thread, removing the target sending thread from the first sending thread pool to finish the target request.
7. The micro-service architecture operation maintenance method according to claim 6, wherein after the step of obtaining the target receiving thread corresponding to the response exception prompt message when receiving the response exception prompt message sent by the micro-service to be maintained, the method comprises:
acquiring a first thread number associated with the target sending thread and a second thread number associated with the target receiving thread;
and if the first thread number is the same as the second thread number, determining that the target sending thread is matched with the target receiving thread.
8. A microservice architecture operation and maintenance device, the microservice architecture operation and maintenance device comprising:
the component calling module is used for creating a target service gateway through a gateway component in the micro service architecture and creating a target receiving thread pool through a degraded component in the micro service architecture when a micro service maintenance instruction is received;
the incidence relation establishing module is used for establishing the incidence relation between the target service gateway and the micro service to be maintained, and the incidence relation between the target receiving thread pool and the micro service to be maintained;
the target request intercepting module is used for intercepting a target request sent by the target micro service to the micro service to be maintained through the target service gateway and acquiring the operation type of the target request;
a target receiving thread storage module, configured to store a target receiving thread corresponding to the target request into the target receiving thread pool if the operation type of the target request is a write operation;
and the response module is used for responding to the target receiving thread pool when the micro service to be maintained is detected to be maintained, so as to complete the maintenance of the micro service to be maintained.
9. A microservice architecture operation and maintenance device, the microservice architecture operation and maintenance device comprising: memory, a processor and a micro service architecture operation and maintenance program stored on the memory and executable on the processor, the micro service architecture operation and maintenance program when executed by the processor implementing the steps of the micro service architecture operation and maintenance method according to any one of claims 1 to 7.
10. A readable storage medium, wherein the readable storage medium stores thereon a micro service architecture operation and maintenance program, and the micro service architecture operation and maintenance program, when executed by a processor, implements the steps of the micro service architecture operation and maintenance method according to any one of claims 1 to 7.
CN202110051581.1A 2021-01-14 2021-01-14 Micro-service architecture operation maintenance method, device, equipment and readable storage medium Active CN112799803B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110051581.1A CN112799803B (en) 2021-01-14 2021-01-14 Micro-service architecture operation maintenance method, device, equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110051581.1A CN112799803B (en) 2021-01-14 2021-01-14 Micro-service architecture operation maintenance method, device, equipment and readable storage medium

Publications (2)

Publication Number Publication Date
CN112799803A true CN112799803A (en) 2021-05-14
CN112799803B CN112799803B (en) 2023-11-17

Family

ID=75809419

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110051581.1A Active CN112799803B (en) 2021-01-14 2021-01-14 Micro-service architecture operation maintenance method, device, equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN112799803B (en)

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105447092A (en) * 2015-11-09 2016-03-30 联动优势科技有限公司 Caching method and apparatus
WO2018113556A1 (en) * 2016-12-22 2018-06-28 成都西加云杉科技有限公司 Network operation support system and network device management method
CN108427581A (en) * 2018-02-07 2018-08-21 平安普惠企业管理有限公司 System micro services method and terminal device
US20180324119A1 (en) * 2017-05-05 2018-11-08 ShieldX Networks, Inc. Upgrading components of a messaging system used by a microservice-based application
CN109101334A (en) * 2018-06-29 2018-12-28 中译语通科技股份有限公司 A kind of micro services concurrency control method towards Zuul gateway
CN109981561A (en) * 2019-01-17 2019-07-05 华南理工大学 Monomer architecture system moves to the user authen method of micro services framework
US20190304445A1 (en) * 2018-03-30 2019-10-03 International Business Machines Corporation Conversational framework
CN110377437A (en) * 2019-07-19 2019-10-25 深圳前海微众银行股份有限公司 Communication means, computer equipment and storage medium between a kind of micro services
TWI676374B (en) * 2018-09-10 2019-11-01 中華電信股份有限公司 Server and method for assigning job for microservices thereof
US20200162578A1 (en) * 2018-11-19 2020-05-21 International Business Machines Corporation Microservices request flow control synchronization
WO2020115521A1 (en) * 2018-12-02 2020-06-11 Pratik Sharma Service gateway in microservices architecture
CN111756601A (en) * 2020-06-24 2020-10-09 中国平安财产保险股份有限公司 Microservice architecture monitoring method and device, computer equipment and readable storage medium
CN112000448A (en) * 2020-07-17 2020-11-27 北京计算机技术及应用研究所 Micro-service architecture-based application management method

Patent Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105447092A (en) * 2015-11-09 2016-03-30 联动优势科技有限公司 Caching method and apparatus
WO2018113556A1 (en) * 2016-12-22 2018-06-28 成都西加云杉科技有限公司 Network operation support system and network device management method
US20180324119A1 (en) * 2017-05-05 2018-11-08 ShieldX Networks, Inc. Upgrading components of a messaging system used by a microservice-based application
CN108427581A (en) * 2018-02-07 2018-08-21 平安普惠企业管理有限公司 System micro services method and terminal device
US20190304445A1 (en) * 2018-03-30 2019-10-03 International Business Machines Corporation Conversational framework
CN109101334A (en) * 2018-06-29 2018-12-28 中译语通科技股份有限公司 A kind of micro services concurrency control method towards Zuul gateway
TWI676374B (en) * 2018-09-10 2019-11-01 中華電信股份有限公司 Server and method for assigning job for microservices thereof
US20200162578A1 (en) * 2018-11-19 2020-05-21 International Business Machines Corporation Microservices request flow control synchronization
WO2020115521A1 (en) * 2018-12-02 2020-06-11 Pratik Sharma Service gateway in microservices architecture
CN109981561A (en) * 2019-01-17 2019-07-05 华南理工大学 Monomer architecture system moves to the user authen method of micro services framework
CN110377437A (en) * 2019-07-19 2019-10-25 深圳前海微众银行股份有限公司 Communication means, computer equipment and storage medium between a kind of micro services
CN111756601A (en) * 2020-06-24 2020-10-09 中国平安财产保险股份有限公司 Microservice architecture monitoring method and device, computer equipment and readable storage medium
CN112000448A (en) * 2020-07-17 2020-11-27 北京计算机技术及应用研究所 Micro-service architecture-based application management method

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
S. RAJAPAKSA等: ""A Scalable Bioinformatics Analysis Platform based on Microservices Architecture"", 《IEEE》 *
周家昊: ""微服务架构关键技术研究与通用框架实现"", 《中国优秀硕士学位论文全文数据库 信息科技辑》 *

Also Published As

Publication number Publication date
CN112799803B (en) 2023-11-17

Similar Documents

Publication Publication Date Title
CN107276789B (en) Log uploading method and device and computer readable storage medium
KR102379313B1 (en) Electronic device for displaying application andoperating method thereof
US20160007204A1 (en) Method and apparatus of notifying of smishing
CN109582402B (en) Page display method and device
CN107577472B (en) Software installation method and device and computer readable storage medium
EP2784661B1 (en) Computer program product, information processing method, and information processing apparatus
CN107645582B (en) Information changing method, terminal equipment and computer readable medium
CN107908487B (en) Task control management method, device and equipment and computer readable storage medium
CN109117153B (en) Application processing method, device, terminal and storage medium
US11169697B2 (en) Electronic device and method for displaying contextual information of application
US11782695B2 (en) Dynamic ring structure for deployment policies for improved reliability of cloud service
CN108415767B (en) Server thread control method, device, equipment and readable storage medium
CN110995842A (en) Method, device and equipment for downloading service data and storage medium
CN110989877A (en) Message management method, related equipment and computer readable storage medium
CN112799803B (en) Micro-service architecture operation maintenance method, device, equipment and readable storage medium
CN114096946A (en) Method and apparatus for managing applications
CN110018918B (en) Method and device for repairing terminal abnormity, mobile terminal and storage medium
CN110321251B (en) Data backup method, device, equipment and storage medium based on network block equipment
CN113421084B (en) Bus card processing method, device, equipment and readable storage medium
US11947709B2 (en) Electronic device for controlling access to device resource and operation method thereof
US11455318B2 (en) Data replication using probabilistic replication filters
CN113138763A (en) Page construction method, device, equipment and computer readable storage medium
US20140324948A1 (en) Information processing apparatus and control method thereof
CN111049981A (en) Message identification method, device, user equipment and computer readable storage medium
CN113835846B (en) Method and device for creating k8s cluster and computer-readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant