CN114143323A - Enterprise-level micro-service platform cross-regional disaster recovery architecture and method - Google Patents
Enterprise-level micro-service platform cross-regional disaster recovery architecture and method Download PDFInfo
- Publication number
- CN114143323A CN114143323A CN202111439762.8A CN202111439762A CN114143323A CN 114143323 A CN114143323 A CN 114143323A CN 202111439762 A CN202111439762 A CN 202111439762A CN 114143323 A CN114143323 A CN 114143323A
- Authority
- CN
- China
- Prior art keywords
- environment
- production environment
- city
- service
- business
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention provides a cross-regional disaster recovery architecture and a cross-regional disaster recovery method for an enterprise-level micro-service platform, and relates to the technical field of disaster recovery. The architecture comprises: the network flow configuration device, the registration center, the configuration center, the authentication center, the monitoring center and the management platform are all configured to be shared by a production environment and a city environment and used for configuring corresponding network flow for the business micro-service of the production environment and/or the city environment, providing node registration, corresponding configuration information, uniformly authenticating, collecting and recording indexes and uniformly managing. Through the functional intercommunication of the production environment and the city-sharing environment, the problems that when some or all nodes of a certain service microservice are down, systems cannot be switched flexibly, and manual intervention is needed when the service unavailable time is too long can be solved.
Description
Technical Field
The invention relates to the technical field of disaster tolerance, in particular to a cross-regional disaster tolerance architecture and a cross-regional disaster tolerance method for an enterprise-level micro-service platform.
Background
Under the rapid development of information technology, internet companies and manufacturers increasingly pay attention to the construction of system disaster tolerance. Disaster recovery backup is divided into data-level disaster recovery and application-level disaster recovery if divided according to the application. And in the data level disaster tolerance, when a local data disaster occurs, the system at least stores a piece of available key service data in a different place. The application-level disaster recovery backup is to establish completely same applications in a production environment and a same-city environment, the two applications are combined into a double-active system, when a disaster occurs in the production environment application, the application in the same-city environment can take over the service of the production environment, and after the production environment system is normally used, the service is migrated again to the production environment. The biggest difference between application level disaster recovery and data level disaster recovery is whether the same city system takes over the services of the production system when the production system has a disaster, so that the continuity of the services is ensured, and the problem is also the key solution of the application level disaster recovery.
In the actual production environment of an enterprise, when some micro-service part of nodes or all nodes are down, if the prior art scheme is used for processing the problem that the service is unavailable, two problems can occur: firstly, when operation and maintenance personnel find problems and manually switch flow distribution, long-time service is unavailable, and production accidents are caused in serious cases; and secondly, when the machine room configuration items of the registration center are used, whether all the nodes in the same city are involved in the service can not be flexibly controlled.
Disclosure of Invention
In order to overcome the defects of the prior art, the invention provides a cross-regional disaster recovery architecture and a cross-regional disaster recovery method for an enterprise-level micro service platform, which can realize the function intercommunication between a production environment and a city environment and are beneficial to solving the problem that when some or all nodes of a certain service micro service part are down, systems cannot be switched flexibly.
In order to solve the technical problems, the technical scheme adopted by the invention is as follows:
in a first aspect, the present invention provides a cross-regional disaster recovery architecture for an enterprise-level microservice platform, wherein the architecture comprises:
the network traffic configuration device is configured to be shared by a production environment and a city-sharing environment and is used for configuring corresponding network traffic to the production environment and/or the city-sharing environment; a registry configured to be shared by a production environment and a city-wide environment for registering with a business microservice providing node of the production environment and/or the city-wide environment;
the configuration center is shared by the production environment and the same city environment and is used for providing corresponding configuration information under the monitoring of business microservices of the production environment and/or the same city environment;
the authentication center is configured to be shared by a production environment and a city-sharing environment and is used for performing unified authentication on business micro-services of the production environment and/or the city-sharing environment;
the monitoring center is configured to be shared by a production environment and a city-sharing environment and used for collecting and recording indexes of the production environment and/or the city-sharing environment during the operation of business microservices;
a management platform configured to be shared by the production environment and the same city environment for unified management of the business microservices of the production environment and/or the same city environment.
Optionally, the network traffic configuration apparatus includes a load balancer and a gateway; wherein:
and the load balancer forwards the flow to the gateway in the preset working state according to the working state of the gateway.
Optionally, the gateway has a characteristic of preferentially accessing the same environment, and preferentially accesses the business microservices of the production environment or the same city environment corresponding to the gateway of the production environment or the same city environment.
Optionally, the node data of the registry are synchronized with each other, and all the business microservices of the production environment and/or the same city environment are registered with the registry node.
Optionally, the configuration center may uniformly configure the business microservices of the production environment and/or the city-sharing environment, and uniformly manage and control the configuration.
Optionally, the authentication center interacts with the authentication center to verify transaction validity and ensure security of transactions between microservices, when requesting for the service microservices in the production environment and/or the same city environment each time.
Optionally, the monitoring center collects and displays the running indexes of the business microservices in the production environment and/or the city environment so as to check the running state of the business microservices in real time.
Optionally, the management platform includes:
the service governance of the business microservice of the production environment and/or the same city environment;
and uniformly managing the information of each component of the business microservices of the production environment and/or the city environment.
In a second aspect, the present invention provides a method for disaster recovery across regions of an enterprise-level microservice platform, where the method includes:
configuring, by a network traffic configuration device shared by a production environment and a metropolitan environment, corresponding network traffic to the production environment and/or the metropolitan environment;
registering with a business microservice providing node of a production environment and/or a city environment through a registry shared by the production environment and the city environment;
providing corresponding configuration information under the monitoring of business microservices of the production environment and/or the city environment through a configuration center shared by the production environment and the city environment; performing unified authentication on the business micro-services of the production environment and/or the city environment through an authentication center shared by the production environment and the city environment;
acquiring and recording indexes of the production environment and/or the city environment during the operation of the business microservices through a monitoring center shared by the production environment and the city environment;
and uniformly managing the business micro-services of the production environment and/or the same city environment through a management platform shared by the production environment and the same city environment.
Optionally, wherein:
in the state that partial nodes of the first type of service micro-service in the production environment or the same city environment are down, other types of service micro-services in the production environment or the same city environment can access nodes of the first type of service micro-service which are not down or access the first type of service micro-service nodes in the same city environment or the production environment; or
In a state that all nodes of a first type of service micro service in the production environment or the same city environment are down, other types of service micro services in the production environment or the same city environment can access the first type of service micro service nodes in the same city environment or the production environment; or
And in the state that all nodes of the production environment and the same city environment are communicated, the mixed calling based on flow ratio among different environments is supported during business micro-service interaction.
According to the scheme provided by the invention, the load balancing method based on the Ribbon component used when the service micro-services access each other is rewritten by reconstructing the software development kit depended on by the service system, the area affinity switch is added, the key fields such as the special identification are added to the production environment and the same city environment, and the fields can be updated to the metadata of the registration center in real time when being modified, so that the configuration is timely validated, the residual node pressure can be reduced when the nodes of the production environment are partially crashed, the flow can be quickly and automatically switched to the nodes of the same city environment when all the nodes are crashed, and the problems that the system cannot be flexibly switched and manual intervention is needed when the service unavailable time is too long are solved.
Drawings
FIG. 1 is a schematic diagram of the operation of a prior art architecture;
FIG. 2 is a schematic diagram illustrating the operation of the architecture of an embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating a partial node downtime for processing a business microservice by applying an embodiment of the present invention;
FIG. 4 is a schematic diagram illustrating a total node downtime for processing a business microservice according to an embodiment of the present invention;
FIG. 5 is a diagram illustrating the handling of a hybrid call in which embodiments of the present invention are implemented;
FIG. 6 is a schematic diagram illustrating a processing of a gateway downtime according to an embodiment of the present invention;
FIG. 7 is a schematic diagram illustrating a processing of a downtime of a registry according to an embodiment of the present invention;
FIG. 8 is a schematic diagram illustrating processing and configuring a central downtime according to an embodiment of the present invention;
fig. 9 is a schematic diagram of processing downtime of a gateway, a registry, and a configuration center according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the drawings of the embodiments of the present invention. It is to be understood that the embodiments described are only a few embodiments of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the described embodiments of the invention without any inventive step, are within the scope of protection of the invention.
Unless defined otherwise, technical or scientific terms used herein shall have the ordinary meaning as understood by one of ordinary skill in the art to which this invention belongs. The use of "first," "second," and similar terms in the present application do not denote any order, quantity, or importance, but rather the terms are used to distinguish one element from another. The word "comprising" or "comprises", and the like, means that the element or item listed before the word covers the element or item listed after the word and its equivalents, but does not exclude other elements or items. The terms "connected" or "coupled" and the like are not restricted to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "upper", "lower", "left", "right", and the like are used merely to indicate relative positional relationships, and when the absolute position of the object being described is changed, the relative positional relationships may also be changed accordingly.
In the prior art, when some micro-service part node or all nodes are down, two problems can occur: firstly, when operation and maintenance personnel find problems and manually switch flow distribution, long-time service is unavailable, and production accidents are caused in serious cases; and secondly, when the computer room of the registration center is used for configuring items, whether all nodes in the same city are involved in the service can not be flexibly controlled.
According to the scheme provided by the invention, the load balancing method based on the Ribbon component used when the service micro-services access each other is rewritten by reconstructing the software development kit depended on by the service system, the area affinity switch is added, the key fields such as the special identification are added to the production environment and the same city environment, and the fields can be updated to the metadata of the registration center in real time when being modified, so that the configuration is timely validated, the residual node pressure can be reduced when the nodes of the production environment are partially crashed, the flow can be quickly and automatically switched to the nodes of the same city environment when all the nodes are crashed, and the problems that the system cannot be flexibly switched and manual intervention is needed when the service unavailable time is too long are solved.
Various embodiments of the present invention are described in detail below.
As shown in fig. 1, in the prior art, when architecture modification is not performed, in the same service area (service channel area), components in a production environment and a same city environment belong to different clusters, and serve service microservices in the respective environments respectively. The business micro-service in the production environment can only pull the business micro-service node list of the production environment from the registration center in the production environment, and the configuration center, the authentication center, the monitoring center and the management platform are similar and only serve the business micro-service in the production environment. Furthermore, in a production environment, when the flow reaches other types of business microservices from a consumer to a load balancer and a gateway, if the other types of business microservices have the requirement of calling the first type of business microservices, the other types of business microservices can only serve to find the first type of business microservices in the same environment, and under the condition that the first type of business microservices are normal, a calling link is normal, and the business is normally carried out. As shown, the load balancer herein for the prior art or in various embodiments of the present application may be identified by F5. In a production environment, a same city environment, other classes of business microservices may be defined as business microservices a and a first class of business microservices may be defined as business microservices B. Different service classes can be represented by the service microservice a and the service microservice B, and different nodes corresponding to the service microservices can also be represented, which is not limited herein.
Further, if some nodes of the business micro-service B are down, the remaining available nodes continue to provide services, but the remaining nodes have high pressure, which causes all nodes of the business micro-service B to be down, and the business micro-service a cannot find the available business micro-service B, which causes service interruption, thereby causing the unavailable time of the services to be too long.
Further, the business microservice a works as the called party, and is not described herein again.
As a solution, an embodiment of the present application can provide a cross-regional disaster recovery architecture of an enterprise-level micro service platform, including:
the network traffic configuration device is configured to be shared by a production environment and a city-sharing environment and is used for configuring corresponding network traffic to the production environment and/or the city-sharing environment;
a registry configured to be shared by a production environment and a city-wide environment for registering with a business microservice providing node of the production environment and/or the city-wide environment;
the configuration center is shared by the production environment and the same city environment and is used for providing corresponding configuration information under the monitoring of business microservices of the production environment and/or the same city environment;
the authentication center is configured to be shared by a production environment and a city-sharing environment and is used for performing unified authentication on business micro-services of the production environment and/or the city-sharing environment;
the monitoring center is configured to be shared by a production environment and a city-sharing environment and used for collecting and recording indexes of the production environment and/or the city-sharing environment during the operation of business microservices;
a management platform configured to be shared by the production environment and the same city environment for unified management of the business microservices of the production environment and/or the same city environment.
In some embodiments, the network traffic configuration apparatus comprises a load balancer and a gateway; wherein:
and the load balancer forwards the flow to the gateway in the preset working state according to the working state of the gateway.
Among other things, the load balancer may be configured to use the F5 scheme, which builds on an existing network architecture, providing an inexpensive, efficient, and transparent way to extend the bandwidth of network devices and servers, increase throughput, enhance network data processing capabilities, and increase network flexibility and availability. It should be noted that: the load balancing device is not an underlying network device but a performance optimization device. For network applications, load balancing is not required at the beginning, and when the access volume of the network applications is increased and a single processing unit cannot meet the load requirement, the network application traffic will become a bottleneck, and the load balancing plays a role.
In some embodiments, the gateway has a preference for access to the environment, and the gateway corresponding to the production environment or the same city environment has a preference for access to the business microservices of the production environment or the same city environment.
Load balancing has two meanings: on one hand, the operation of single heavy load is shared by a plurality of node devices for parallel processing, after the processing of each node device is finished, the results are gathered and returned to the user, and the system processing capacity is greatly improved (clustering technology). On the other hand, a large amount of concurrent access or data traffic is shared by a plurality of node devices to be processed respectively, so that the time for a user to wait for response is reduced, and the method is mainly used for Web applications such as a Web server, an FTP server and an enterprise key application server.
In some embodiments of the present invention, as shown in fig. 2, the modified architecture merges the respective registration center clusters of the production environment and the same-city environment into one cluster, and the business microservices of the production environment and the same-city environment can serve to discover all business microservice instance information in the whole business area;
further, a configuration center, an authentication center and a monitoring center cluster are also combined into a cluster to manage and monitor all the micro-services and the instance nodes;
furthermore, the management platforms are combined, and all the business micro-service instances are managed on one background.
Furthermore, fields such as production city environment identifiers, regional affinity switches and the like are added in the SDK jar packet depended by the business microservice, the configuration information is uniformly managed and controlled on the management platform, and the configuration information is immediately pushed to the metadata of the business microservice of the registry after being modified.
Furthermore, when the service micro-service A calls the service micro-service B, the service micro-service A pulls all available service micro-service B instance information according to a load balancing algorithm rewritten in the SDK jar packet, and then selects a proper available service micro-service B instance from instance nodes of all the service micro-service B in a production environment and a city environment according to a region affinity switch and a flow ratio carried in metadata of a registration center of the service micro-service B for access.
Further, the node data of the registry are synchronized with each other, and all the business microservices of the production environment and/or the city environment are registered with the registry node. Specifically, the registry uses eureka components in a Spring Cloud technical framework, key fields such as a specific identifier are added to a production environment and a city environment by rewriting a load balancing method based on Ribbon components used when service micro-services access each other, and an area affinity switch is added, and the fields can be updated into metadata of the registry in real time when modified, so that configuration can take effect in time, and therefore when a part of nodes of the production environment are down, the pressure of the remaining nodes is reduced, and when all the nodes are down, the flow is quickly and automatically switched to the nodes of the city environment.
The Spring Cloud is an ordered set of a series of frames, development of infrastructure of the distributed system is ingeniously simplified by using development convenience of the Spring book, and one-key starting and deployment can be achieved by using development style of the Spring book, such as service discovery registration, configuration center, message bus, load balancing, circuit breaker, data monitoring and the like. The registration mechanism of each embodiment of the application combines the service frameworks which are perfect and have high recognition degree in the field by using the Spring Cloud, avoids repeated configuration, and encapsulates and shields complex configuration and implementation principles by the Spring Boot style, so that a set of distributed system development toolkits which are simple and easy to understand, deploy and maintain is output.
Further, the configuration center may uniformly configure the business microservices of the production environment and/or the city environment, and uniformly manage and control the configuration. Specifically, the configuration center mainly uses an open source apollo technical framework, can uniformly configure the business microservices, uniformly manage and control the configuration, after the business microservices use the configuration center, a configuration can be established in the configuration center, and the business microservices A can monitor the change of the configuration, so as to perform hot update operation on some configurations of the business microservices A, thereby achieving the capacity of uniform management and control, equivalently putting the same information together for maintenance, and avoiding repeated labor.
Apollo (Apollo) is an open-source production-level configuration center product, can be used for centrally managing the configuration of different environments and different clusters, can be pushed to an application end in real time after configuration modification, has the characteristics of standard authority, process management and the like, and is suitable for a micro-service configuration management scene.
Furthermore, the authentication center mainly interacts with the authentication center when requesting business micro-services of the production environment and/or the same city environment each time, verifies the transaction validity, and ensures the security of transactions among micro-services. Specifically, the authentication center uses OAuth2.0 authentication technology to mainly perform unified authentication on the business micro-services, and each request of the micro-services interacts with the authentication center to verify the validity of the transaction and ensure the security of the transaction between the micro-services.
Wherein OAuth2.0 is a continuation version of the OAuth protocol. The authentication mechanism of the embodiments of the present application may adopt OAuth2.0 to pay attention to the simplicity of the client developer, and may represent the user by organizing approved interactions between the resource owner and the HTTP facilitator, or may allow the third party application to obtain access rights on behalf of the user. Meanwhile, in some embodiments, a special authentication flow may be provided for various terminal devices that users may face, such as Web applications, desktop applications, and mobile phones.
Furthermore, the monitoring center collects and displays the running indexes of the business microservices of the production environment and/or the city environment so as to check the running state of the business microservices in real time. Specifically, the monitoring center adopts an open source Prometheus technical framework, collects indexes of the service micro-service during operation and displays the indexes through a Grafana front-end technical framework, collected information of Prometheus comprises transaction time consumption, transaction times, transaction failure rate and fusing of the service micro-service, monitoring and collection of information of a micro-service server CPU, a memory, a database thread pool, a micro-service JVM and the like, and technical personnel can be helped to check the operation state of the service micro-service in real time.
Among them, the Prometheus technical framework provides a multidimensional data model and a flexible query language: combining the monitoring data in any dimension by associating the monitoring indexes with a plurality of tags (tags); providing an HTTP query interface; the data can be conveniently displayed by combining the components such as Grafana and the like, and Grafana can be used for data monitoring and data statistics and has seven characteristics of visualization, alarming, notification, dynamic instrument panel, mixed data source, annotation and filter.
Further, the management platform comprises: the service governance of the business microservice of the production environment and/or the same city environment; and uniformly managing the information of each component of the business microservices of the production environment and/or the city environment. Specifically, the management platform is also called a business microservice unified management platform, and mainly performs unified management on business microservices, including service management of the business microservices and unified management of information of each component of the business microservice management platform (API gateway, registration center, configuration center, authentication center, monitoring center); the service management aspect provides functions of micro-service API interface authentication, IP white list, micro-service fusing, micro-service interaction authority, flow weight, gray level and the like.
As a solution, in combination with the foregoing, an embodiment of the present application can provide a cross-regional disaster recovery method for an enterprise-level microservice platform, including:
configuring, by a network traffic configuration device shared by a production environment and a metropolitan environment, corresponding network traffic to the production environment and/or the metropolitan environment;
registering with a business microservice providing node of a production environment and/or a city environment through a registry shared by the production environment and the city environment;
providing corresponding configuration information under the monitoring of business microservices of the production environment and/or the city environment through a configuration center shared by the production environment and the city environment; performing unified authentication on the business micro-services of the production environment and/or the city environment through an authentication center shared by the production environment and the city environment;
acquiring and recording indexes of the production environment and/or the city environment during the operation of the business microservices through a monitoring center shared by the production environment and the city environment;
and uniformly managing the business micro-services of the production environment and/or the same city environment through a management platform shared by the production environment and the same city environment.
In some embodiments of the present invention, in a state that some nodes of the first type of service microservices in the production environment or the same city environment are down, other types of service microservices in the production environment or the same city environment can access nodes of the first type of service microservices which are not down or access the first type of service microservices nodes in the same city environment or the production environment.
In some embodiments of the present invention, in a state that all nodes of the first type of service microservices in the production environment or the same city environment are down, other types of service microservices in the production environment or the same city environment can access the first type of service microservices nodes in the same city environment or the production environment.
In some embodiments of the present invention, in a state where the production environment is connected to all nodes of the same city environment, the business microservice supports mixed call based on flow ratio between different environments during interaction.
Referring to fig. 3 for example, when a business microservice performs interaction, it supports a priority access with the environment, and when a part of nodes of a business microservice B in a production environment goes down, a business microservice a accesses the remaining surviving nodes of the business microservice B;
further, when the business microservice has a large access amount, the microservice can be manually configured on the management platform to support mixed call of different environments, that is, the business microservice a of the production environment can simultaneously access the remaining business microservice B of the production environment and all the business microservices B of the same city environment.
In some embodiments of the present invention, referring to fig. 4, when the business microservice B of the production environment is all down, the business microservice a of the production environment automatically accesses the surviving nodes of the business microservice B of the same city environment.
In some embodiments of the present invention, referring to fig. 5, by configuring the area affinity switch of the service and the traffic proportion when accessed in the management platform, the business microservice B of the production environment and the same city environment is called according to the traffic proportion or not when called.
In some embodiments of the present invention, referring to fig. 6, before forwarding traffic to a gateway, an F5 load balancer will detect whether the gateway is alive, an F5 load balancer only forwards traffic to the alive gateway, and an F5 load balancer of a production environment forwards traffic to the gateway of the production environment by default;
further, when the gateway of the same city environment is down, the F5 load balancer of the same city environment forwards traffic to the gateway of the production environment, and the business microserver of the production environment continues to provide services.
In some embodiments of the present invention, referring to fig. 7, after the architecture is modified, the production environment and the co-city environment registration centers are merged into a cluster, each registration center node is a Peer node (data is synchronized with each other), which can be regarded as that all the business microservices of the production environment and the co-city environment are registered with each registration center node, when the registration center of the co-city environment goes down, the registration center of the production environment still has full business microservices information, and the business microservices are registered with the production environment registration center nodes when they continue to offer, and the production environment registration center can continue to provide services.
In some embodiments of the present invention, referring to fig. 8, configuration information of a full amount of service microservices is stored in both the production environment and the configuration center in the same city environment, and when the configuration center in the same city environment goes down, the configuration center in the production environment may continue to provide services;
further, the functions of the configuration center have been described in the previous embodiments, and are not described herein again.
In some embodiments of the present invention, referring to fig. 9, when a gateway, a registry, and a configuration center in the same city environment are down, an F5 load balancer forwards traffic to the gateway in the production environment, and the micro service of the production environment and the micro service of the service in the same city environment can both continue to use the registry and the configuration center in the production environment, so that calls between service systems are not affected, and the micro service nodes in the same city environment can continue to provide services, so that service continuity can be still ensured and disaster tolerance can be enhanced in a case where all the micro service components in one environment are down.
In summary, the cross-regional disaster recovery system and method provided by the invention can realize the function intercommunication between the production environment and the same city environment, and are beneficial to solving the problems that when some or all nodes of a certain service microservice are down, the system cannot be flexibly switched, and when the service unavailable time is too long, manual intervention is required.
In some embodiments, a processor executing computer-executable instructions may be a processing device including more than one general-purpose processing device, such as a microprocessor, Central Processing Unit (CPU), Graphics Processing Unit (GPU), or the like. More specifically, the processor may be a Complex Instruction Set Computing (CISC) microprocessor, Reduced Instruction Set Computing (RISC) microprocessor, Very Long Instruction Word (VLIW) microprocessor, processor running other instruction sets, or processors running a combination of instruction sets. The processor may also be one or more special-purpose processing devices such as an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Digital Signal Processor (DSP), a system on a chip (SoC), or the like.
In some embodiments, the computer-readable storage medium may be a memory, such as a read-only memory (ROM), a random-access memory (RAM), a phase-change random-access memory (PRAM), a static random-access memory (SRAM), a dynamic random-access memory (DRAM), an electrically erasable programmable read-only memory (EEPROM), other types of random-access memory (RAM), a flash disk or other form of flash memory, a cache, a register, a static memory, a compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD) or other optical storage, a tape cartridge or other magnetic storage device, or any other potentially non-transitory medium that may be used to store information or instructions that may be accessed by a computer device, and so forth.
In some embodiments, the computer-executable instructions may be implemented as a plurality of program modules that collectively implement the method for displaying medical images according to any one of the present disclosure.
The present disclosure describes various operations or functions that may be implemented as or defined as software code or instructions. The display unit may be implemented as software code or modules of instructions stored on a memory, which when executed by a processor may implement the respective steps and methods.
Such content may be source code or differential code ("delta" or "patch" code) that may be executed directly ("object" or "executable" form). A software implementation of the embodiments described herein may be provided through an article of manufacture having code or instructions stored thereon, or through a method of operating a communication interface to transmit data through the communication interface. A machine or computer-readable storage medium may cause a machine to perform the functions or operations described, and includes any mechanism for storing information in a form accessible by a machine (e.g., a computing display device, an electronic system, etc.), such as recordable/non-recordable media (e.g., Read Only Memory (ROM), Random Access Memory (RAM), magnetic disk storage media, optical storage media, flash memory display devices, etc.). The communication interface includes any mechanism for interfacing with any of a hardwired, wireless, optical, etc. medium to communicate with other display devices, such as a memory bus interface, a processor bus interface, an internet connection, a disk controller, etc. The communication interface may be configured by providing configuration parameters and/or transmitting signals to prepare the communication interface to provide data signals describing the software content. The communication interface may be accessed by sending one or more commands or signals to the communication interface.
The computer-executable instructions of embodiments of the present disclosure may be organized into one or more computer-executable components or modules. Aspects of the disclosure may be implemented with any number and combination of such components or modules. For example, aspects of the disclosure are not limited to the specific computer-executable instructions or the specific components or modules illustrated in the figures and described herein. Other embodiments may include different computer-executable instructions or components having more or less functionality than illustrated and described herein.
The above description is intended to be illustrative and not restrictive. For example, the above-described examples (or one or more versions thereof) may be used in combination with each other. For example, other embodiments may be used by those of ordinary skill in the art upon reading the above description. In addition, in the foregoing detailed description, various features may be grouped together to streamline the disclosure. This should not be interpreted as an intention that a disclosed feature not claimed is essential to any claim. Rather, the subject matter of the present disclosure may lie in less than all features of a particular disclosed embodiment. Thus, the following claims are hereby incorporated into the detailed description as examples or embodiments, with each claim standing on its own as a separate embodiment, and it is contemplated that these embodiments may be combined with each other in various combinations or permutations. The scope of the disclosure should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
The above embodiments are merely exemplary embodiments of the present disclosure, which is not intended to limit the present disclosure, and the scope of the present disclosure is defined by the claims. Various modifications and equivalents of the disclosure may occur to those skilled in the art within the spirit and scope of the disclosure, and such modifications and equivalents are considered to be within the scope of the disclosure.
Claims (10)
1. An enterprise-level micro-service platform cross-regional disaster recovery architecture, characterized in that the architecture comprises:
the network traffic configuration device is configured to be shared by a production environment and a city-sharing environment and is used for configuring corresponding network traffic to the production environment and/or the city-sharing environment;
a registry configured to be shared by a production environment and a city-wide environment for registering with a business microservice providing node of the production environment and/or the city-wide environment;
the configuration center is shared by the production environment and the same city environment and is used for providing corresponding configuration information under the monitoring of business microservices of the production environment and/or the same city environment;
the authentication center is configured to be shared by a production environment and a city-sharing environment and is used for performing unified authentication on business micro-services of the production environment and/or the city-sharing environment;
the monitoring center is configured to be shared by a production environment and a city-sharing environment and used for collecting and recording indexes of the production environment and/or the city-sharing environment during the operation of business microservices;
a management platform configured to be shared by the production environment and the same city environment for unified management of the business microservices of the production environment and/or the same city environment.
2. The architecture of claim 1, wherein the network traffic configuration means comprises a load balancer and a gateway; wherein:
and the load balancer forwards the flow to the gateway in the preset working state according to the working state of the gateway.
3. The architecture of claim 2, wherein the gateway has a preference for access to the environment corresponding to a production environment or a co-located environment.
4. The architecture according to claim 3, characterized in that the nodes of the registry are mutually synchronized in data, all the business microservices of the production environment and/or of the same city environment being registered with the registry node.
5. The architecture of claim 4, wherein the configuration center can uniformly configure the business microservices of the production environment and/or the same city environment, and uniformly manage the configuration.
6. The architecture of claim 5, wherein the authentication center mainly interacts with the authentication center every time a business microservice of the production environment and/or the same city environment is requested, so as to verify transaction validity and ensure security of transactions among microservices.
7. The framework of claim 6, wherein the monitoring center collects and displays the running indexes of the business microservices of the production environment and/or the same city environment so as to check the running state of the business microservices in real time.
8. The architecture of claim 7, wherein the management platform comprises:
the service governance of the business microservice of the production environment and/or the same city environment;
and uniformly managing the information of each component of the business microservices of the production environment and/or the city environment.
9. An enterprise-level micro-service platform cross-regional disaster recovery method is characterized by comprising the following steps:
configuring, by a network traffic configuration device shared by a production environment and a metropolitan environment, corresponding network traffic to the production environment and/or the metropolitan environment;
registering with a business microservice providing node of a production environment and/or a city environment through a registry shared by the production environment and the city environment;
providing corresponding configuration information under the monitoring of business microservices of the production environment and/or the city environment through a configuration center shared by the production environment and the city environment; performing unified authentication on the business micro-services of the production environment and/or the city environment through an authentication center shared by the production environment and the city environment;
acquiring and recording indexes of the production environment and/or the city environment during the operation of the business microservices through a monitoring center shared by the production environment and the city environment;
and uniformly managing the business micro-services of the production environment and/or the same city environment through a management platform shared by the production environment and the same city environment.
10. The cross-regional disaster recovery method of claim 9, wherein:
in the state that partial nodes of the first type of service micro-service in the production environment or the same city environment are down, other types of service micro-services in the production environment or the same city environment can access nodes of the first type of service micro-service which are not down or access the first type of service micro-service nodes in the same city environment or the production environment; or
In the state that all nodes of the first type of service microservices in the production environment or the same city environment are down, other types of service microservices in the production environment or the same city environment can access the first type of service microservices nodes in the same city environment or the production environment; or
And in the state that all nodes of the production environment and the same city environment are communicated, the mixed calling based on flow ratio among different environments is supported during business micro-service interaction.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111439762.8A CN114143323A (en) | 2021-11-30 | 2021-11-30 | Enterprise-level micro-service platform cross-regional disaster recovery architecture and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111439762.8A CN114143323A (en) | 2021-11-30 | 2021-11-30 | Enterprise-level micro-service platform cross-regional disaster recovery architecture and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114143323A true CN114143323A (en) | 2022-03-04 |
Family
ID=80389397
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111439762.8A Pending CN114143323A (en) | 2021-11-30 | 2021-11-30 | Enterprise-level micro-service platform cross-regional disaster recovery architecture and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114143323A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116633993A (en) * | 2023-07-25 | 2023-08-22 | 中邮消费金融有限公司 | Cross-network micro-service calling method, device, equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018201832A1 (en) * | 2017-05-04 | 2018-11-08 | 中兴通讯股份有限公司 | Data migration method and system for distributed cache database |
| CN109976952A (en) * | 2019-04-09 | 2019-07-05 | 苏州浪潮智能科技有限公司 | The method and apparatus of cross-domain backup in cloud computing system |
| CN112671882A (en) * | 2020-12-18 | 2021-04-16 | 上海安畅网络科技股份有限公司 | Same-city double-activity system and method based on micro-service |
-
2021
- 2021-11-30 CN CN202111439762.8A patent/CN114143323A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018201832A1 (en) * | 2017-05-04 | 2018-11-08 | 中兴通讯股份有限公司 | Data migration method and system for distributed cache database |
| CN109976952A (en) * | 2019-04-09 | 2019-07-05 | 苏州浪潮智能科技有限公司 | The method and apparatus of cross-domain backup in cloud computing system |
| CN112671882A (en) * | 2020-12-18 | 2021-04-16 | 上海安畅网络科技股份有限公司 | Same-city double-activity system and method based on micro-service |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116633993A (en) * | 2023-07-25 | 2023-08-22 | 中邮消费金融有限公司 | Cross-network micro-service calling method, device, equipment and storage medium |
| CN116633993B (en) * | 2023-07-25 | 2023-10-10 | 中邮消费金融有限公司 | Cross-network micro-service calling method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107301048B (en) | Internal control management system of application response type shared application architecture | |
| US20190068690A1 (en) | Automated management of resource attributes across network-based services | |
| US9672053B2 (en) | Service request processing | |
| US8805984B2 (en) | Multi-operational transactional access of in-memory data grids in a client-server environment | |
| US8825817B1 (en) | Using a template to update a stack of resources | |
| CN109542611A (en) | Database, that is, service system, database dispatching method, equipment and storage medium | |
| US9626223B2 (en) | Provisioning IaaS services | |
| CN111800462B (en) | Micro service instance processing method, micro service instance processing device, computer equipment and storage medium | |
| WO2021190360A1 (en) | Virtualized resource scheduling system and method in vehicle diagnostic cloud platform | |
| CN111064626B (en) | Configuration updating method, device, server and readable storage medium | |
| CN105740469B (en) | Storage server and metadata access method | |
| CN114826869B (en) | Device management method and device management system | |
| WO2017054533A1 (en) | External resource management method, apparatus and system through cloud interworking | |
| CN116016667A (en) | Unified management method and system for multiple types of registries of cloud native platform | |
| CN116800825A (en) | Calling method, device, equipment and medium based on micro-service splitting | |
| US9350738B2 (en) | Template representation of security resources | |
| CN113794652A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN114143323A (en) | Enterprise-level micro-service platform cross-regional disaster recovery architecture and method | |
| CN115086166A (en) | Computing system, container network configuration method, and storage medium | |
| US20240061854A1 (en) | Dynamic filter and projection push down | |
| CN115834668B (en) | Cluster node control method, device, equipment, storage medium and program product | |
| CN116647552A (en) | Service processing method and system in heterogeneous micro-service cluster, terminal and storage medium | |
| CN106559454B (en) | Resource access method, device and system | |
| CN106302733A (en) | A kind of distributed type assemblies merges implementation method and the device of NFS protocol | |
| CN107453950A (en) | A kind of information processing method and monitoring system |
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 |