CN108156013A - A kind of Page Service disaster recovery method, device and electronic equipment - Google Patents
A kind of Page Service disaster recovery method, device and electronic equipment Download PDFInfo
- Publication number
- CN108156013A CN108156013A CN201611110778.3A CN201611110778A CN108156013A CN 108156013 A CN108156013 A CN 108156013A CN 201611110778 A CN201611110778 A CN 201611110778A CN 108156013 A CN108156013 A CN 108156013A
- Authority
- CN
- China
- Prior art keywords
- page
- service
- history
- rendering
- access request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
-
- 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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
-
- 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/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- 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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
This application discloses three kinds of Page Service disaster recovery methods, device and electronic equipment and a kind of Page Service disaster tolerance systems.Wherein, the Page Service disaster tolerance system when service availability problem occur in other services that page rendering service relies on, can render the local disk caching of the page, high in the clouds backup offer degradation disaster tolerance service by being stored with history；When page rendering services itself appearance exception, the history that high in the clouds stores can be obtained by Web server and renders the page, to provide degradation disaster tolerance service；When availability failure occurs in full page rendering service cluster, it can be backed up by high in the clouds and content delivery network service device provides disaster tolerance of revealing all the details, therefore, can may have access to effective guarantee page quick response.
Description
Technical field
This application involves disaster tolerance technology fields, and in particular to a kind of Page Service disaster recovery method, device and electronic equipment.This
Application is related to other two kinds of Page Service disaster recovery methods, device and electronic equipment and a kind of Page Service disaster tolerance system simultaneously.
Background technology
In large Web application development technique field, in order to reduce the workload of front end developer, front and rear end is detached
Development, there is the development scheme that page code is write based on template instruction, for example, the meeting-place active page in this year double 11
Page code is mostly write in this way.When user accesses this page based on template, need to be provided by server
Page rendering service, has thus aggravated server stress.
By taking the active page of double 11 meeting-place as an example, such webpage carries commodity sales promotion diversion function, is that the shopping of consumer enters
Mouthful, therefore, the visit capacity that will generate ten million or even hundred million grades during activity.In the case of big visit capacity high concurrent, server
The page rendering service at end will bear huge pressure, be likely to occur the situation for the machine of delaying at any time.Therefore, how to research and develop out
A kind of Page Service disaster tolerance mode, can ensure page quick response and may have access to become those skilled in the art there is an urgent need to
It solves the problems, such as.
Invention content
The application provides a kind of Page Service disaster recovery method device and electronic equipment, to solve prior art page response speed
The slow even not addressable problem of degree.The application in addition provide two kinds of Page Service disaster recovery methods, device and electronic equipment and
A kind of Page Service disaster tolerance system.
The application provides a kind of Page Service disaster recovery method, which is characterized in that including：
Receive the access request for user's specified page；
Judge whether the load of page rendering service reaches preset load threshold；It is specified if so, obtaining the user
The history of the page renders the page, if it is not, then obtaining real-time wash with watercolours by user's specified page described in page rendering service real-time rendering
Contaminate the page；
The rendering page that initiator's loopback to the access request obtains.
Optionally, it before whether the load for judging page rendering service reaches preset load threshold, further includes：
Judge whether the page rendering service can be used；If so, enter in next step, if it is not, then being obtained by Web server
The history of user's specified page is taken to render the page, and enters the wash with watercolours that initiator's loopback to the access request obtains
The step of contaminating the page.
Optionally, the history for obtaining user's specified page renders the page, including：
It obtains the history being locally stored and renders the page；
If the history being locally stored, which has not been obtained, renders the page, the history for obtaining high in the clouds storage renders the page.
Optionally, the history for obtaining high in the clouds storage renders the page, including：
It obtains the history stored in the primary storage device in high in the clouds and renders the page；
If the history stored in the primary storage device, which has not been obtained, renders the page, high in the clouds spare storage device is obtained
The history of middle storage renders the page.
Optionally, it after user's specified page described in the real-time rendering, further includes：
The real-time rendering page is stored in local memory device, the page is rendered as the history being locally stored；With
And by real-time rendering page storage beyond the clouds storage device, the history as high in the clouds storage renders the page.
Optionally, it is described to store the real-time rendering page in storage device beyond the clouds, in the following way：
It will be in real-time rendering page storage beyond the clouds primary storage device；And the real-time rendering page is deposited
Storage is beyond the clouds in spare storage device.
Optionally, the access request is asked including encrypted access.
In addition the application provides a kind of Page Service disaster tolerance device, including：
Access request receiving unit, for receiving the access request for user's specified page；
Judging unit is overloaded, for judging whether the load of page rendering service reaches preset load threshold；If so,
Start history and render page acquiring unit, if it is not, then starting page rendering unit；
History renders page acquiring unit, and the page is rendered for obtaining the history of user's specified page；
Page rendering unit, for by user's specified page described in page rendering service real-time rendering, obtaining real-time wash with watercolours
Contaminate the page；
Page loopback cell is rendered, for the rendering page of initiator's loopback acquisition of the access request.
In addition the application provides a kind of electronic equipment, including：
Processor；And
Memory, for storing the program for realizing Page Service disaster recovery method, which is powered and passes through the processor
After the program for running the Page Service disaster recovery method, following step is performed：Receive the access request for user's specified page；Sentence
Whether the load of disconnected page rendering service reaches preset load threshold；If so, obtain the history of user's specified page
The page is rendered, if it is not, then servicing user's specified page described in real-time rendering by page rendering, obtains the real-time rendering page；To
The rendering page that initiator's loopback of the access request obtains.
In addition the application provides a kind of Page Service disaster recovery method, including：
Receive the access request for user's specified page that client is sent；
Judge that the local history for whether storing the user's specified page for meeting preset limitation rules renders the page；If
It is then to obtain the history to render the page, if it is not, the access request then is sent to content source server, and described in reception
The rendering page of user's specified page of content source server loopback；
The rendering page that initiator's loopback to the access request obtains.
Optionally, it is described the access request is sent to content source server before, further include：
The determining content source server for wanting Hui Yuan.
Optionally, the content source server for determining to want Hui Yuan, in the following way：
According at least one content source server respectively with running the distance between equipment of the method, determine to want Hui Yuan
Content source server.
Optionally, if the content source server is unavailable, the content source server for wanting Hui Yuan is redefined, and by institute
It states access request and is sent to the content source server redefined.
Optionally, if content source server cluster is unavailable, it is determined that the cloud storage service device of Hui Yuan, and by the visit
Ask that request is sent to determining cloud storage service device, and the user for receiving the determining cloud storage service device loopback specifies
The history of the page renders the page.
Optionally, if the determining cloud storage service device is unavailable, the cloud storage service device for wanting Hui Yuan is redefined,
And the access request is sent to the cloud storage service device redefined.
Optionally, the rendering page of the user's specified page for receiving the content source server loopback it
Afterwards, it further includes：
Store the rendering page received.
Optionally, the access request is asked including encrypted access.
In addition the application provides a kind of Page Service disaster tolerance device, including：
Access request receiving unit, for receiving the access request for user's specified page of client transmission；
Acquiring unit is judged, for judging locally whether store the user's specified page for meeting preset limitation rules
History render the page；If so, start page acquiring unit, if it is not, then starting back source unit；
The page acquiring unit renders the page for obtaining the history；
Described time source unit for the access request to be sent to content source server, and receives the content source clothes
The rendering page of user's specified page of business device loopback；
Page loopback cell, for the rendering page obtained to initiator's loopback of the access request.
In addition the application provides a kind of electronic equipment, including：
Processor；And
Memory, for storing the program for realizing Page Service disaster recovery method, which is powered and passes through the processor
After the program for running the Page Service disaster recovery method, following step is performed：Receive client transmission is directed to user's specified page
Access request；Judge that the local history for whether storing the user's specified page for meeting preset limitation rules renders page
Face；If so, obtaining the history renders the page, if it is not, the access request then is sent to content source server, and receive
The rendering page of user's specified page of the content source server loopback；Initiator's loopback to the access request obtains
The rendering page obtained.
In addition the application provides a kind of Page Service disaster recovery method, including：
Receive the access request for user's specified page；
The history for obtaining user's specified page renders the page；
The history that initiator's loopback to the access request obtains renders the page.
Optionally, the history for obtaining user's specified page renders the page, including：
It obtains the history stored in primary storage device and renders the page；
If the history stored in the primary storage device, which has not been obtained, renders the page, obtain in spare storage device and deposit
The history of storage renders the page.
Optionally, the access request is asked including encrypted access.
In addition the application provides a kind of Page Service disaster tolerance device, including：
Access request receiving unit, for receiving the access request for user's specified page；
The page acquiring unit renders the page for obtaining the history of user's specified page；
Page loopback cell, the history for being obtained to initiator's loopback of the access request render the page.
In addition the application provides a kind of electronic equipment, including：
Processor；And
Memory, for storing the program for realizing Page Service disaster recovery method, which is powered and passes through the processor
After the program for running the Page Service disaster recovery method, following step is performed：Receive the access request for user's specified page；It obtains
The history of user's specified page is taken to render the page；The history that initiator's loopback to the access request obtains renders page
Face.
In addition the application provides a kind of Page Service disaster tolerance system, which is characterized in that including：Content source server cluster,
Content delivery network node cluster and cloud storage service device cluster, the content source server dispose the first above-mentioned Page Service
Disaster tolerance device, the content delivery network node dispose above-mentioned second of Page Service disaster tolerance device, the cloud storage service device
Dispose the third above-mentioned Page Service disaster tolerance device.
Compared with prior art, the application has the following advantages：
It is available to there is service in other services that page rendering service relies on for the Page Service disaster tolerance system that the application provides
During sex chromosome mosaicism, the local disk caching of the page, high in the clouds backup offer degradation disaster tolerance service can be rendered by being stored with history；
When page rendering services itself appearance exception, the history that high in the clouds stores can be obtained by Web server and renders the page, with offer
Degradation disaster tolerance service；When availability failure occurs in full page rendering service cluster, high in the clouds can be passed through and backed up and content point
Hair network server provides disaster tolerance of revealing all the details, and therefore, can be may have access to effective guarantee page quick response.
Description of the drawings
Fig. 1 is the flow chart of the embodiment for the first Page Service disaster recovery method that the application provides；
Fig. 2 is the system architecture schematic diagram of the embodiment for the first Page Service disaster recovery method that the application provides；
Fig. 3 is the schematic diagram of the embodiment for the first Page Service disaster tolerance device that the application provides；
Fig. 4 is the schematic diagram of the embodiment for the first electronic equipment that the application provides；
Fig. 5 is the flow chart of the embodiment for second of Page Service disaster recovery method that the application provides；
Fig. 6 is the system architecture schematic diagram of the embodiment for second of Page Service disaster recovery method that the application provides；
Fig. 7 is the schematic diagram of the embodiment for second of Page Service disaster tolerance device that the application provides；
Fig. 8 is the schematic diagram of the embodiment for second of electronic equipment that the application provides；
Fig. 9 is the flow chart of the embodiment for the third Page Service disaster recovery method that the application provides；
Figure 10 is the schematic diagram of the embodiment for the third Page Service disaster tolerance device that the application provides；
Figure 11 is the schematic diagram of the embodiment for the third electronic equipment that the application provides；
Figure 12 is a kind of schematic diagram of the embodiment for Page Service disaster tolerance system that the application provides；
The access link schematic diagram of the embodiment for the first Page Service disaster recovery method that Figure 13 the application provides.
Specific embodiment
Many details are elaborated in the following description in order to fully understand the application.But the application can be with
Much implement different from other manner described here, those skilled in the art can be in the situation without prejudice to the application intension
Under do similar popularization, therefore the application is not limited by following public specific implementation.
In this application, three kinds of Page Service disaster recovery methods, device and electronic equipment and a kind of Page Service are provided
Disaster tolerance system.It is described in detail one by one in the following embodiments.
The Page Service disaster recovery method that the application provides, the basic thought of core are：By to content source server
Page rendering service carries out load dynamic regulation, the history of local cache is made full use of to render the page, the history wash with watercolours that high in the clouds stores
The page is contaminated, reduces the rendering load of page rendering service routine, ensures the stability of page rendering service.
It please refers to Fig.1, is the flow chart of the first Page Service disaster recovery method embodiment of the application.The method packet
Include following steps：
Step S101：Receive the access request for user's specified page.
The access request can be directed to the access request of subscription client or from preposition
CDN (Content Delivery Network, content distributing network) node access request (also referred to as return source request), example
Such as, in some scenarios, in order to ensure that user can be accessed the newest page in time, for example activity publication, price appear, the second
It kills, caching and the user terminal caching of CDN requires instant actual effect, needs to return the page that source obtains latest edition again, this
In the case of, the access request of subscription client will go back to sources to content source server by CDN, i.e.,：Run the side that the application provides
The server of method.
The access request, can be the access request of http protocol or encrypted access is asked, and e.g., HTTPS please
It asks.Using complete HTTPS access links, it is possible to prevente effectively from access request is held as a hostage in access link, user is caused to visit
Ask failure.
Step S103：Judge whether the load of page rendering service reaches preset load threshold；If so, described in obtaining
The history of user's specified page renders the page, if it is not, then being obtained by user's specified page described in page rendering service real-time rendering
Obtain the real-time rendering page.
The template engine that essentially consists in of the performance consumption of page rendering service renders this part, in the big feelings of concurrent visit capacity
Under condition, frequent template rendering can cause system load drastically to be risen violently, and lead to operating lag.In order to ensure under large concurrent, foot
Enough quickly responses, the first Page Service disaster recovery method that the application provides carry out page rendering service load dynamic and adjust
Section, that is, realize dynamic frequency reducing, and the entire strategy that renders is exactly the timed backup page to local cache and cloud storage service cluster,
It is requested next every time, it can all go to judge whether current system load overloads, the page of Last Backup is directly read if overload
It returns, is rendered without the use of template engine, reaching dynamic reduces system load, the purpose of quick response.
Therefore, the first Page Service disaster recovery method that the application provides, after access request is received, it is necessary first to sentence
Whether the load of disconnected page rendering service reaches preset load threshold, and according to judging result, determines to obtain user's specific page
The history in face renders the page or services user's specified page described in real-time rendering by page rendering, obtains the real-time rendering page.
The preset load threshold can be the maximum load threshold value that page rendering service allows.When page rendering service
Load when reaching the load threshold, then it represents that page rendering service is in full load condition.The preset load threshold can
Rule of thumb set.
It please refers to Fig.2, is the system architecture schematic diagram of the first Page Service disaster recovery method embodiment of the application.
In the present embodiment, Tengine can be used in Web server, and page rendering service can be provided by Wormhole.Wherein, Tengine
It is a Web server project, it, for the demand of big visit capacity website, is added to many advanced work(on the basis of Nginx
Energy and characteristic.Wormhole is a set of node for being absorbed in template rendering (Node.js is a Javascript running environment)
Container, the performance consumption of Wormhole are concentrated mainly on page module and rely on parsing and masterplate engine renders aspect.
In practical applications, for content source server, although there may be the help of preposition CDN, still may be used
It can generate and largely return source request, rendering source station to Wormhole brings higher load, while ensureing to render real-time,
Wormhole loads dynamic usage history rendering cache (local disk, cloud storage service) according to the rendering of current system, comes
The rendering load of page rendering service routine is reduced, ensures the stability of page rendering service.
In the present embodiment, built-in one of Tengine obtains the module that current system renders load, when access request arrives
During up to web application, if the load of current the machine is higher, an overload mark will be increased in normal access request
Wormhole is passed to, Wormhole is identified according to this, is still backed up to judge to carry out to continue real-time rendering from history
Middle reading directly returns.
It should be noted that the server architecture of above-mentioned Tengine+Wormhole is a kind of specific embodiment,
Other frameworks can also be selected in practical applications, for example, Web server, using Nginx servers etc., page rendering service is led to
Node.js offers, above-mentioned various forms of variations, all only change of specific embodiment, without departing from the core of the application are provided
The heart, therefore all within the protection domain of the application.
In the step of whether above-mentioned load for judging page rendering service reaches preset load threshold, if it is decided that page
The load that face renders service is not up to preset load threshold, then can be specified by user described in page rendering service real-time rendering
The page obtains the real-time rendering page of the page.Page rendering service in the case where the page normally renders, can timed backup
For the rendered good page to local disk and long-range cloud storage service, the history as user's specified page renders page
Face occurs overloading or the problems such as system is unavailable when uses in case follow-up.
When it is implemented, to back up the rendered good page, following manner realization can be used：By the real-time rendering page
Face is stored in local memory device, and the page is rendered as the history being locally stored；And the real-time rendering page is stored
Beyond the clouds in storage device, the history as high in the clouds storage renders the page.
By in real-time rendering page storage beyond the clouds storage device, following manner realization can be used：By the reality
When render page storage beyond the clouds in primary storage device；And the real-time rendering page is stored into slack storage beyond the clouds
In equipment.This processing mode sets real-time rendering page timed backup to the primary storage device in high in the clouds and high in the clouds slack storage
It is standby；Therefore, cloud storage service can be effectively prevent to fail because of force majeure.
In the step of whether above-mentioned load for judging page rendering service reaches preset load threshold, if it is decided that page
The load that face renders service reaches preset load threshold, then the history for obtaining user's specified page is needed to render the page.
When it is implemented, the history for obtaining user's specified page renders the page, following manner can be used：First
History is obtained from content source server local cache and renders the page, if should without storage in content source server local cache
The history of user's specified page renders the page, then the history for obtaining user's specified page that long-range cloud storage service provides renders
The page.Using this processing mode, if request page renders serv-fail, local cache can be loaded successively, access cloud storage
Backup page provided etc. is provided.
Cloud storage service may include Page Template, the page and launch data etc..Dependence for cloud storage service, this implementation
The page rendering service of example provides two layers of stability guarantee：1) the active and standby deployment in strange land is carried out to cloud storage service, to avoid list
Point failure causes page rendering service unavailable；2) data (e.g., Page Template and the dispensing data cloud storage service being provided
Deng) Web applications local memory and disk disaster-tolerant backup are carried out, it, can be directly using local when cloud storage service breaks down
Data cached offer page rendering service, ensures that overall page renders the availability of service；The history that cloud storage service is provided
It renders the page and carries out Web application local disk disaster-tolerant backups.
When the history for obtaining high in the clouds storage renders the page, the history stored in the primary storage device in high in the clouds can be obtained first
The page is rendered, if the history not stored in the primary storage device in high in the clouds renders the page, high in the clouds spare storage device can be obtained
The history of middle storage renders the page.
As a preferred solution, whether reach preset load threshold in the load for judging page rendering service
Before, the first method that the application provides, may also include the steps of：Judge whether the page rendering service can be used；If
It is then to enter step S103, if it is not, the history that user's specified page is then obtained by Web server renders the page, goes forward side by side
The step of entering the rendering page that initiator's loopback to the access request obtains.Using this processing mode so that
When page rendering services itself appearance exception, the history that high in the clouds stores can be obtained by Web server and renders the page, this is one
The effective degradation disaster tolerance mode of kind.
Step S105：The rendering page that initiator's loopback to the access request obtains.
In the above-described embodiment, the first Page Service disaster recovery method is provided, corresponding, the application also carries
For the first Page Service disaster tolerance device.The device is corresponding with the embodiment of the above method.
Fig. 3 is please referred to, is the schematic diagram of the first Page Service disaster tolerance device embodiment of the application.Due to device reality
It applies example and is substantially similar to embodiment of the method, so describing fairly simple, referring to the part explanation of embodiment of the method in place of correlation
.Device embodiment described below is only schematical.
The first Page Service disaster tolerance device of the present embodiment, including：
Access request receiving unit 101, for receiving the access request for user's specified page；
Judging unit 103 is overloaded, for judging whether the load of page rendering service reaches preset load threshold；If
It is then to start history to render page acquiring unit 105, if it is not, then starting page rendering unit 107；
The history renders page acquiring unit 105, and the page is rendered for obtaining the history of user's specified page；
The page rendering unit 107 for servicing user's specified page described in real-time rendering by page rendering, obtains
The real-time rendering page；
Page loopback cell 109 is rendered, for the rendering page of initiator's loopback acquisition of the access request.
Optionally, described device further includes：
Page rendering service availability judging unit, for judging whether the page rendering service can be used；If so, it opens
The dynamic overload judging unit 103, if it is not, the history that user's specified page is then obtained by Web server renders the page,
And start the rendering page loopback cell 109.
Optionally, the history renders page acquiring unit 105 and includes：
It is local to obtain subelement, render the page for obtaining the history being locally stored；
High in the clouds obtains subelement, if rendering the page for the history being locally stored to have not been obtained, obtains high in the clouds and deposits
The history of storage renders the page.
Optionally, the high in the clouds obtains subelement and includes：
Primary acquisition subelement renders the page for obtaining the history stored in the primary storage device in high in the clouds；
Spare acquisition subelement, if rendering the page for the history stored in the primary storage device to have not been obtained,
It obtains the history stored in the spare storage device of high in the clouds and renders the page.
Optionally, described device further includes：
Local backup unit, for the real-time rendering page to be stored in local memory device, as being locally stored
History render the page；
High in the clouds backup units, for by real-time rendering page storage beyond the clouds storage device, being stored as high in the clouds
History render the page.
Optionally, the high in the clouds backup units, specifically for the real-time rendering page is stored primary storage beyond the clouds
In equipment；It and will be in real-time rendering page storage beyond the clouds spare storage device.
Optionally, the access request is asked including encrypted access.
It please refers to Fig.4, is the schematic diagram of the electronic equipment embodiment of the application.Since apparatus embodiments are substantially similar to
Embodiment of the method, so describing fairly simple, the relevent part can refer to the partial explaination of embodiments of method.Described below
Apparatus embodiments are only schematical.
The a kind of electronic equipment of the present embodiment, the electronic equipment include：Processor 101；And memory 103, for depositing
The program of Page Service disaster recovery method is realized in storage, which, which is powered and passes through the processor, runs the Page Service disaster recovery method
Program after, perform following step：Receive the access request for user's specified page；Judging the load of page rendering service is
It is no to reach preset load threshold；If so, the history for obtaining user's specified page renders the page, if it is not, then passing through page
Face renders user's specified page described in service real-time rendering, the acquisition real-time rendering page；It is returned to the initiator of the access request
Send the rendering page of acquisition.
Corresponding with above-mentioned method, the application also provides the first Page Service disaster recovery method.Fig. 5 is please referred to, is
The flow chart for second of Page Service disaster recovery method embodiment that the application provides, the present embodiment are identical with first embodiment content
Part repeat no more, refer to the corresponding portion in embodiment one.Second of Page Service disaster recovery method that the application provides
Including：
Step S101：Receive the access request for user's specified page that client is sent.
Second of Page Service disaster recovery method that the application provides, may operate on CDN node server.The access please
CDN node server can be sent to by client by asking.In practical applications, history access can be stored in client browser caching
The page crossed.However, requirement of the large Web application to speed can not be met just with browser rs cache, because of browser
Caching can only promote the speed of secondary access.For the acceleration accessed for the first time, need to optimize from network level.
In the present embodiment, for the acceleration accessed for the first time, accelerated using CDN, by by static resource be cached to from
In the CDN node of the close identical network operator in family, the access speed of user can be not only promoted, moreover it is possible to save the band of server
Width consumption, reduces load.CDN only has static file processing capacity, without the rendering capability of PHP/Node, so treatment effeciency
Height, performance is good, and anti-pressure ability is strong.
Accelerate network access speed using CDN caching technologies.Why the user of different regions accesses same domain name but
The IP address of different CDN nodes can be obtained, this will depend on the intelligent domain name resolution service that CDN service quotient provides, browser hair
When playing inquiry of the domain name, this intelligent DNS service can calculate according to User IP and return to the same network C DN node IP nearest from it,
Guiding browser is established with this node to be connected to obtain resource.
The access request can be the access request of http protocol, also be asked including encrypted access, e.g., HTTPS request.
Using complete HTTPS access links, it is possible to prevente effectively from access request is held as a hostage in access link, user is caused to access event
Barrier.
Step S103：Judge the local history wash with watercolours for whether storing the user's specified page for meeting preset limitation rules
Contaminate the page；If so, obtaining the history renders the page, if it is not, the access request is then sent to content source server, and
Receive the rendering page of user's specified page of the content source server loopback.
The CDN node on the identical network circuit nearest from oneself can be accessed in the user of different regions, when request reaches
After CDN node, node can judge whether the content caching of oneself is effective, if it is valid, the cache contents that make an immediate response are to user,
So as to accelerate response speed.
It should be noted that only meet preset limitation rules (i.e. effectively) when the history being locally stored renders the page
When, which could be rendered the page and be passed back to requesting party, for example, similar page tools such as activity are issued, price appears, the second kills
There is certain timeliness, only when its is effective, which could be rendered the page and be passed back to requesting party.In order to ensure user's energy
Enough that the newest page is accessed in time, caching and the user terminal caching of CDN requires instant actual effect, needs to return source acquisition again most
The page of new version.
If the cache invalidation of CDN node, it can go the relevant content source server of access request to obtain according to service configuration
Newest resource response is taken to user, and content caching is got off to respond to the user of subsequent access.Therefore, an area
As long as interior first load resource there are one user, caching is established in CDN, other subsequent users of this area can be utilized directly
Resource in CDN cachings.
Fig. 6 is please referred to, the system architecture of second of the Page Service disaster recovery method embodiment signal provided for the application
Figure.The big visit capacity of user of the web application of the present embodiment is very big, in order to cope with the situation of big visit capacity, high concurrent, this reality
It applies example and provides page access service by content source server cluster.In this case, the access request is sent described
To before content source server, it is necessary first to determine to want the content source server of Hui Yuan.
When it is implemented, wanting the content source server for determining to want Hui Yuan, following manner realization can be used：According at least
The distance between equipment (CDN node) of second method that one content source server provides respectively with operation the application, really
Surely the content source server of Hui Yuan is wanted.It is of course also possible to random determines a content source server, as the content for wanting Hui Yuan
Source server.If it is determined that content source server break down unavailable, then need to redefine the content source for wanting Hui Yuan and take
Business device, and the access request is sent to the content source server redefined.
When it is implemented, second of Page Service disaster recovery method that the application provides, is returned receiving content source server
After the rendering page of user's specified page sent, it may also include the steps of：The rendering page received is stored, in case
It is follow-up to use.
In extreme circumstances, in fact it could happen that all not available situation of entire content source server cluster, in this case, this
Second of the disaster recovery method provided is provided, designs and is revealed all the details by CDN to ensure Page Service, once content source server is all delayed
Machine, the then mode that will switch CDN go back tos sources, by CDN entirety Hui Yuan to calamity for cloud storage service.
In practical applications, ensure that the page may have access to by cloud storage service device cluster.Therefore, it is necessary first to determine to want Hui Yuan
Cloud storage service device, after the cloud storage service device of Hui Yuan is determined, the access request is sent to determining cloud storage
Server, and the history for receiving user's specified page of the determining cloud storage service device loopback renders the page.If
Determining cloud storage service device is unavailable, then redefines the cloud storage service device for wanting Hui Yuan, and the access request is sent
To the cloud storage service device redefined.
Step S105：The rendering page that initiator's loopback to the access request obtains.
In the above-described embodiment, second of Page Service disaster recovery method is provided, corresponding, the application also carries
For second of Page Service disaster tolerance device.The device is corresponding with the embodiment of the above method.
Fig. 7 is please referred to, is the schematic diagram of second of Page Service disaster tolerance device embodiment of the application.Due to device reality
It applies example and is substantially similar to embodiment of the method, so describing fairly simple, referring to the part explanation of embodiment of the method in place of correlation
.Device embodiment described below is only schematical.
Second of Page Service disaster tolerance device of the present embodiment, including：
Access request receiving unit 101, for receiving the access request for user's specified page of client transmission；
Judge acquiring unit 103, specified for judging locally whether to store the user for meeting preset limitation rules
The history of the page renders the page；If so, start page acquiring unit 105, if it is not, then starting back source unit 107；
The page acquiring unit 105 renders the page for obtaining the history；
Described time source unit 107 for the access request to be sent to content source server, and receives the content source
The rendering page of user's specified page of server loopback；
Page loopback cell 109, for the rendering page obtained to initiator's loopback of the access request.
Optionally, described time source unit 107 includes：
Content source server determination subelement, for determining to want the content source server of Hui Yuan.
Optionally, the content source server determination subelement, specifically for according at least one content source server point
The distance between equipment not with running the method determines to want the content source server of Hui Yuan.
Optionally, if the content source server is unavailable, the content source server for wanting Hui Yuan is redefined, and by institute
It states access request and is sent to the content source server redefined.
Optionally, if content source server cluster is unavailable, it is determined that the cloud storage service device of Hui Yuan, and by the visit
Ask that request is sent to determining cloud storage service device, and the user for receiving the determining cloud storage service device loopback specifies
The history of the page renders the page.
Optionally, if the determining cloud storage service device is unavailable, the cloud storage service device for wanting Hui Yuan is redefined,
And the access request is sent to the cloud storage service device redefined.
Optionally, described device further includes：
Backup units, for storing the rendering page received.
Optionally, the access request is asked including encrypted access.
Fig. 8 is please referred to, is the schematic diagram of the electronic equipment embodiment of the application.Since apparatus embodiments are substantially similar to
Embodiment of the method, so describing fairly simple, the relevent part can refer to the partial explaination of embodiments of method.Described below
Apparatus embodiments are only schematical.
The a kind of electronic equipment of the present embodiment, the electronic equipment include：Processor 101；And memory 103, for depositing
The program of Page Service disaster recovery method is realized in storage, which, which is powered and passes through the processor, runs the Page Service disaster recovery method
Program after, perform following step：Receive the access request for user's specified page that client is sent；Whether judge local
The history that storage meets user's specified page of preset limitation rules renders the page；If so, obtain the history wash with watercolours
The page is contaminated, if it is not, the access request then is sent to content source server, and receives the institute of the content source server loopback
State the rendering page of user's specified page；The rendering page that initiator's loopback to the access request obtains.
Corresponding with above-mentioned method, the application also provides the first Page Service disaster recovery method.Fig. 9 is please referred to, is
The flow chart for the third Page Service disaster recovery method embodiment that the application provides, the present embodiment are identical with first embodiment content
Part repeat no more, refer to the corresponding portion in embodiment one.The third Page Service disaster recovery method that the application provides
Including：
Step S101：Receive the access request for user's specified page.
The access request, can be the access request of http protocol or encrypted access is asked, and e.g., HTTPS please
It asks.In the present embodiment, using complete HTTPS access links；This processing mode, it is possible to prevente effectively from access request is being visited
It asks in link and is held as a hostage, cause user's access fault.
Step S103：The history for obtaining user's specified page renders the page.
The history for obtaining user's specified page renders the page, and following manner realization can be used：Master is obtained first
The page is rendered with the history stored in storage device, if the history stored in primary storage device, which has not been obtained, renders the page,
It then obtains the history stored in spare storage device and renders the page.Using this processing mode so that when host apparatus fails,
It can also degrade and provide service using stand-by equipment.
Step S105：The history that initiator's loopback to the access request obtains renders the page.
In the above-described embodiment, the third Page Service disaster recovery method is provided, corresponding, the application also carries
For the third Page Service disaster tolerance device.The device is corresponding with the embodiment of the above method.
Figure 10 is please referred to, is the schematic diagram of the third Page Service disaster tolerance device embodiment of the application.Due to device
Embodiment is substantially similar to embodiment of the method, so describing fairly simple, related part is said referring to the part of embodiment of the method
It is bright.Device embodiment described below is only schematical.
The third Page Service disaster tolerance device of the present embodiment, including：
Access request receiving unit 101, for receiving the access request for user's specified page；
Page acquiring unit 103 renders the page for obtaining the history of user's specified page；
Page loopback cell 105, the history for being obtained to initiator's loopback of the access request render the page.
Optionally, the page acquiring unit 103 includes：
Primary acquisition subelement renders the page for obtaining the history stored in primary storage device；
Spare acquisition subelement, if rendering the page for the history stored in the primary storage device to have not been obtained,
It obtains the history stored in spare storage device and renders the page.
Optionally, the access request is asked including encrypted access.
1 is please referred to Fig.1, is the schematic diagram of the electronic equipment embodiment of the application.Since apparatus embodiments are substantially similar
In embodiment of the method, so describing fairly simple, the relevent part can refer to the partial explaination of embodiments of method.It is described below
Apparatus embodiments it is only schematical.
The a kind of electronic equipment of the present embodiment, the electronic equipment include：Processor 101；And memory 103, receive needle
To the access request of user's specified page；The history for obtaining user's specified page renders the page；To the access request
The history that initiator's loopback obtains renders the page.
The embodiment of the present application additionally provides a kind of Page Service disaster tolerance system, and as shown in figure 12, which includes：It is interior
Hold source server cluster, content delivery network node cluster and cloud storage service device cluster, in the content source server deployment
The first Page Service disaster tolerance device described in embodiment is stated, the content delivery network node is disposed described in above-described embodiment
Second of Page Service disaster tolerance device, the cloud storage service device dispose the third Page Service disaster tolerance described in above-described embodiment
Device.
The first described Page Service disaster tolerance device is deployed on Web server, can be received for user's specified page
Access request, and judge whether the load of page rendering service reaches preset load threshold；If so, obtain the user
The history of specified page renders the page, if it is not, then servicing user's specified page described in real-time rendering by page rendering, obtains real
When render the page, get render the page after, to the access request initiator's loopback obtain the rendering page；Described
Two kinds of Page Service disaster tolerance devices are deployed in CDN node, in the visit for user's specified page for receiving client transmission
It asks request, first determines whether that the local history for whether storing the user's specified page for meeting preset limitation rules renders page
Face；If so, obtaining the history renders the page, if it is not, the access request then is sent to content source server, and receive
The rendering page of user's specified page of the content source server loopback, after the rendering page is got, to the visit
Ask the rendering page that initiator's loopback of request obtains；The third described Page Service disaster tolerance device is deployed on Cloud Server,
After the access request for user's specified page is received, the history for obtaining user's specified page renders the page, and to
The history that initiator's loopback of the access request obtains renders the page.
3 are please referred to Fig.1, is the access link schematic diagram of the Page Service disaster tolerance system embodiment of the application.In this reality
It applies in example, in order to avoid user's access link is held as a hostage, page rendering service (Wormhole) completes the transformation of full HTTPS,
Including going back to source to the link for rendering source station from CDN to user terminal and from CDN, complete HTTPS access links are realized, in avoiding
Between be held as a hostage, cause user's access fault.Wherein, the HTTPS services of user terminal are provided by CDN is unified, are completely supported
Including the various protocols from HTTPS, SPDY to HTTP2；From CDN to the rendering source station of page rendering service, then by uniformly connecing
Enter layer service to handle, SSL certificate and forwarding work are managed collectively by being uniformly accessed into layer.
In the present embodiment, Wormhole is that the preposition stateless static pages of a CDN render service, from framework complexity
Degree and maintenance cost angle are set out, the pattern disposed using strange land multimachine room, are returned source policy by CDN and are realized that strange land is mostly living.With
For the business of 2016 double 11, in order to support the business of 2016 double 11, Wormhole deploys two places (Shanghai+Shenzhen) three
The strategy of computer room, wherein Shanghai based on same city disaster tolerance, deploys two computer rooms.The Wormhole clusters pair of these three computer rooms deployment
Deng service, after CDN returns the serv-fail of one computer room of source request, can be automatically switched to separately by the Failback mechanism of CDN
An outer computer room retries request, as long as ensureing to be capable of providing service there are one computer room, whole page rendering service would not
It interrupts, and by the availability verification of the rehearsal of suspension several times.
It is available to there is service in other services that page rendering service relies on for the Page Service disaster tolerance system that the application provides
During sex chromosome mosaicism, the local disk caching of the page, high in the clouds backup offer degradation disaster tolerance service can be rendered by being stored with history；
When page rendering services itself appearance exception, the history that high in the clouds stores can be obtained by Web server and renders the page, with offer
Degradation disaster tolerance service；When availability failure occurs in full page rendering service cluster, high in the clouds can be passed through and backed up and content point
Hair network server provides disaster tolerance of revealing all the details, and therefore, can be may have access to effective guarantee page quick response.
Although the application is disclosed as above with preferred embodiment, it is not for limiting the application, any this field skill
Art personnel are not being departed from spirit and scope, can make possible variation and modification, therefore the guarantor of the application
Shield range should be subject to the range that the application claim is defined.
In a typical configuration, computing device includes one or more processors (CPU), input/output interface, net
Network interface and memory.
Memory may include computer-readable medium in volatile memory, random access memory (RAM) and/or
The forms such as Nonvolatile memory, such as read-only memory (ROM) or flash memory (flash RAM).Memory is computer-readable medium
Example.
1st, computer-readable medium can be by any side including permanent and non-permanent, removable and non-removable media
Method or technology realize that information stores.Information can be computer-readable instruction, data structure, the module of program or other numbers
According to.The example of the storage medium of computer includes, but are not limited to phase transition internal memory (PRAM), static RAM
(SRAM), dynamic random access memory (DRAM), other kinds of random access memory (RAM), read-only memory
(ROM), electrically erasable programmable read-only memory (EEPROM), fast flash memory bank or other memory techniques, CD-ROM are read-only
Memory (CD-ROM), digital versatile disc (DVD) or other optical storages, magnetic tape cassette, tape magnetic rigid disk storage or
Other magnetic storage apparatus or any other non-transmission medium, available for storing the information that can be accessed by a computing device.According to
Herein defines, and computer-readable medium does not include non-temporary computer readable media (transitory media), such as modulates
Data-signal and carrier wave.
2nd, it will be understood by those skilled in the art that embodiments herein can be provided as method, system or computer program production
Product.Therefore, the embodiment in terms of complete hardware embodiment, complete software embodiment or combination software and hardware can be used in the application
Form.It can be used moreover, the application can be used in one or more computers for wherein including computer usable program code
The computer program product that storage medium is implemented on (including but not limited to magnetic disk storage, CD-ROM, optical memory etc.)
Form.
Claims (25)
1. a kind of Page Service disaster recovery method, which is characterized in that including：
Receive the access request for user's specified page；
Judge whether the load of page rendering service reaches preset load threshold；If so, obtain user's specified page
History render the page, if it is not, then pass through page rendering service real-time rendering described in user's specified page, obtain real-time rendering page
Face；
The rendering page that initiator's loopback to the access request obtains.
2. Page Service disaster recovery method according to claim 1, which is characterized in that in the judgement page rendering service
Before whether load reaches preset load threshold, further include：
Judge whether the page rendering service can be used；If so, enter in next step, if it is not, then obtaining institute by Web server
The history for stating user's specified page renders the page, and enters the rendering page that initiator's loopback to the access request obtains
The step of face.
3. Page Service disaster recovery method according to claim 1 or 2, which is characterized in that the acquisition user specifies
The history of the page renders the page, including：
It obtains the history being locally stored and renders the page；
If the history being locally stored, which has not been obtained, renders the page, the history for obtaining high in the clouds storage renders the page.
4. Page Service disaster recovery method according to claim 3, which is characterized in that the history wash with watercolours for obtaining high in the clouds storage
The page is contaminated, including：
It obtains the history stored in the primary storage device in high in the clouds and renders the page；
If the history stored in the primary storage device, which has not been obtained, renders the page, obtain and deposited in the spare storage device of high in the clouds
The history of storage renders the page.
5. Page Service disaster recovery method according to claim 1, which is characterized in that refer in user described in the real-time rendering
After determining the page, further include：
The real-time rendering page is stored in local memory device, the page is rendered as the history being locally stored；It and will
Beyond the clouds in storage device, the history as high in the clouds storage renders the page for the real-time rendering page storage.
6. Page Service disaster recovery method according to claim 5, which is characterized in that described to deposit the real-time rendering page
It stores up in storage device beyond the clouds, in the following way：
It will be in real-time rendering page storage beyond the clouds primary storage device；And the real-time rendering page is stored in
In the spare storage device of high in the clouds.
7. Page Service disaster recovery method according to claim 1, which is characterized in that the access request includes encrypted access
Request.
8. a kind of Page Service disaster tolerance device, which is characterized in that including：
Access request receiving unit, for receiving the access request for user's specified page；
Judging unit is overloaded, for judging whether the load of page rendering service reaches preset load threshold；If so, start
History renders page acquiring unit, if it is not, then starting page rendering unit；
History renders page acquiring unit, and the page is rendered for obtaining the history of user's specified page；
Page rendering unit for servicing user's specified page described in real-time rendering by page rendering, obtains real-time rendering page
Face；
Page loopback cell is rendered, for the rendering page of initiator's loopback acquisition of the access request.
9. a kind of electronic equipment, which is characterized in that including：
Processor；And
Memory, for storing the program for realizing Page Service disaster recovery method, which is powered and passes through the processor and run
After the program of the Page Service disaster recovery method, following step is performed：Receive the access request for user's specified page；Judge page
Whether the load that face renders service reaches preset load threshold；If so, the history for obtaining user's specified page renders
The page if it is not, then servicing user's specified page described in real-time rendering by page rendering, obtains the real-time rendering page；To described
The rendering page that initiator's loopback of access request obtains.
10. a kind of Page Service disaster recovery method, which is characterized in that including：
Receive the access request for user's specified page that client is sent；
Judge that the local history for whether storing the user's specified page for meeting preset limitation rules renders the page；If so,
It then obtains the history and renders the page, if it is not, the access request then is sent to content source server, and receive the content
The rendering page of user's specified page of source server loopback；
The rendering page that initiator's loopback to the access request obtains.
11. Page Service disaster recovery method according to claim 10, which is characterized in that send out the access request described
It send to before content source server, further includes：
The determining content source server for wanting Hui Yuan.
12. Page Service disaster recovery method according to claim 11, which is characterized in that the content source for determining to want Hui Yuan
Server, in the following way：
According at least one content source server respectively with running the distance between equipment of the method, determine to want that Hui Yuan's is interior
Hold source server.
13. Page Service disaster recovery method according to claim 10, which is characterized in that if the content source server can not
With then redefining the content source server for wanting Hui Yuan, and the access request is sent to the content source service redefined
Device.
14. Page Service disaster recovery method according to claim 10, which is characterized in that if content source server cluster can not
With, it is determined that the cloud storage service device of Hui Yuan, and the access request is sent to determining cloud storage service device, and receive
The history of user's specified page of the determining cloud storage service device loopback renders the page.
15. Page Service disaster recovery method according to claim 14, which is characterized in that if the determining cloud storage service
Device is unavailable, then redefines the cloud storage service device for wanting Hui Yuan, and the access request is sent to the cloud redefined and is deposited
Store up server.
16. Page Service disaster recovery method according to claim 10, which is characterized in that receive the content source clothes described
After the rendering page of user's specified page of business device loopback, further include：
Store the rendering page received.
17. Page Service disaster recovery method according to claim 10, which is characterized in that the access request includes encryption and visits
Ask request.
18. a kind of Page Service disaster tolerance device, which is characterized in that including：
Access request receiving unit, for receiving the access request for user's specified page of client transmission；
Acquiring unit is judged, for judging locally whether store going through for the user's specified page for meeting preset limitation rules
History renders the page；If so, start page acquiring unit, if it is not, then starting back source unit；
The page acquiring unit renders the page for obtaining the history；
Described time source unit for the access request to be sent to content source server, and receives the content source server
The rendering page of user's specified page of loopback；
Page loopback cell, for the rendering page obtained to initiator's loopback of the access request.
19. a kind of electronic equipment, which is characterized in that including：
Processor；And
Memory, for storing the program for realizing Page Service disaster recovery method, which is powered and passes through the processor and run
After the program of the Page Service disaster recovery method, following step is performed：Receive the visit for user's specified page that client is sent
Ask request；Judge that the local history for whether storing the user's specified page for meeting preset limitation rules renders the page；If
It is then to obtain the history to render the page, if it is not, the access request then is sent to content source server, and described in reception
The rendering page of user's specified page of content source server loopback；What initiator's loopback to the access request obtained
Render the page.
20. a kind of Page Service disaster recovery method, which is characterized in that including：
Receive the access request for user's specified page；
The history for obtaining user's specified page renders the page；
The history that initiator's loopback to the access request obtains renders the page.
21. Page Service disaster recovery method according to claim 20, which is characterized in that described to obtain user's specific page
The history in face renders the page, including：
It obtains the history stored in primary storage device and renders the page；
If the history stored in the primary storage device, which has not been obtained, renders the page, obtain what is stored in spare storage device
History renders the page.
22. Page Service disaster recovery method according to claim 20, which is characterized in that the access request includes encryption and visits
Ask request.
23. a kind of Page Service disaster tolerance device, which is characterized in that including：
Access request receiving unit, for receiving the access request for user's specified page；
Page acquiring unit renders the page for obtaining the history of user's specified page；
Page loopback cell, the history for being obtained to initiator's loopback of the access request render the page.
24. a kind of electronic equipment, which is characterized in that including：
Processor；And
Memory, for storing the program for realizing Page Service disaster recovery method, which is powered and passes through the processor and run
After the program of the Page Service disaster recovery method, following step is performed：Receive the access request for user's specified page；Obtain institute
The history for stating user's specified page renders the page；The history that initiator's loopback to the access request obtains renders the page.
25. a kind of Page Service disaster tolerance system, which is characterized in that including：Content source server cluster, content delivery network node
Cluster and cloud storage service device cluster, the content source server dispose Page Service disaster tolerance dress according to claim 8
It puts, the content delivery network node disposes Page Service disaster tolerance device according to claim 18, the cloud storage clothes
Business device disposes Page Service disaster tolerance device according to claim 23.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611110778.3A CN108156013B (en) | 2016-12-02 | 2016-12-02 | Page service disaster tolerance method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611110778.3A CN108156013B (en) | 2016-12-02 | 2016-12-02 | Page service disaster tolerance method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108156013A true CN108156013A (en) | 2018-06-12 |
| CN108156013B CN108156013B (en) | 2021-08-10 |
Family
ID=62468250
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611110778.3A Active CN108156013B (en) | 2016-12-02 | 2016-12-02 | Page service disaster tolerance method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108156013B (en) |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109474668A (en) * | 2018-10-16 | 2019-03-15 | 平安科技（深圳）有限公司 | CDN service switching method, device, computer equipment and storage medium |
| CN110045928A (en) * | 2019-04-09 | 2019-07-23 | 烟台大学 | A kind of electronic information mobile terminal |
| CN110096659A (en) * | 2019-03-27 | 2019-08-06 | 北京三快在线科技有限公司 | A kind of page display method, device, equipment and readable storage medium storing program for executing |
| CN110851192A (en) * | 2018-07-27 | 2020-02-28 | 北京京东尚科信息技术有限公司 | Method and device for responding to configuration of degraded switch |
| WO2020078450A1 (en) * | 2018-10-19 | 2020-04-23 | 北京微播视界科技有限公司 | Video content push method and apparatus |
| CN111245873A (en) * | 2018-11-28 | 2020-06-05 | 北京京东尚科信息技术有限公司 | Service degradation method, device, equipment and storage medium |
| CN111404754A (en) * | 2020-03-23 | 2020-07-10 | 北京九州云动科技有限公司 | Disaster recovery method, device and equipment for interface |
| CN111767486A (en) * | 2019-09-24 | 2020-10-13 | 北京京东尚科信息技术有限公司 | Method, device, electronic equipment and computer readable medium for displaying page |
| CN112436953A (en) * | 2020-08-14 | 2021-03-02 | 上海幻电信息科技有限公司 | Page data backup and disaster tolerance page display method and device |
| WO2021051492A1 (en) * | 2019-09-18 | 2021-03-25 | 招商银行股份有限公司 | Database service node switching method, apparatus and device, and computer storage medium |
| CN112565472A (en) * | 2019-09-10 | 2021-03-26 | 北京京东尚科信息技术有限公司 | Static resource processing method and device |
| CN112596955A (en) * | 2020-12-28 | 2021-04-02 | 山西云时代研发创新中心有限公司 | Emergency processing system and method for processing large-scale system emergency in cloud computing |
| CN113486272A (en) * | 2021-07-07 | 2021-10-08 | 上海中通吉网络技术有限公司 | Method for refreshing page in application |
| CN113645062A (en) * | 2021-07-13 | 2021-11-12 | 阿里巴巴新加坡控股有限公司 | Page data processing method and device and electronic equipment |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101465768A (en) * | 2009-01-12 | 2009-06-24 | 上海及第熊软件科技有限公司 | Method and system for implementing website disaster-tolerating and error-tolerating operation |
| CN102487402A (en) * | 2010-12-03 | 2012-06-06 | 腾讯科技（深圳）有限公司 | Method, device and system for realizing webpage rendering by server side |
| CN102902805A (en) * | 2012-10-15 | 2013-01-30 | 东软集团股份有限公司 | Page access method and device |
| CN103778236A (en) * | 2014-01-26 | 2014-05-07 | 网宿科技股份有限公司 | Webpage data distribution processing method and device as well as webpage generation processing method and device |
| CN104519081A (en) * | 2013-09-27 | 2015-04-15 | 阿里巴巴集团控股有限公司 | Page access method and device |
| CN104573025A (en) * | 2015-01-12 | 2015-04-29 | 北京京东尚科信息技术有限公司 | Method and system for increasing page loading rate |
| CN104579765A (en) * | 2014-12-27 | 2015-04-29 | 北京奇虎科技有限公司 | Disaster tolerance method and device for cluster system |
| CN106156231A (en) * | 2015-04-24 | 2016-11-23 | 阿里巴巴集团控股有限公司 | A kind of website disaster recovery method, Apparatus and system |
-
2016
- 2016-12-02 CN CN201611110778.3A patent/CN108156013B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101465768A (en) * | 2009-01-12 | 2009-06-24 | 上海及第熊软件科技有限公司 | Method and system for implementing website disaster-tolerating and error-tolerating operation |
| CN102487402A (en) * | 2010-12-03 | 2012-06-06 | 腾讯科技（深圳）有限公司 | Method, device and system for realizing webpage rendering by server side |
| CN102902805A (en) * | 2012-10-15 | 2013-01-30 | 东软集团股份有限公司 | Page access method and device |
| CN104519081A (en) * | 2013-09-27 | 2015-04-15 | 阿里巴巴集团控股有限公司 | Page access method and device |
| CN103778236A (en) * | 2014-01-26 | 2014-05-07 | 网宿科技股份有限公司 | Webpage data distribution processing method and device as well as webpage generation processing method and device |
| CN104579765A (en) * | 2014-12-27 | 2015-04-29 | 北京奇虎科技有限公司 | Disaster tolerance method and device for cluster system |
| CN104573025A (en) * | 2015-01-12 | 2015-04-29 | 北京京东尚科信息技术有限公司 | Method and system for increasing page loading rate |
| CN106156231A (en) * | 2015-04-24 | 2016-11-23 | 阿里巴巴集团控股有限公司 | A kind of website disaster recovery method, Apparatus and system |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110851192A (en) * | 2018-07-27 | 2020-02-28 | 北京京东尚科信息技术有限公司 | Method and device for responding to configuration of degraded switch |
| CN109474668A (en) * | 2018-10-16 | 2019-03-15 | 平安科技（深圳）有限公司 | CDN service switching method, device, computer equipment and storage medium |
| CN109474668B (en) * | 2018-10-16 | 2022-03-04 | 平安科技（深圳）有限公司 | CDN service switching method and device, computer equipment and storage medium |
| WO2020078450A1 (en) * | 2018-10-19 | 2020-04-23 | 北京微播视界科技有限公司 | Video content push method and apparatus |
| US11146858B2 (en) | 2018-10-19 | 2021-10-12 | Beijing Microlive Vision Technology Co., Ltd | Method and apparatus for pushing video content |
| CN111245873B (en) * | 2018-11-28 | 2023-09-05 | 北京京东尚科信息技术有限公司 | Service degradation method, device, equipment and storage medium |
| CN111245873A (en) * | 2018-11-28 | 2020-06-05 | 北京京东尚科信息技术有限公司 | Service degradation method, device, equipment and storage medium |
| CN110096659B (en) * | 2019-03-27 | 2021-08-20 | 北京三快在线科技有限公司 | Page display method, device and equipment and readable storage medium |
| CN110096659A (en) * | 2019-03-27 | 2019-08-06 | 北京三快在线科技有限公司 | A kind of page display method, device, equipment and readable storage medium storing program for executing |
| CN110045928A (en) * | 2019-04-09 | 2019-07-23 | 烟台大学 | A kind of electronic information mobile terminal |
| CN112565472A (en) * | 2019-09-10 | 2021-03-26 | 北京京东尚科信息技术有限公司 | Static resource processing method and device |
| CN112565472B (en) * | 2019-09-10 | 2024-05-17 | 北京京东尚科信息技术有限公司 | Static resource processing method and device |
| WO2021051492A1 (en) * | 2019-09-18 | 2021-03-25 | 招商银行股份有限公司 | Database service node switching method, apparatus and device, and computer storage medium |
| CN111767486A (en) * | 2019-09-24 | 2020-10-13 | 北京京东尚科信息技术有限公司 | Method, device, electronic equipment and computer readable medium for displaying page |
| CN111404754A (en) * | 2020-03-23 | 2020-07-10 | 北京九州云动科技有限公司 | Disaster recovery method, device and equipment for interface |
| CN112436953A (en) * | 2020-08-14 | 2021-03-02 | 上海幻电信息科技有限公司 | Page data backup and disaster tolerance page display method and device |
| CN112596955A (en) * | 2020-12-28 | 2021-04-02 | 山西云时代研发创新中心有限公司 | Emergency processing system and method for processing large-scale system emergency in cloud computing |
| CN113486272A (en) * | 2021-07-07 | 2021-10-08 | 上海中通吉网络技术有限公司 | Method for refreshing page in application |
| CN113645062A (en) * | 2021-07-13 | 2021-11-12 | 阿里巴巴新加坡控股有限公司 | Page data processing method and device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108156013B (en) | 2021-08-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108156013A (en) | A kind of Page Service disaster recovery method, device and electronic equipment | |
| US10104037B2 (en) | Method and system for network access request control | |
| CN108027805B (en) | Load distribution in a data network | |
| CN111885123B (en) | Construction method and device of cross-K8 s target service access channel | |
| US9582377B1 (en) | Dynamic sizing of storage capacity for a remirror buffer | |
| US20160197835A1 (en) | Architecture and method for virtualization of cloud networking components | |
| US20160198003A1 (en) | Architecture and method for sharing dedicated public cloud connectivity | |
| US20160197834A1 (en) | Architecture and method for traffic engineering between diverse cloud providers | |
| US20150195347A1 (en) | Architecture and method for cloud provider selection and projection | |
| US20150193466A1 (en) | Architecture and method for cloud provider selection and projection | |
| WO2018121334A1 (en) | Web application service providing method, apparatus, electronic device and system | |
| CN102843426B (en) | Based on Web cache resources shared system and the method for intelligent father node | |
| CN108737532A (en) | A kind of resource acquiring method, client, computer equipment and readable medium | |
| CN103607424B (en) | Server connection method and server system | |
| US20150193246A1 (en) | Apparatus and method for data center virtualization | |
| CN113010818A (en) | Access current limiting method and device, electronic equipment and storage medium | |
| CN106302595A (en) | A kind of method and apparatus that server is carried out physical examination | |
| US20170153909A1 (en) | Methods and Devices for Acquiring Data Using Virtual Machine and Host Machine | |
| CN107135242B (en) | Mongodb cluster access method, device and system | |
| CN109039794A (en) | One kind returning source path and determines method and device | |
| CN113301079B (en) | Data acquisition method, system, computing device and storage medium | |
| CN109561054A (en) | A kind of data transmission method, controller and access device | |
| CN113067875A (en) | Access method, device and equipment based on dynamic flow control of micro-service gateway | |
| WO2016109845A1 (en) | Architecture and method for traffic engineering between diverse cloud providers | |
| CN111694639A (en) | Method and device for updating address of process container and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20211105 Address after: Room 507, floor 5, building 3, No. 969, Wenyi West Road, Wuchang Street, Yuhang District, Hangzhou City, Zhejiang Province Patentee after: ZHEJIANG TMALL TECHNOLOGY Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: ALIBABA GROUP HOLDING Ltd. |