CN115174365A - Method for realizing remote multi-activity platform - Google Patents
Method for realizing remote multi-activity platform Download PDFInfo
- Publication number
- CN115174365A CN115174365A CN202210790687.8A CN202210790687A CN115174365A CN 115174365 A CN115174365 A CN 115174365A CN 202210790687 A CN202210790687 A CN 202210790687A CN 115174365 A CN115174365 A CN 115174365A
- Authority
- CN
- China
- Prior art keywords
- data
- active
- activity
- component
- service
- 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
- 230000000694 effects Effects 0.000 title claims abstract description 27
- 238000000034 method Methods 0.000 title claims abstract description 20
- 238000012986 modification Methods 0.000 claims abstract description 4
- 230000004048 modification Effects 0.000 claims abstract description 4
- 238000005192 partition Methods 0.000 claims abstract description 4
- 238000012423 maintenance Methods 0.000 claims description 12
- 238000010276 construction Methods 0.000 claims description 4
- 230000002457 bidirectional effect Effects 0.000 claims description 3
- 238000011084 recovery Methods 0.000 abstract description 3
- 238000007789 sealing Methods 0.000 abstract 1
- 230000008602 contraction Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
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/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
-
- 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/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
-
- 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/08—Configuration management of networks or network elements
- H04L41/0876—Aspects of the degree of configuration automation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method for realizing a remote multi-live platform, which comprises the following steps: selecting a partition dimension: selecting a data dimension to be used as a data slice, thereby realizing that services can be separately deployed in different data centers; determining a modification range: selecting a service range related to the last selected data dimension to do more activities; and (3) unit sealing: calling is made to occur in the unit as much as possible, and cross-data center calling is avoided as much as possible; data that is not acceptable to be eventually consistent is written in a single point: for some data with extremely high real-time requirements, the final consistent data cannot be accepted and only single-point writing can be carried out. The invention solves the problem of disaster recovery by building a different-place multi-activity platform, improves the continuity of the service, and can quickly expand service units in other machine rooms or other regions when the capacity of the machine rooms or the regions is limited, thereby realizing the purpose of quick horizontal expansion.
Description
Technical Field
The invention relates to the technical field of computer wide area networks, in particular to a method for realizing a remote multi-activity platform.
Background
The English Multi-Site High Availability, as the name implies, is distributed at multiple sites in different places to provide services to the outside at the same time. The main difference from the traditional disaster recovery is that all sites in the multi-activity system are simultaneously served, and the following specific differences exist: the traditional disaster recovery center does not provide service at ordinary times, and whether the switching to the disaster recovery center can be successfully performed or not cannot be determined at key moment. The traditional disaster recovery center does not provide service at ordinary times, the whole disaster recovery resources are in a waste state, and the cost is high. The traditional disaster recovery center does not provide services at ordinary times, so that a data center providing services at ordinary times still stays in a single region, and when the volume of a service is large to a certain degree, the problem of resource bottleneck of the single region cannot be solved by the mode.
Therefore, a method for implementing a multi-live platform in different places is needed to solve the existing problems.
Disclosure of Invention
The invention aims to provide a method for realizing multiple remote platforms, which aims to solve the problems in the background technology.
In order to achieve the purpose, the invention provides the following technical scheme: a method for realizing a remote multi-live platform comprises the following steps:
s1, selecting a partition dimension: selecting a data dimension to be used as a data slice, thereby realizing that services can be separately deployed in different data centers;
s2, determining a modification range: selecting a service range related to the last selected data dimension to do more activities;
and (3) closing the unit S: calling is made to occur in the unit as much as possible, and calling across data centers is avoided as much as possible, on one hand, for user experience, the RT for local calling is shorter, and on the other hand, for stability, one data center is prevented from being affected by the other data centers;
s4, the data which is finally consistent cannot be accepted to be subjected to single-point writing: and some data which have extremely high real-time requirements and cannot accept final consistency can only be written in a single point.
Preferably, the remote multi-activity management and control platform comprises an access layer, an application layer and a data layer.
Preferably, the access layer is mainly a Tengine-based multi-active component called MSFE, the MSFE needs multi-unit deployment, can carry all unit front-end traffic, and routes to the back-end application of the correct unit according to the routing rule, and the multi-active console provides conventional operation and maintenance capabilities such as MSFE cluster new construction, capacity expansion, capacity reduction and the like.
Preferably, the application layer mainly comprises an EDAS-based RPC service component and an MQ-based message queue component, newly increased active parameters and processing logic of the EDAS support the multi-active RPC capability, during access, a service needs to declare the multi-active attribute of the RPC-Provider and upgrade the EDAS container version, RPC service intercommunication among units is realized through the cascade CSB component, issuing operation is performed on an MSHA management and control console, the ONS-based synchronization capability and the multi-active processing logic support the multi-active MQ capability, and during access, the unit attribute and the synchronization link configuration of the Producer and the Consumer need to be started in the multi-active management and control.
Preferably, the data layer mainly comprises a client and a multi-active component based on the DRDS, and the two cooperate to complete the management and control of the multi-active data layer.
Preferably, the DRDS multi-live component needs to be installed at a Server end of the DRDS, and is mainly matched with the multi-live Drvier to complete the logic processing of multi-live data in different places, and in addition to the components of the multi-live data layer, in order to complete multi-live data in different places, cloud products related to data synchronization need to be relied on, and based on the single/bidirectional synchronization capability of the DTS, the DRDS multi-live component is matched with multi-live management and control to complete the logic processing of data synchronization control of multi-live data in different places.
Compared with the prior art, the invention has the beneficial effects that:
(1) The invention solves the problem of disaster tolerance by building a multi-live platform in different places, improves the continuity of the service, and can rapidly expand service units in other machine rooms or other regions when the capacity of the machine rooms or the regions is limited, thereby achieving the purpose of rapid horizontal expansion;
(2) The operation and maintenance automation is realized, the automation of the change operation of the access layer, the service layer and the data layer and the automation of the operation and maintenance of the access layer cluster are mainly embodied, the operation and maintenance of the access layer cluster mainly comprise the creation of the cluster, the capacity expansion and reduction server, the capacity expansion and reduction SLB and the like, a one-key operation and maintenance change scheme is provided, and a server does not need to be logged in completely.
Drawings
FIG. 1 is a flow chart of the method steps of the present invention;
FIG. 2 is a block diagram of an extended service unit structure according to the present invention;
fig. 3 is a block diagram of a multi-activity management and control platform according to the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments.
Referring to fig. 1-3, an embodiment of the present invention is shown: a method for realizing a remote multi-live platform comprises the following steps:
s1, selecting a partition dimension: selecting a data dimension to be used as a data slice, thereby realizing that services can be separately deployed in different data centers;
s2, determining a modification range: selecting a service range related to the last selected data dimension to do more activities;
and (3) closing the unit S: calling is made to occur in the unit as much as possible, and calling across data centers is avoided as much as possible, on one hand, for user experience, the local calling RT is shorter, and on the other hand, for stability, one data center is prevented from being affected by problems and other data centers;
s4, the data which are finally consistent cannot be accepted to be subjected to single-point writing: for some data with extremely high real-time requirements, the final consistent data cannot be accepted and only single-point writing can be carried out.
Further, the remote multi-activity management and control platform comprises an access layer, an application layer and a data layer.
Furthermore, the access layer is mainly a Tengine-based multi-active component called as MSFE, the MSFE needs multi-unit deployment, can accept all unit front-end traffic and route to the back-end application of the correct unit according to the routing rule, and the multi-active console provides conventional operation and maintenance capabilities such as MSFE cluster new construction, capacity expansion, capacity reduction and the like.
Further, the application layer mainly comprises an EDAS-based RPC service component and an MQ-based message queue component, newly increased active parameters and processing logic of the EDAS support the multi-active RPC capability, during access, a service needs to declare the multi-active attribute of the RPC-Provider and upgrade the EDAS container version, RPC service intercommunication among units is realized through the cascade CSB component, issuing operation is carried out on an MSHA management and control platform, the ONS-based synchronization capability and the multi-active processing logic support the multi-active MQ capability, and during access, the unit attribute and the synchronous link configuration of the Producer and the Consumer need to be started in the multi-active management and control.
Furthermore, the data layer mainly comprises a client and a multi-active component based on the DRDS, and the client and the multi-active component cooperate to complete the control of the multi-active data layer.
Further, the DRDS multi-live component needs to be installed at the Server side of the DRDS, and is mainly matched with the multi-live Drvier to complete the logic processing of multi-live data in different places, and in addition to the components of the multi-live data layer, in order to complete multi-live data in different places, cloud products related to data synchronization need to be relied on, and based on the single/bidirectional synchronization capability of the DTS, the DRDS multi-live component is matched with multi-live management and control to complete the logic processing of data synchronization control of multi-live data in different places.
The working principle is as follows: when the remote multi-activity management and control platform is used, one data dimension is selected to be used as data slicing, so that services can be separately deployed in different data centers, a service range related to the last selected data dimension is selected to be used as much as possible, calling is performed in the unit as much as possible, calling across the data centers is avoided as much as possible, on one hand, for user experience, RT (remote terminal) is called locally and on the other hand, stability is achieved, one data center is prevented from having problems, other data centers are affected, requirements on real-time performance are extremely high, the final consistent data cannot be accepted, and only single-point writing can be performed, the remote multi-activity management and control platform comprises an access layer, an application layer and a data layer, the access layer is mainly a multi-activity component based on Tengine and is called as MSFE, the MSFE needs multi-unit deployment, can bear front-end flow of all units and can be routed to a rear-end application of a correct unit according to routing rules, the multi-active control platform provides conventional operation and maintenance capabilities such as MSFE cluster new construction, capacity expansion, capacity reduction and the like, the application layer mainly comprises an RPC service component based on EDAS and a message queue component based on MQ, newly increased active parameters and processing logic of EDAS support the multi-active RPC capability, when accessing, a service needs to declare the multi-active attribute of RPC-Provider and upgrade the EDAS container version, RPC service intercommunication among units is realized by cascading CSB components, issuing operation is carried out on the MSHA control platform, the synchronization capability and the multi-active processing logic based on ONS support the multi-active MQ capability, when accessing, the unit attribute and synchronous link configuration of Producer and Consumer need to be started in multi-active management and control, the data layer mainly comprises a client and a multi-active component based on DRDS, the client and the multi-active component are matched together to complete management and control of a multi-active data layer, the DRDS multi-active component needs to be installed at a Server end of the DRDS, and is matched with the multi-active Drvier to complete multi-active logic processing in different places, in addition to the components of the multi-activity data layer, in order to complete multi-activity in different places, cloud products related to data synchronization are needed, based on single/two-way synchronization capability of a DTS, data synchronization control logic processing of multi-activity in different places is completed by being matched with multi-activity management and control, full automation of operation and maintenance is achieved, automation of change operation of an access layer, a service layer and a data layer and full automation of operation and maintenance of an access layer cluster are mainly reflected, on the aspect of operation and maintenance of the access layer cluster, a capacity expansion and contraction server, a capacity expansion and contraction SLB and the like are mainly included, a one-button operation and maintenance change scheme is provided, and a server does not need to be logged in any case.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.
Claims (6)
1. A method for realizing remote multi-live platform is characterized by comprising the following steps:
s1, selecting a partition dimension: selecting a data dimension to slice data, thereby realizing that services can be separately deployed in different data centers;
s2, determining a modification range: selecting a service range related to the last selected data dimension to do more activities;
and (3) closing the unit S: calling is made to occur in the unit as much as possible, and calling across data centers is avoided as much as possible, on one hand, for user experience, the RT for local calling is shorter, and on the other hand, for stability, one data center is prevented from being affected by the other data centers;
s4, the data which is finally consistent cannot be accepted to be subjected to single-point writing: for some data with extremely high real-time requirements, the final consistent data cannot be accepted and only single-point writing can be carried out.
2. The method of claim 1, wherein the method comprises the following steps: the allopatric multi-activity management and control platform comprises an access layer, an application layer and a data layer.
3. The method of claim 2, wherein the method comprises the following steps: the access layer is mainly a Tengine-based multi-active component called MSFE, the MSFE needs multi-unit deployment, can bear all unit front-end traffic and route to the back-end application of the correct unit according to the routing rule, and the multi-active console provides conventional operation and maintenance capabilities such as MSFE cluster new construction, capacity expansion, capacity reduction and the like.
4. The method of claim 2, wherein the method comprises the following steps: the application layer mainly comprises an RPC service component based on EDAS and a message queue component based on MQ, newly increased active parameters and processing logic of the EDAS support the multi-active RPC capability, during access, a service needs to declare the multi-active attribute of the RPC-Provider and upgrade the EDAS container version, RPC service intercommunication among units is realized through a cascade CSB component, and issuing operation is carried out on an MSHA management and control console, the synchronization capability based on ONS and the multi-active processing logic support the multi-active MQ capability, and during access, the unit attribute and the synchronization link configuration of a Producer and a Consumer need to be started in the multi-active management and control.
5. The method of claim 2, wherein the method comprises the following steps: the data layer mainly comprises a client and a multi-active component based on the DRDS, and the client and the multi-active component cooperate to complete control over the multi-active data layer.
6. The method of claim 5, wherein the method comprises the following steps: the DRDS multi-activity component needs to be installed at a Server end of the DRDS, mainly cooperates with a multi-activity Drvier to finish off-site multi-activity logic processing, and besides the multi-activity data layer component, in order to finish off-site multi-activity, the DRDS multi-activity component also needs to depend on cloud products related to data synchronization, and cooperates with multi-activity management and control to finish off-site multi-activity data synchronization control logic processing based on single/bidirectional synchronization capability of the DTS.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210790687.8A CN115174365A (en) | 2022-07-05 | 2022-07-05 | Method for realizing remote multi-activity platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210790687.8A CN115174365A (en) | 2022-07-05 | 2022-07-05 | Method for realizing remote multi-activity platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115174365A true CN115174365A (en) | 2022-10-11 |
Family
ID=83490465
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210790687.8A Pending CN115174365A (en) | 2022-07-05 | 2022-07-05 | Method for realizing remote multi-activity platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115174365A (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109819004A (en) * | 2017-11-22 | 2019-05-28 | 中国人寿保险股份有限公司 | For disposing the method and system at more live data centers |
-
2022
- 2022-07-05 CN CN202210790687.8A patent/CN115174365A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109819004A (en) * | 2017-11-22 | 2019-05-28 | 中国人寿保险股份有限公司 | For disposing the method and system at more live data centers |
Non-Patent Citations (1)
| Title |
|---|
| 天秤座的架构师: "阿里资深架构师推荐：浅谈异地多活及阿里云容灾经验分享", CSDN, 4 July 2020 (2020-07-04), pages 5 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Hou et al. | Edge intelligence for mission-critical 6G services in space-air-ground integrated networks | |
| CN112671882B (en) | Same-city double-activity system and method based on micro-service | |
| CN109819004B (en) | Method and system for deploying multi-activity data centers | |
| CN110083662B (en) | Double-living framework construction method based on platform system | |
| RU2606058C2 (en) | Improved reserve management system and method for implementation thereof | |
| CN112003716A (en) | Data center dual-activity implementation method | |
| CN111612466A (en) | Consensus and resource transmission method, device and storage medium | |
| KR102232364B1 (en) | Method of Updating Edge Application with Seamless Service in Micro Service Edge Application | |
| CN110535924B (en) | Rail transit server communication method and system | |
| CN116401225A (en) | Distributed file system oriented to satellite cloud | |
| CN105827678A (en) | High-availability framework based communication method and node | |
| Tang et al. | Slicing-based software-defined mobile edge computing in the air | |
| CN111258760A (en) | Platform management method, system, device and storage medium | |
| CN115174365A (en) | Method for realizing remote multi-activity platform | |
| JP2012150567A (en) | Resource reservation device, method and program | |
| CN101667980B (en) | Method and system for realizing metropolitan connection of Internet data center | |
| CN113179228B (en) | Method, device, equipment and medium for improving switch stacking reliability | |
| CN109302319A (en) | Message pool distributed type assemblies and its management method | |
| KR0175456B1 (en) | Distributed Object Access Information Management System and Its Decentralization Method | |
| KR102205593B1 (en) | Decision Methods of Edge Servers in a Relational Edge Cloud Environment | |
| JPH04311251A (en) | Multiprocessor system | |
| CN209134427U (en) | A kind of vehicle-mounted command communications system of complete disaster tolerance | |
| CN115967611A (en) | Cross-domain switching processing method, device, equipment and storage medium | |
| CN114785849A (en) | Application high-availability method realized based on multi-level node network | |
| CN114398203A (en) | Cloud disaster recovery system, method, electronic device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |