Container management method and device based on target application architecture, and electronic equipment

Abstract

The invention discloses a container management method and device based on a target application architecture and electronic equipment, and relates to the technical field of cloud computing or other related fields, and the method comprises the following steps: detecting the health state of a WEB container by an external network soft load balancer, isolating the WEB container when the health state is detected to be abnormal, and storing the WEB container in the external network soft load balancer; the method comprises the following steps of: detecting the health state of an APP container by a health server, bearing the service flow by other health WEB containers, detecting the health state of the APP container by an intranet soft load balancer, isolating the APP container when detecting that the health state is abnormal, bearing the service flow by other health APP containers, and detecting the health state of a corresponding database by the APP container. When the health state is abnormal, all the APP containers in the APP group where the APP containers are located are isolated, and other APP groups bear the service flow. According to the method and the device, the technical problem that the use performance of the application is influenced due to the fact that the time for finding the fault is relatively late because the application architecture lacks an automatic detection and automatic isolation mechanism in the related technology is solved.

Description

Technical Field

[0001] The present invention relates to the field of cloud computing technology or other related fields, and in particular to a container management method and device based on a target application architecture, and an electronic device. Background Art

[0002] In the application environment of the Internet and financial industries, it is crucial to ensure the high availability and disaster recovery capabilities of the system. As users' expectations for service stability and response speed increase, enterprises must take effective measures to deal with system downtime caused by hardware failure, software anomalies or network problems. To this end, load balancing and redundant architectures are widely used in the deployment of servers and databases to improve performance and ensure that the system can quickly recover and continue to provide services when a single point of failure occurs.

[0003] In the related art, the existing system deployment strategies have obvious deficiencies in high availability and disaster recovery capabilities when facing core components, especially database server failures. Although WEB servers and APP servers can better cope with single point failures through load balancing deployment, databases usually adopt a master-slave mode. Once the master database fails, manual intervention is required to switch the master and standby databases, which not only increases the complexity of emergency response and prolongs the RTO (recovery time objective) and RPO (recovery point objective), but also during the switching process, the system will face a short service interruption, affecting user experience and transaction continuity. At the same time, the existing system deployment strategy lacks an automatic detection and automatic isolation mechanism for faulty databases, resulting in the system being unable to identify and isolate the problem database in time at the beginning of the failure, thereby amplifying the scope of the failure and increasing the failure recovery time. The existence of these problems makes it impossible for the existing system deployment strategy to achieve fast and imperceptible self-discovery and self-healing of faults in terms of ensuring the global high availability of the system, especially in the database failure scenario.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present invention provide a container management method and device, and an electronic device based on a target application architecture, so as to at least solve the technical problem in the related art that the application architecture lacks an automatic detection and automatic isolation mechanism, resulting in a late detection of faults and affecting the application performance.

[0006] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a container management method based on a target application architecture is provided, the target application architecture comprising: an intranet soft load balancer, multiple WEB containers, multiple APP groups and multiple databases, wherein each APP group comprises multiple APP containers, all APP containers in the same APP group use one database, and different APP groups use different databases, the container management method comprises: based on a first preset frequency, an external network soft load balancer detects the health status of all WEB containers, for each WEB container, when it is detected that the health status of the WEB container is abnormal, the WEB container is isolated, and other healthy WEB containers except the WEB container are used to manage the health status of the WEB container. The server bears the business traffic, wherein a WEB server is deployed on each WEB container; based on the second preset frequency, the intranet soft load balancer detects the health status of all APP containers, and for each APP container, when it is detected that the health status of the APP container is abnormal, the APP container is isolated, and the business traffic is borne by other healthy APP containers except the APP container, wherein an APP server is deployed on each APP container; based on the third preset frequency, the APP container detects the health status of the corresponding database, and when the health status of the corresponding database is abnormal, all APP containers in the APP group where the APP container is located are isolated, and the business traffic is borne by APP containers in other APP groups.

[0007] Optionally, the container management method based on the target application architecture also includes: based on a preset communication protocol, controlling the external network soft load balancer to establish a communication connection with all WEB servers, and all WEB servers to establish a communication connection with the intranet soft load balancer; controlling the intranet soft load balancer to establish a communication connection with all APP groups, and controlling each APP group to establish a communication connection with the corresponding database.

[0008] Optionally, the step of detecting that the health status of the WEB container or the APP container is abnormal includes: when the external network soft load balancer detects that the WEB container or the APP container does not exist, determining that the health status of the WEB container or the APP container is abnormal; or, when no response is received from the WEB container or the APP container within a specified time, determining that the health status of the WEB container or the APP container is abnormal, wherein when a WEB server or an APP server fails, the container where the server is located automatically dies.

[0009] Optionally, after isolating the WEB container or the APP container, it includes: controlling the external network soft load balancer to stop allocating business traffic to the isolated WEB container, and restarting the automatically destroyed WEB container; or controlling the internal network soft load balancer to stop allocating business traffic to the isolated APP container, and restarting the automatically destroyed APP container.

[0010] Optionally, the step of detecting that the health status of the database is abnormal includes: querying the database status flag of the database, and when the value of the database status flag indicates an abnormality, determining that the health status of the database is abnormal; when the query of the database status flag of the database fails, determining that the health status of the database is abnormal.

[0011] Optionally, after the APP container detects the health status of the corresponding database, it includes: when the health status of the corresponding database is abnormal, storing the abnormal record in the address information module of the APP container; based on a second preset frequency, the intranet soft load balancer queries the address information module, and when the abnormal record is queried, all APP containers in the APP group where the APP container is located are isolated based on the abnormal record.

[0012] Optionally, after isolating all APP containers in the APP group where the APP container is located, it includes: controlling the intranet soft load balancer to stop distributing business traffic to all APP containers in the isolated APP group, and restarting all APP containers that automatically die.

[0013] According to another aspect of an embodiment of the present invention, a container management device based on a target application architecture is also provided. The target application architecture includes: an intranet soft load balancer, multiple WEB containers, multiple APP groups and multiple databases, wherein each APP group includes multiple APP containers, all APP containers in the same APP group use one database, and different APP groups use different databases. The container management device includes: a first isolation unit, based on a first preset frequency, an external network soft load balancer detects the health status of all WEB containers, for each WEB container, when it is detected that the health status of the WEB container is abnormal, the WEB container is isolated, and other healthy WEB containers except the WEB container take over the business flow. A WEB server is deployed on each WEB container; a second isolation unit, based on a second preset frequency, the intranet soft load balancer detects the health status of all APP containers, for each APP container, when it is detected that the health status of the APP container is abnormal, the APP container is isolated, and the business traffic is borne by other healthy APP containers except the APP container, wherein an APP server is deployed on each APP container; a third isolation unit, based on a third preset frequency, the APP container detects the health status of the corresponding database, when the health status of the corresponding database is abnormal, all APP containers in the APP group where the APP container is located are isolated, and the business traffic is borne by APP containers in other APP groups.

[0014] Optionally, the container management device based on the target application architecture also includes: a first control module, which controls the external network soft load balancer to establish a communication connection with all WEB servers, and all WEB servers to establish a communication connection with the intranet soft load balancer based on a preset communication protocol; a second control module, which is used to control the intranet soft load balancer to establish a communication connection with all APP groups, and control each APP group to establish a communication connection with the corresponding database.

[0015] Optionally, the first isolation unit includes: a first determination module, used to determine that the health status of the WEB container or the APP container is abnormal when the external network soft load balancer detects that the WEB container or the APP container does not exist; a second determination module, used to determine that the health status of the WEB container or the APP container is abnormal when no response is received from the WEB container or the APP container within a specified time, wherein when a WEB server or an APP server fails, the container where the server is located automatically dies.

[0016] Optionally, the first isolation unit also includes: a third control module, used to control the external network soft load balancer to stop allocating business traffic to the isolated WEB container, and restart the WEB container that automatically disappears; a fourth control module, used to control the internal network soft load balancer to stop allocating business traffic to the isolated APP container, and restart the APP container that automatically disappears.

[0017] Optionally, the third isolation unit includes: a third determination module, used to query the database status identification bit of the database, and determine that the health status of the database is abnormal when the numerical value of the database status identification bit indicates an abnormality; a fourth determination module, used to determine that the health status of the database is abnormal when the query of the database status identification bit of the database fails.

[0018] Optionally, the third isolation unit also includes: a storage module, which is used to store abnormal records in the address information module of the APP container when the health status of the corresponding database is abnormal; an isolation module, which queries the address information module based on a second preset frequency by the intranet soft load balancer, and isolates all APP containers in the APP group where the APP container is located based on the abnormal records when abnormal records are queried.

[0019] Optionally, the third isolation unit also includes: a fifth control module, used to control the intranet soft load balancer to stop allocating business traffic to all APP containers in the isolated APP group, and restart all APP containers that automatically die.

[0020] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is further provided, wherein the computer-readable storage medium includes a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute any one of the above-mentioned container management methods based on the target application architecture.

[0021] According to another aspect of an embodiment of the present invention, there is also provided an electronic device, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any one of the above-mentioned container management methods based on the target application architecture.

[0022] According to another aspect of an embodiment of the present invention, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps of any one of the above-mentioned container management methods based on the target application architecture are implemented.

[0023] In the present disclosure, the target application architecture includes: an intranet soft load balancer, multiple WEB containers, multiple APP groups and multiple databases, wherein each APP group includes multiple APP containers, all APP containers in the same APP group use one database, and different APP groups use different databases. In this target application architecture, the WEB containers, APP groups and databases are deployed with functional peers, each peer node carries the same transactions, and when a node fails, other healthy nodes take over the business.

[0024] In the present disclosure, based on a first preset frequency, an external network soft load balancer detects the health status of all WEB containers. For each WEB container, when it is detected that the health status of the WEB container is abnormal, the WEB container is isolated, and other healthy WEB containers except the WEB container bear the business traffic. Secondly, based on a second preset frequency, an internal network soft load balancer detects the health status of all APP containers. For each APP container, when it is detected that the health status of the APP container is abnormal, the APP container is isolated, and other healthy APP containers except the APP container bear the business traffic. At the same time, Based on the third preset frequency, the APP container detects the health status of the corresponding database. When the health status of the corresponding database is abnormal, all APP containers in the APP group where the APP container is located are isolated, and the business traffic is borne by the APP containers in other APP groups, thereby realizing automatic detection and automatic isolation mechanism for WEB containers, APP groups and databases. When any node fails, other healthy nodes bear the business traffic, improving the self-healing ability and fault response speed of the system, and further solving the technical problem that the application architecture in the related technology lacks automatic detection and automatic isolation mechanism, resulting in late detection of faults and affecting the application performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0026] Figure 1 A hardware structure block diagram of a computer terminal (or mobile device) for implementing a container management method based on a target application architecture is shown;

[0027] Figure 2 is a flow chart of an optional container management method based on a target application architecture according to an embodiment of the present invention;

[0028] Figure 3is a schematic diagram of an optional target application architecture according to an embodiment of the present invention;

[0029] Figure 4 is a schematic diagram of an optional container management device based on a target application architecture according to an embodiment of the present invention;

[0030] Figure 5 It is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0031] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme 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 are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0032] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0033] It should be noted that the container management method and device based on the target application architecture in the present disclosure can be used in the field of cloud computing technology. When managing containers and databases based on the target application architecture, it can also be used in any field other than the field of cloud computing technology. When managing containers and databases based on the target application architecture, the present disclosure does not limit the application field of the container management method and device based on the target application architecture.

[0034] It should be noted that the information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) collected by this disclosure are information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data are in compliance with the relevant laws, regulations and standards of the relevant regions, necessary confidentiality measures are taken, and public order and good customs are not violated, and corresponding operation portals are provided for users to choose to authorize or refuse. For example, an interface is set up between this system and relevant users or organizations. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or organization.

[0035] It should be noted that in the present disclosure, when collecting and analyzing customer information, corresponding operation entrances are provided for users to choose to agree or reject the automated decision results; if the user chooses to reject, the expert decision-making process is entered.

[0036] The following embodiments of the present invention can be applied to various container-managed systems / applications / devices based on the target application architecture. The target application architecture in the present invention includes: an intranet soft load balancer, multiple WEB containers, multiple APP groups, and multiple databases, wherein each APP group includes multiple APP containers, and all APP containers in the same APP group use one database, and different APP groups use different databases. In this target application architecture, WEB containers, APP groups, and databases are functionally deployed in a peer-to-peer manner, and each peer node carries the same transaction. When a node fails, other healthy nodes take over the business, thereby improving the self-healing ability and performance of the system.

[0037] The present invention is described in detail below in conjunction with various embodiments.

[0038] Embodiment 1

[0039] According to an embodiment of the present invention, an embodiment of a container management method based on a target application architecture is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0040] The container management method embodiment based on the target application architecture provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1The hardware structure block diagram of a computer terminal (or mobile device) for implementing a container management method based on a target application architecture is shown. Figure 1 As shown, the computer terminal 10 (or mobile device) may include one or more ( Figure 1 The computer system includes a processor 102 (the processor 102 may include but is not limited to a microcontroller unit (MCU) or a field programmable gate array (FPGA)), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, the computer system may include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS), a network interface, a power supply and / or a camera. A person skilled in the art can understand that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0041] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0042] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the container management method based on the target application architecture in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the container management method based on the target application architecture is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0043] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0044] The display may be, for example, a touch screen liquid crystal display (LCD), which enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0045] Under the above operating environment, this application provides Figure 2 The container management method based on the target application architecture shown in FIG. It should be noted that the method is implemented based on the pre-built target application architecture. Figure 3 is a schematic diagram of an optional target application architecture according to an embodiment of the present invention, such as Figure 3 As shown in the figure, "client" refers to terminal devices such as mobile phones or computers held by users, "F5" is the network-side hardware load balancer, "external network SLB" and "intranet SLB" refer to the external network soft load balancer and the intranet soft load balancer respectively. The external network soft load balancer and the intranet soft load balancer are deployed in the external network environment and the intranet environment of the financial institution respectively. The functions of F5 and the external network soft load balancer include evenly distributing the business requests initiated by the client to the back-end WEB container cluster, and the function of the intranet soft load balancer includes evenly distributing the business requests to the APP cluster.

[0046] The target application architecture includes an intranet soft load balancer, multiple WEB containers, multiple APP groups, and multiple databases, where each APP group includes multiple APP containers. In the WEB container cluster, each WEB container is deployed in a peer-to-peer manner, that is, each WEB container is functionally equivalent, carries the same business requests, and supports horizontal expansion. Similarly, in the APP cluster, each APP cluster is functionally equivalent, and all APP containers in each APP cluster are functionally equivalent. In the database cluster, each database is functionally equivalent.

[0047] It should be noted that the APP cluster is also deployed in correspondence with the database, that is, one APP cluster uses one database, and the APP group and the corresponding database are called a node. For example, APP group 1 and database 1 are called node 1, and APP group N and database N are called node N. All APP containers in the same APP group use the same database. WEB containers support deployment in correspondence with APP groups and databases, and also support separate deployment of WEB container clusters, that is, WEB container clusters do not support establishing a corresponding relationship with nodes.

[0048] It should also be noted that Figure 3 In the communication protocol, HTTP / HTTPS (Hypertext Transfer Protocol / Hypertext Transfer Protocol Secure) is used between the client and F5, and the communication protocol between other components is TCP (Transmission Control Protocol).

[0049] Figure 2 is a flowchart of an optional container management method based on a target application architecture according to an embodiment of the present invention, such as Figure 2 As shown, the method comprises the following steps:

[0050] Step S201, based on the first preset frequency, the external network soft load balancer detects the health status of all WEB containers. For each WEB container, if it is detected that the health status of the WEB container is abnormal, the WEB container is isolated, and other healthy WEB containers except the WEB container bear the business traffic, wherein a WEB server is deployed on each WEB container.

[0051] In the embodiment of the present invention, based on the target application architecture, the external network soft load balancer executes a refined WEB container health status detection strategy according to the first preset frequency to continuously monitor all WEB containers. The first preset frequency can be set to once every 10 seconds, aiming to capture the operating status of the WEB container in real time and ensure that any abnormal status can be quickly discovered and responded to.

[0052] It should be noted that the WEB server is deployed on the PAAS (Platform as a Service) container to form a WEB container. A WEB server is deployed on each WEB container, and the deployed WEB servers are independent and stateless, which means that the abnormality of one container will not affect the normal operation of other containers. All WEB containers are mounted on the external network soft load balancer, and the health check policy of all WEB containers is configured in the external network soft load balancer.

[0053] For each WEB container, the external network soft load balancer will perform a deep health check and automatically identify the health status of the WEB container. When it detects that the health status of a WEB container is abnormal, the external network soft load balancer will immediately take action to isolate the WEB container. This means that the abnormal WEB container will no longer receive any new network requests, and its business processing capabilities will be suspended to prevent the failure from affecting the system.

[0054] After isolating the abnormal WEB container, other healthy WEB containers will automatically take over the business traffic of the isolated container. The external network soft load balancer rebalances the load and seamlessly forwards the business requests originally assigned to the faulty container to other healthy containers to ensure the continuity of application services. This process is automated and does not require manual intervention, thereby reducing RTO (Recovery Time Objective) and RPO (Recovery Point Objective), and improving the high availability and disaster recovery capabilities of the architecture system.

[0055] In step S202, based on the second preset frequency, the intranet soft load balancer detects the health status of all APP containers. For each APP container, if it is detected that the health status of the APP container is abnormal, the APP container is isolated, and other healthy APP containers except the APP container bear the business traffic, wherein an APP server is deployed on each APP container.

[0056] Based on the target application architecture, the embodiment of the present invention uses the intranet soft load balancer to perform a strict APP container health detection process according to the second preset frequency to continuously monitor all APP containers. The second preset frequency can be set to once every 10 seconds, aiming to capture the operating status of the WPP container in real time and ensure that any abnormal state can be quickly discovered and responded to.

[0057] It should be noted that the APP server is deployed on a PAAS (Platform as a Service) container to form an APP container. An APP server is deployed on each APP container, and the deployed APP servers are independent and stateless, which means that an abnormality in one container will not affect the normal operation of other containers. At the same time, in the embodiment of the present invention, the APP containers are deployed in groups, and each APP group includes multiple APP containers.

[0058] For each APP container, the intranet soft load balancer will perform a deep health check and automatically identify the health status of the APP container. When it detects that the health status of an APP container is abnormal, the intranet soft load balancer will immediately take action to isolate the APP container. This means that the abnormal APP container will no longer receive any new network requests, and its business processing capabilities will be suspended to prevent the failure from affecting the system.

[0059] After isolating the abnormal APP container, other healthy APP containers will automatically take on the business traffic of the isolated container. It should be noted that within an APP group, if one or more APP containers fail and are isolated, other healthy APP containers in the APP group can still operate normally. The intranet soft load balancer rebalances the load and seamlessly forwards the business requests originally assigned to the failed container to other healthy containers, thereby improving the high availability and disaster recovery capabilities of the architecture system.

[0060] Step S203: Based on the third preset frequency, the APP container detects the health status of the corresponding database. When the health status of the corresponding database is abnormal, all APP containers in the APP group where the APP container is located are isolated, and the business traffic is borne by the APP containers in other APP groups.

[0061] In the embodiment of the present invention, based on the target application architecture, the APP container executes a sophisticated database health detection mechanism at a third preset frequency to continuously monitor the database. The third preset frequency can be set to once a minute, aiming to capture the operation status of the database in real time and respond promptly at the early stage of a database failure to reduce the impact on application services.

[0062] It should be noted that the APP group and the database are deployed in correspondence, that is, one APP group uses one database, and all APP containers in the same APP group use the same database. Each database stores all transaction data, including transaction logs, market quotation information, etc. The databases are independent of each other and do not involve data synchronization.

[0063] Each APP container automatically identifies the health status of the corresponding database. When it is detected that the health status of the corresponding database is abnormal, the intranet soft load balancer immediately takes action to isolate all APP containers in the APP group where the APP container is located, that is, to isolate the APP group that uses the abnormal database. This means that all APP containers in the isolated APP group will no longer receive any new network requests, their business processing capabilities will be suspended, and the corresponding abnormal database will stop being used. At this time, the business traffic will be borne by the APP containers in other healthy APP groups, and the intranet soft load balancer will seamlessly forward the business requests originally assigned to the faulty container to other healthy containers by rebalancing the load.

[0064] In the embodiment of the present invention, there are two scenarios for APP container and database anomalies: one is the scenario where the APP container is abnormal and the database is normal. In this scenario, the abnormal APP container is isolated and the database runs normally; the other is the scenario where the database is abnormal. In this scenario, regardless of whether the APP container corresponding to the database is normal, all APP containers corresponding to the abnormal database, that is, all APP containers in the corresponding APP group, need to be isolated. The embodiment of the present invention improves the high availability and disaster recovery capabilities of the architecture system through these two isolation mechanisms.

[0065] Optionally, the container management method based on the target application architecture also includes: based on a preset communication protocol, controlling the external network soft load balancer to establish a communication connection with all WEB servers, and all WEB servers to establish a communication connection with the intranet soft load balancer; controlling the intranet soft load balancer to establish a communication connection with all APP groups, and controlling each APP group to establish a communication connection with the corresponding database.

[0066] In the target application architecture of the embodiment of the present invention, such as Figure 3 As shown in the figure, all WEB servers establish communication connections with the external network soft load balancer and the internal network soft load balancer respectively, and the communication protocol adopts the TCP protocol. Based on the communication protocol, the external network soft load balancer distributes the service request to the WEB container where the WEB server is located, and the WEB container then sends the service request to the internal network soft load balancer.

[0067] The intranet soft load balancer establishes communication connections with all APP groups, and each APP group establishes communication connections with the corresponding database. Based on the communication protocol, the intranet soft load balancer assigns business requests to the APP group where the APP server is located, and the APP group uses the database to execute the business logic corresponding to the business request.

[0068] Optionally, the step of detecting that the health status of the WEB container or the APP container is abnormal includes: when the external network soft load balancer detects that the WEB container or the APP container does not exist, determining that the health status of the WEB container or the APP container is abnormal; or, when no response is received from the WEB container or the APP container within a specified time, determining that the health status of the WEB container or the APP container is abnormal, wherein when a WEB server or an APP server fails, the container where the server is located automatically dies.

[0069] In steps S201 and S202, when a WEB container or APP container fails, the PAAS container will automatically die. When the external network soft load balancer detects the health status of the WEB container, it will send a detection instruction to the WEB container. If the detection instruction returns that the WEB container does not exist or the external network soft load balancer does not receive a response from the WEB container to the detection instruction within the threshold time, it is considered that the WEB container has failed and the health status is abnormal. At this time, the external network soft load balancer may take immediate action to isolate the abnormal WEB container.

[0070] Similarly, when the intranet soft load balancer detects the health status of the APP container, it will send a detection instruction to the APP container. If the detection instruction returns that the APP container does not exist or within the threshold time, the intranet soft load balancer does not receive a response from the WEB container to the detection instruction, it is considered that the APP container has failed and the health status is abnormal. At this time, the intranet soft load balancer may take immediate action to isolate the abnormal APP container.

[0071] Optionally, after isolating the WEB container or the APP container, it includes: controlling the external network soft load balancer to stop allocating business traffic to the isolated WEB container, and restarting the automatically destroyed WEB container; or controlling the internal network soft load balancer to stop allocating business traffic to the isolated APP container, and restarting the automatically destroyed APP container.

[0072] In steps S201 and S202, after isolating the WEB container, the external network soft load balancer stops allocating business traffic to the isolated WEB container, and other healthy WEB containers bear all business traffic. At the same time, the automatically dead WEB container is restarted and redeployed. After the WEB container recovers to a healthy state, the external network soft load balancer will re-incorporate the WEB container and restore its ability to normally receive and process business traffic.

[0073] Similarly, after isolating the APP container, the intranet soft load balancer stops allocating business traffic to the isolated APP container, and other healthy APP containers bear all business traffic. At the same time, the automatically dead APP container will be restarted and redeployed. After the APP container returns to a healthy state, the intranet soft load balancer will re-incorporate the APP container and restore its ability to normally receive and process business traffic.

[0074] The embodiments of the present invention can automatically identify and isolate faulty containers and automatically restart containers. The entire process does not require human intervention, thereby improving the response speed and recovery capability of the architecture system.

[0075] Optionally, the step of detecting that the health status of the database is abnormal includes: querying the database status flag of the database, and when the value of the database status flag indicates an abnormality, determining that the health status of the database is abnormal; when the query of the database status flag of the database fails, determining that the health status of the database is abnormal.

[0076] In an embodiment of the present invention, there is a database status detection device in each database. When the database crashes, file read and write errors, monitoring is unavailable, network connection fails, etc., the database status detection device sets the value of the database status identification bit of the database to 0. When the database is in a normal state, the value of the database status identification bit is 1.

[0077] In step S203, the APP container's database detection mechanism is manifested as querying the database status flag of the database. If the returned database status flag indicates an abnormality (that is, the value of the database status flag is 0), or the query instruction fails or reports an error, the health status of the database is considered to be abnormal and needs to be isolated.

[0078] Optionally, after the APP container detects the health status of the corresponding database, it includes: when the health status of the corresponding database is abnormal, storing the abnormal record in the address information module of the APP container; based on a second preset frequency, the intranet soft load balancer queries the address information module, and when the abnormal record is queried, all APP containers in the APP group where the APP container is located are isolated based on the abnormal record.

[0079] After the APP container detects that the health status of the corresponding database is abnormal, the abnormal record is stored in the address information module inside the APP container. The intranet soft load balancer will periodically query the address information module in the APP container, for example, based on the second preset frequency, and when the abnormal record is queried, the database abnormality information in the abnormal record is obtained, and the APP group corresponding to the database is isolated, that is, all APP containers in the APP group are isolated, and the business traffic is stopped from being distributed to the isolated APP group.

[0080] It should be noted that when querying the database exception information in the exception record, you can choose to isolate the corresponding APP group after querying the exception records of a certain database for multiple consecutive times.

[0081] Optionally, after isolating all APP containers in the APP group where the APP container is located, it includes: controlling the intranet soft load balancer to stop distributing business traffic to all APP containers in the isolated APP group, and restarting all APP containers that automatically die.

[0082] After isolating all APP containers in the APP group where the APP container is located, the intranet soft load balancer stops allocating business traffic to the isolated APP group, and other healthy APP groups bear all business traffic. At the same time, all automatically dead APP containers in the APP group are restarted, and the APP group is redeployed. After the APP group returns to a healthy state, the intranet soft load balancer will re-incorporate the APP group and restore its ability to normally receive and process business traffic.

[0083] It should be noted that the embodiment of the present invention also provides a method of manually isolating nodes, that is, an external terminal or an operation object can actively isolate a certain WEB container, APP container or database to facilitate daily maintenance of application services.

[0084] In an embodiment of the present invention, the target application architecture includes: an intranet soft load balancer, multiple WEB containers, multiple APP groups and multiple databases, wherein each APP group includes multiple APP containers, all APP containers in the same APP group use one database, and different APP groups use different databases. In this target application architecture, the WEB containers, APP groups and databases are all functionally deployed in a peer-to-peer manner, each peer node carries the same transactions, and when a node fails, other healthy nodes take over the business.

[0085] In the embodiment of the present invention, the external network soft load balancer detects the health status of all WEB containers based on the first preset frequency. For each WEB container, when it is detected that the health status of the WEB container is abnormal, the WEB container is isolated, and other healthy WEB containers except the WEB container bear the business traffic, thereby realizing automatic detection and automatic isolation of the WEB container.

[0086] Secondly, based on the second preset frequency, the intranet soft load balancer detects the health status of all APP containers. For each APP container, if it is detected that the health status of the APP container is abnormal, the APP container will be isolated, and other healthy APP containers except the APP container will bear the business traffic, thereby realizing automatic detection and automatic isolation of the APP container.

[0087] At the same time, based on the third preset frequency, the APP container detects the health status of the corresponding database. When the health status of the corresponding database is abnormal, all APP containers in the APP group where the APP container is located are isolated, and the APP containers in other APP groups bear the business traffic, thereby realizing automatic detection and automatic isolation of the database.

[0088] In the embodiment of the present invention, when a single node (WEB container, APP container and database) fails, other nodes will take over the business, which can cope with the failure of each node in the whole architecture system, and improve the high availability and high disaster recovery capabilities of the application service. By implementing the automatic detection and automatic isolation mechanism of the WEB container, APP group and database, when any node fails, other healthy nodes will bear the business traffic, which improves the self-healing ability and fault response speed of the system, and thus solves the technical problem that the application architecture lacks automatic detection and automatic isolation mechanism in the related technology, resulting in late detection of faults and affecting the performance of application use.

[0089] The following is a detailed description in conjunction with another embodiment.

[0090] Embodiment 2

[0091] A container management device based on a target application architecture provided in this embodiment includes a plurality of implementation units, each of which corresponds to each implementation step in the above-mentioned first embodiment.

[0092] Figure 4 is a schematic diagram of an optional container management device based on a target application architecture according to an embodiment of the present invention, such as Figure 4 As shown, the container management device based on the target application architecture may include: a first isolation unit 41 , a second isolation unit 42 , and a third isolation unit 43 .

[0093] Among them, the first isolation unit 41, based on the first preset frequency, uses the external network soft load balancer to detect the health status of all WEB containers. For each WEB container, if it is detected that the health status of the WEB container is abnormal, the WEB container is isolated, and other healthy WEB containers except the WEB container bear the business traffic, wherein a WEB server is deployed on each WEB container.

[0094] The second isolation unit 42, based on the second preset frequency, detects the health status of all APP containers by the intranet soft load balancer. For each APP container, when it is detected that the health status of the APP container is abnormal, the APP container is isolated, and other healthy APP containers except the APP container bear the business traffic, wherein an APP server is deployed on each APP container.

[0095] The third isolation unit 43 detects the health status of the corresponding database by the APP container based on the third preset frequency. When the health status of the corresponding database is abnormal, all APP containers in the APP group where the APP container is located are isolated, and the business traffic is borne by the APP containers in other APP groups.

[0096] In an embodiment of the present invention, the target application architecture includes: an intranet soft load balancer, multiple WEB containers, multiple APP groups and multiple databases, wherein each APP group includes multiple APP containers, all APP containers in the same APP group use one database, and different APP groups use different databases. In this target application architecture, the WEB containers, APP groups and databases are all functionally deployed in a peer-to-peer manner, each peer node carries the same transactions, and when a node fails, other healthy nodes take over the business.

[0097] The container management device based on the target application architecture can detect the health status of all WEB containers based on the first preset frequency by the first isolation unit 41, and for each WEB container, when it is detected that the health status of the WEB container is abnormal, the WEB container is isolated, and the business traffic is borne by other healthy WEB containers other than the WEB container. Secondly, the health status of all APP containers is detected by the intranet soft load balancer based on the second preset frequency by the second isolation unit 42. For each APP container, when it is detected that the health status of the APP container is abnormal, the APP container is isolated, and the business traffic is borne by other healthy APP containers other than the APP container. At the same time, through the third isolation unit 43, based on the third preset frequency, the APP container detects the health status of the corresponding database. When the health status of the corresponding database is abnormal, all APP containers in the APP group where the APP container is located are isolated, and the APP containers in other APP groups bear the business traffic, realizing automatic detection and automatic isolation mechanism for WEB containers, APP groups and databases. When any node fails, other healthy nodes bear the business traffic, which improves the self-healing ability and fault response speed of the system, thereby solving the technical problem that the application architecture in the related technology lacks automatic detection and automatic isolation mechanism, resulting in late discovery of faults and affecting the performance of application usage.

[0098] Optionally, the container management device based on the target application architecture also includes: a first control module, which controls the external network soft load balancer to establish a communication connection with all WEB servers, and all WEB servers to establish a communication connection with the intranet soft load balancer based on a preset communication protocol; a second control module, which is used to control the intranet soft load balancer to establish a communication connection with all APP groups, and control each APP group to establish a communication connection with the corresponding database.

[0099] Optionally, the first isolation unit 41 includes: a first determination module, used to determine that the health status of the WEB container or the APP container is abnormal when the external network soft load balancer detects that the WEB container or the APP container does not exist; a second determination module, used to determine that the health status of the WEB container or the APP container is abnormal when no response is received from the WEB container or the APP container within a specified time, wherein when a WEB server or an APP server fails, the container where the server is located automatically dies.

[0100] Optionally, the first isolation unit 41 also includes: a third control module, used to control the external network soft load balancer to stop allocating business traffic to the isolated WEB container, and restart the WEB container that automatically disappears; a fourth control module, used to control the internal network soft load balancer to stop allocating business traffic to the isolated APP container, and restart the APP container that automatically disappears.

[0101] Optionally, the third isolation unit 43 includes: a third determination module, used to query the database status identification bit of the database, and determine that the health status of the database is abnormal when the numerical value of the database status identification bit indicates an abnormality; a fourth determination module, used to determine that the health status of the database is abnormal when the query of the database status identification bit of the database fails.

[0102] Optionally, the third isolation unit 43 also includes: a storage module, which is used to store abnormal records in the address information module of the APP container when the health status of the corresponding database is abnormal; an isolation module, which queries the address information module based on the second preset frequency by the intranet soft load balancer, and isolates all APP containers in the APP group where the APP container is located based on the abnormal records when the abnormal records are queried.

[0103] Optionally, the third isolation unit 43 further includes: a fifth control module, used to control the intranet soft load balancer to stop allocating business traffic to all APP containers in the isolated APP group, and restart all APP containers that automatically die.

[0104] The above-mentioned container management device based on the target application architecture may also include a processor and a memory. The above-mentioned first isolation unit 41, the second isolation unit 42, the third isolation unit 43, etc. are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.

[0105] The processor includes a kernel, which retrieves the corresponding program unit from the memory. One or more kernels can be set, and the kernel parameters can be adjusted to manage containers and databases based on the target application architecture.

[0106] The above-mentioned memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one storage chip.

[0107] Embodiment 3

[0108] An embodiment of the present application may provide an electronic device, Figure 5 is a structural block diagram of an electronic device according to an embodiment of the present application. Figure 5 As shown, the electronic device may include: one or more ( Figure 5 (only one is shown) processor 502, memory 504, storage controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0109] Among them, the memory can be used to store software programs and modules, such as program instructions / modules corresponding to the methods and devices in the embodiments of the present application, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, realizing the above-mentioned method. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0110] The processor can call the information and application programs stored in the memory through the transmission device to perform the following steps: based on the first preset frequency, the external network soft load balancer detects the health status of all WEB containers. For each WEB container, when it is detected that the health status of the WEB container is abnormal, the WEB container is isolated, and the business traffic is borne by other healthy WEB containers except the WEB container, wherein a WEB server is deployed on each WEB container; based on the second preset frequency, the intranet soft load balancer detects the health status of all APP containers. For each APP container, when it is detected that the health status of the APP container is abnormal, the APP container is isolated, and the business traffic is borne by other healthy APP containers except the APP container, wherein an APP server is deployed on each APP container; based on the third preset frequency, the APP container detects the health status of the corresponding database. When the health status of the corresponding database is abnormal, all APP containers in the APP group where the APP container is located are isolated, and the business traffic is borne by APP containers in other APP groups.

[0111] The processor can also call the information and applications stored in the memory through the transmission device to perform the following steps: based on the preset communication protocol, control the external network soft load balancer to establish a communication connection with all WEB servers, and all WEB servers to establish a communication connection with the intranet soft load balancer; control the intranet soft load balancer to establish a communication connection with all APP groups, and control each APP group to establish a communication connection with the corresponding database.

[0112] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: when the external network soft load balancer detects that the WEB container or APP container does not exist, it determines that the health status of the WEB container or APP container is abnormal; or, when no response is received from the WEB container or APP container within a specified time, it determines that the health status of the WEB container or the APP container is abnormal, wherein when a WEB server or APP server fails, the container where the server is located automatically dies.

[0113] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: control the external network soft load balancer to stop allocating business traffic to the isolated WEB container, and restart the automatically terminated WEB container; or control the internal network soft load balancer to stop allocating business traffic to the isolated APP container, and restart the automatically terminated APP container.

[0114] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: query the database status identification bit of the database, and when the value of the database status identification bit indicates an abnormality, determine that the health status of the database is abnormal; when the query of the database status identification bit of the database fails, determine that the health status of the database is abnormal.

[0115] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: when the health status of the corresponding database is abnormal, the abnormal record is stored in the address information module of the APP container; based on the second preset frequency, the address information module is queried by the intranet soft load balancer, and when the abnormal record is queried, all APP containers in the APP group where the APP container is located are isolated based on the abnormal record.

[0116] The processor can also call the information and applications stored in the memory through the transmission device to perform the following steps: control the intranet soft load balancer to stop distributing business traffic to all APP containers in the isolated APP group, and restart all APP containers that automatically die.

[0117] By adopting the embodiment of the present application, a solution of a container management method based on a target application architecture is provided. Based on a first preset frequency, an external network soft load balancer detects the health status of all WEB containers. For each WEB container, when it is detected that the health status of the WEB container is abnormal, the WEB container is isolated, and other healthy WEB containers other than the WEB container bear the business traffic. Secondly, based on a second preset frequency, an internal network soft load balancer detects the health status of all APP containers. For each APP container, when it is detected that the health status of the APP container is abnormal, the APP container is isolated, and other healthy WEB containers other than the APP container bear the business traffic. Other healthy APP containers bear the business traffic. At the same time, based on the third preset frequency, the APP container detects the health status of the corresponding database. When the health status of the corresponding database is abnormal, all APP containers in the APP group where the APP container is located are isolated, and the APP containers in other APP groups bear the business traffic, thereby achieving the automatic detection and automatic isolation mechanism for WEB containers, APP groups and databases. When any node fails, other healthy nodes bear the business traffic, thereby solving the technical problem that the application architecture in the related technology lacks automatic detection and automatic isolation mechanism, resulting in late detection of faults and affecting application performance.

[0118] It can be understood by those skilled in the art that Figure 5 The structure shown is for illustration only, and the electronic device may also be a smart phone, a tablet computer, a PDA, a mobile Internet device (MID), a PAD or other terminal device. Figure 5 The structure of the electronic device is not limited. Figure 5 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 5 Different configurations are shown.

[0119] A person of ordinary skill in the art may understand that all or part of the steps in the various methods for managing containers based on the target application architecture in the above-mentioned embodiments may be completed by instructing hardware related to the terminal device through a program, and the program may be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0120] Embodiment 4

[0121] The embodiment of the present application further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the container management method based on the target application architecture provided in the first embodiment.

[0122] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is further provided, the computer-readable storage medium including a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute any one of the container management methods based on the target application architecture in the above-mentioned embodiment 1.

[0123] Optionally, in this embodiment, the above storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0124] The present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the container management method based on the target application architecture described in each embodiment of the present application.

[0125] The present application also provides a computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the container management method based on the target application architecture described in each embodiment of the present application are implemented.

[0126] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0127] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0128] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0129] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0130] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0131] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0132] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A container management method based on a target application architecture, characterized in that: The target application architecture includes: an intranet soft load balancer, multiple WEB containers, multiple APP groups and multiple databases, wherein each APP group includes multiple APP containers, all APP containers in the same APP group use one database, and different APP groups use different databases. The container management method includes: Based on the first preset frequency, the external network soft load balancer detects the health status of all the WEB containers. For each of the WEB containers, if it is detected that the health status of the WEB container is abnormal, the WEB container is isolated, and other healthy WEB containers other than the WEB container bear the business traffic, wherein a WEB server is deployed on each of the WEB containers; Based on the second preset frequency, the intranet soft load balancer detects the health status of all the APP containers. For each of the APP containers, if it is detected that the health status of the APP container is abnormal, the APP container is isolated, and other healthy APP containers other than the APP container bear the business traffic, wherein an APP server is deployed on each of the APP containers; Based on the third preset frequency, the APP container detects the health status of the corresponding database. When the health status of the corresponding database is abnormal, all APP containers in the APP group where the APP container is located are isolated, and the business traffic is borne by APP containers in other APP groups.

2. The container management method according to claim 1, characterized in that: Also includes: Based on a preset communication protocol, control the external network soft load balancer to establish a communication connection with all the WEB servers, and all the WEB servers to establish a communication connection with the internal network soft load balancer; Control the intranet soft load balancer to establish a communication connection with all the APP groups, and control each of the APP groups to establish a communication connection with the corresponding database.

3. The container management method according to claim 1, characterized in that: The step of detecting that the health status of the WEB container or the APP container is abnormal includes: When the external network soft load balancer detects that the WEB container or the APP container does not exist, it determines that the health status of the WEB container or the APP container is abnormal; or If no response is received from the WEB container or the APP container within a specified time, the health status of the WEB container or the APP container is determined to be abnormal, wherein when the WEB server or the APP server fails, the container where the server is located automatically dies.

4. The container management method according to claim 1, characterized in that: After isolating the WEB container or the APP container, the method includes: Control the external network soft load balancer to stop allocating service traffic to the isolated WEB container, and restart the automatically terminated WEB container; or, The intranet soft load balancer is controlled to stop allocating business traffic to the isolated APP container, and the automatically terminated APP container is restarted.

5. The container management method according to claim 1, characterized in that: The step of detecting that the health status of the database is abnormal comprises: querying a database status flag of the database, and determining that the health status of the database is abnormal when the value of the database status flag indicates that it is abnormal; In the case where the query of the database status flag of the database fails, it is determined that the health status of the database is abnormal.

6. The container management method according to claim 1, characterized in that: After the APP container detects the health status of the corresponding database, it includes: When the health status of the corresponding database is abnormal, the abnormal record is stored in the address information module of the APP container; Based on the second preset frequency, the intranet soft load balancer queries the address information module, and when the abnormal record is found, all APP containers in the APP group where the APP container is located are isolated based on the abnormal record.

7. The container management method according to claim 1, characterized in that: After isolating all APP containers in the APP group where the APP container is located, including: The intranet soft load balancer is controlled to stop allocating business traffic to all APP containers in the isolated APP group, and all APP containers that are automatically destroyed are restarted.

8. A container management device based on a target application architecture, characterized in that: The target application architecture includes: an intranet soft load balancer, multiple WEB containers, multiple APP groups and multiple databases, wherein each APP group includes multiple APP containers, all APP containers in the same APP group use one database, and different APP groups use different databases. The container management device includes: A first isolation unit, based on a first preset frequency, uses an external network soft load balancer to detect the health status of all the WEB containers, and for each of the WEB containers, when it is detected that the health status of the WEB container is abnormal, isolates the WEB container, and other healthy WEB containers other than the WEB container bear the business traffic, wherein a WEB server is deployed on each of the WEB containers; A second isolation unit, based on a second preset frequency, detects the health status of all the APP containers by the intranet soft load balancer, and for each of the APP containers, when it is detected that the health status of the APP container is abnormal, isolates the APP container, and other healthy APP containers except the APP container bear the business traffic, wherein an APP server is deployed on each of the APP containers; The third isolation unit detects the health status of the corresponding database by the APP container based on the third preset frequency. When the health status of the corresponding database is abnormal, all APP containers in the APP group where the APP container is located are isolated, and the business traffic is borne by the APP containers in other APP groups.

9. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the container management method based on the target application architecture as described in any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the container management method based on the target application architecture described in any one of claims 1 to 7 are implemented.

Images