CN112954087A - Domain name connection method and device for SaaS (software as a service), computer equipment and storage medium - Google Patents
Domain name connection method and device for SaaS (software as a service), computer equipment and storage medium Download PDFInfo
- Publication number
- CN112954087A CN112954087A CN202110193920.XA CN202110193920A CN112954087A CN 112954087 A CN112954087 A CN 112954087A CN 202110193920 A CN202110193920 A CN 202110193920A CN 112954087 A CN112954087 A CN 112954087A
- Authority
- CN
- China
- Prior art keywords
- domain name
- saas service
- domain
- saas
- standby
- 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
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000004590 computer program Methods 0.000 claims description 14
- 238000001514 detection method Methods 0.000 claims description 13
- 230000006870 function Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 3
- 238000004422 calculation algorithm Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 102220470087 Ribonucleoside-diphosphate reductase subunit M2_S20A_mutation Human genes 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000012163 sequencing technique Methods 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
- H04L61/301—Name conversion
-
- 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application provides a domain name connection method, a domain name connection device, computer equipment and a storage medium of a software as a service (SaaS), which are used for automatically realizing domain name switching so as to ensure high availability of the service. The method mainly comprises the following steps: when a SaaS service request sent by a user is received, acquiring a domain name priority sequence list and determining whether a client is in a fusing state, wherein the domain name with the highest priority in the domain name priority sequence list is a main domain name, and the other domain names are standby domain names; if the client is not in a fusing state, using the main domain name to access the SaaS service; if the client is in a fusing state, determining whether the standby domain names in the domain name priority sequence list are unavailable; if the standby domain name in the domain name priority sequence list is available, the available standby domain name is used for accessing the SaaS service; and if the standby domain names in the domain name priority sequence list are unavailable, accessing the SaaS service by using the domain name set by the user or the default domain name.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a domain name connection method and apparatus for SaaS service, a computer device, and a storage medium.
Background
The DNS (Domain Name System), which is a distributed database that maps Domain names and IP addresses to each other. It is not enough to know the domain name of a certain machine on the Internet, and there is a way to find that machine. The task of finding the machine is performed by a device called a domain name server on the network, and the process of completing the task is called domain name resolution
In the prior art, when a domain name used by a client cannot be accessed, the client needs to manually modify the domain name, and the SaaS service cannot be used in the process, that is, the domain name of the client cannot be configured on a SaaS service platform.
Disclosure of Invention
The embodiment of the application provides a domain name connection method and device of a SaaS service, computer equipment and a storage medium, which are used for automatically realizing domain name switching so as to ensure high availability of the service.
The embodiment of the invention provides a domain name connection method of SaaS service, which comprises the following steps:
when a SaaS service request sent by a user is received, acquiring a domain name priority sequence list and determining whether a client is in a fusing state, wherein the domain name with the highest priority in the domain name priority sequence list is a main domain name, and the other domain names are standby domain names;
if the client is not in a fusing state, using the main domain name to access the SaaS service;
if the client is in a fusing state, determining whether the standby domain names in the domain name priority sequence list are unavailable;
if the standby domain name in the domain name priority sequence list is available, the available standby domain name is used for accessing the SaaS service;
and if the standby domain names in the domain name priority sequence list are unavailable, accessing the SaaS service by using the domain name set by the user or the default domain name.
The embodiment of the invention provides a domain name connecting device of SaaS service, which comprises:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring a domain name priority sequence list and determining whether a client is in a fusing state or not when receiving a SaaS service request sent by a user, the domain name with the highest priority in the domain name priority sequence list is a main domain name, and the other domain names are standby domain names;
the access module is used for accessing the SaaS service by using the main domain name if the client is not in a fusing state;
a determining module, configured to determine whether none of the standby domain names in the domain name priority order list is available if the client is in a blown state;
the access module is further configured to access the SaaS service by using the available standby domain name if the standby domain name in the domain name priority order list is available;
the access module is further configured to access the SaaS service using the domain name set by the user or a default domain name if none of the standby domain names in the domain name priority order list is available.
A computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the domain name connection method of the SaaS service when executing the computer program.
A computer-readable storage medium storing a computer program which, when executed by a processor, implements the above-described domain name connection method for SaaS service.
The invention provides a domain name connection method, a device, computer equipment and a storage medium of a SaaS service, when a SaaS service request sent by a user is received, a domain name priority sequence list is obtained and whether a client side is in a fusing state is determined, the domain name with the highest priority in the domain name priority sequence list is a main domain name, and the other domain names are standby domain names; if the client is not in a fusing state, using the main domain name to access the SaaS service; if the client is in a fusing state, determining whether the standby domain names in the domain name priority sequence list are unavailable; if the standby domain name in the domain name priority sequence list is available, the available standby domain name is used for accessing the SaaS service; and if the standby domain names in the domain name priority sequence list are unavailable, accessing the SaaS service by using the domain name set by the user or the default domain name. Therefore, when the SaaS service is requested, if some domain names cannot be used due to special reasons, the most appropriate available domain name can be calculated according to an algorithm, and domain name switching is automatically realized, so that the high availability of the service is ensured.
Drawings
Fig. 1 is a flowchart of a domain name connection method for SaaS service according to a first embodiment of the present application;
fig. 2 is a flowchart of a domain name connection method for SaaS service according to a second embodiment of the present application;
fig. 3 is a flowchart of acquiring a domain name priority order list according to a third embodiment of the present application;
fig. 4 is a flowchart of a domain name connection method for SaaS service according to a fourth embodiment of the present disclosure;
fig. 5 is a block diagram illustrating a domain name connection apparatus of a SaaS service according to an embodiment of the present disclosure;
fig. 6 is a schematic diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order to better understand the technical solutions described above, the technical solutions of the embodiments of the present application are described in detail below with reference to the drawings and the specific embodiments, and it should be understood that the specific features of the embodiments and the embodiments of the present application are detailed descriptions of the technical solutions of the embodiments of the present application, and are not limitations of the technical solutions of the present application, and the technical features of the embodiments and the embodiments of the present application may be combined with each other without conflict.
First embodiment
Referring to fig. 1, a domain name connection method of SaaS service in a first embodiment of the present invention is shown, the method specifically includes steps S10-S30B 2:
step S10, when receiving a SaaS service request sent by a user, acquiring a domain name priority order list and determining whether the client is in a blown state.
The domain name priority order list comprises a plurality of domain names, the domain name with the highest priority is a main domain name, and the other domain names are standby domain names. Main domain name: when a user initiates a request for the SaaS service, the domain name used in the first place is selected; preparing a domain name: when a user initiates a request for the SaaS service, if the main domain name is unavailable, the standby domain name is used for service request. I.e. when the primary domain name is not available, the client will be in a blown state. The service request is made using the alternate domain name.
Specifically, whether the client is in a fusing state is determined through a fusing threshold, and the fusing threshold is used for judging whether the domain name needs to be fused. When the domain name is used for accessing the SaaS service, if the continuous failure times are larger than the fusing threshold value, the client side enters the fusing state.
In step S20A, if the client is not in the blown state, the SaaS service is accessed using the master domain name.
Step S20B, if the client is in the fusing state, determine whether the standby domain name in the domain name priority order list is unavailable.
And step S30B1, if the standby domain name in the domain name priority order list is available, accessing the SaaS service by using the available standby domain name.
And step S30B2, if the standby domain names in the domain name priority sequence list are unavailable, accessing the SaaS service by using the domain name set by the user or the default domain name.
The default domain name is a batch of SaaS service domain names configured in the SDK by default, and when the domain name is not set by a user, the built-in default domain name is used for requesting the SaaS service.
The invention provides a domain name connection method of SaaS service, which comprises the steps of acquiring a domain name priority sequence list and determining whether a client is in a fusing state or not when receiving a SaaS service request sent by a user, wherein the domain name with the highest priority in the domain name priority sequence list is a main domain name, and the other domain names are standby domain names; if the client is not in a fusing state, using the main domain name to access the SaaS service; if the client is in a fusing state, determining whether the standby domain names in the domain name priority sequence list are unavailable; if the standby domain name in the domain name priority sequence list is available, the available standby domain name is used for accessing the SaaS service; and if the standby domain names in the domain name priority sequence list are unavailable, accessing the SaaS service by using the domain name set by the user or the default domain name. Therefore, when the SaaS service is requested, if some domain names cannot be used due to special reasons, the most appropriate available domain name can be calculated according to an algorithm, and domain name switching is automatically realized, so that the high availability of the service is ensured.
Second embodiment
Referring to fig. 2, before obtaining the domain name priority order table, the method further includes:
step S101, determining whether the SaaS service request contains a domain name of fixed connection.
The domain name of the fixed connection is a specified domain name selected by a user, namely the domain name does not change in the process of using the SaaS service, and the SaaS service is requested through the specified domain name of the user.
In step S102A, if the domain name includes the domain name of the fixed connection, a domain name configuration list is generated according to the domain name of the fixed connection.
For example, if there are 5 domain names of the fixed connection set by the user, a domain name configuration list is generated according to the 5 domain names of the fixed connection, where the domain name configuration list includes the 5 domain names set by the user.
In step S102B, if the domain name of the fixed connection is not included, it is determined whether the SaaS service request includes the domain name of the non-fixed connection.
The domain name of the non-fixed connection can be a domain name set by a user, and a domain name configuration list for accessing the SaaS service can be pulled by the SaaS service through the set domain name.
It should be noted that the domain name of the non-fixed connection is different from the domain name of the fixed connection, and although the domain names of the two types are set by the user, the domain name of the fixed connection does not change during the use of the SaaS service, the SaaS service is requested through a specified domain name set by the user, and the domain name of the non-fixed connection is a basis for acquiring a domain name configuration list, that is, the domain name configuration list for accessing the SaaS service is pulled by the SaaS service according to the domain name of the non-fixed connection.
Step S103B1, if the domain name includes the domain name of the non-fixed connection, obtaining the domain name configured by the user on the SaaS platform through the domain name of the non-fixed connection to obtain the domain name configuration list.
Step S103B2, if the domain name configuration list is not included in the non-fixedly connected domain name or is not successfully acquired through the non-fixedly connected domain name, generate a domain name configuration list according to the non-fixedly connected domain name or the built-in default domain name.
In the embodiment of the invention, when a user initiates a SaaS service request, the domain name is set according to a mode selected by the user. When a user selects a specified domain name (a fixedly connected domain name), namely the domain name does not change in the process of using the SaaS service, the domain name configured by the user is used as a domain name configuration list for finally accessing the SaaS service; when the user does not specify the domain name, if the user sets the domain name (the domain name of the non-fixed connection), the domain name configuration list for accessing the SaaS service is pulled according to the domain name set by the user to the SaaS service, and the domain name configuration list is used as the domain name for finally accessing the SaaS service. And if the user is not set, the SDK built-in domain name is used for the SaaS service to obtain a domain name configuration list.
Third embodiment
Referring to fig. 3, the obtaining of the domain name priority order list includes:
step S201, determining whether the detection times of the domain name configuration list are less than or equal to preset times.
The preset times can be set according to actual requirements, for example, the preset times are 10, 15, 20, and the like, and the embodiment of the present invention is not particularly limited.
It should be noted that before determining whether the number of times of detection of the domain name configuration list is less than or equal to the preset number of times, it is necessary to determine whether the number of domain names in the domain name configuration list is greater than 1, and if so, it is determined whether the number of times of detection of the domain name configuration list is less than or equal to the preset number of times, otherwise, the process of obtaining the domain name priority order list is not required to be performed.
Step S202A, if the detection times are greater than or equal to the preset times, traversing each domain name in the domain name configuration list, sending a SaaS service request using each domain name, and recording the times of success of each domain name request.
For example, if the preset number of times is 15, 15 times of detection data (detection is to send a request without a service attribute to the SaaS service and check the network status of the domain name) are obtained, each time, a simulation request is made for all the domain names in the domain name configuration list, and then the number of times of success of the request for each domain name is calculated, and if 15 times of success of one domain name is achieved, the number of times of success of the request is 15.
Step S202B, if the detection times are greater than the preset times, calculating the priority of each domain name according to the times of successful domain name request and the GAP number.
The GAP progression function is to add corresponding GAP progression to domain names with different priorities when domain name sorting is performed, so that the domain names show the priority function when being sorted. The GAP number is a point value for distinguishing the priority of two domain names, when the scoring calculation value of the second domain name is similar to that of the first domain name (the probability is high when the network conditions are similar), the selected domain name will change continuously, and a proper point value needs to be added to distinguish the two priority. Specifically, the GAP number is an empirical value determined based on long-term observation and analysis of such domain name perturbation problems under normal conditions.
Specifically, the priority number of each domain name is calculated according to the formula (success times 100)/15+ GAP number. And sequencing the priority number, wherein the domain names with higher priority number are used preferentially, and then the main domain name and the standby domain name are sequentially arranged according to the domain name sequence.
Step S203B, sort the domain names in the domain name configuration list according to the priority number from large to small to obtain the domain name priority order list.
In an embodiment provided by the present invention, after obtaining the domain name priority order list, the failure times of each domain name in the domain name priority order list need to be cleared, and the fusing state is recovered to the normal state.
Fourth embodiment
Referring to fig. 4, after accessing the SaaS service using the primary domain name, the standby domain name, the domain name set by the user, or the default domain name, the method further includes
Step S301, determining whether the current domain name fails to access the SaaS service.
In step S302A, if the domain name access is successful, the number of times of the current domain name access failure is cleared.
In step S302B, if the domain name access fails, the current number of times of domain name access failure is obtained.
Step S303B1, if the number of access failures reaches the fusing threshold and the current domain name is the primary domain name, setting the client in the fusing state, and accessing the SaaS service using the available standby domain name.
The fusing threshold is used for judging whether the domain name needs to be fused or not. When the domain name is used for accessing the SaaS service, if the number of continuous failures reaches a fusing threshold value, the client side enters a fusing state.
Step S303B2, if the number of access failures reaches the fusing threshold and the current domain name is the standby domain name, the domain name set by the user, or the default domain name, then the next available standby domain name is updated to access the SaaS service.
In an embodiment provided by the invention, if the number of access failures does not reach a fusing threshold, whether the configuration of the SaaS platform changes is determined; if the configuration of the SaaS platform changes, the domain name priority sequence list is obtained again; re-accessing the SaaS service through the main domain name in the domain name priority sequence list which is obtained again; and if the configuration of the SaaS platform is not changed, adding 1 to the current domain name access failure times.
In the embodiment of the invention, if the access failure times of the domain name do not reach the fusing threshold value, the failure times of the domain name plus 1 are recorded and the user request failure is returned at the same time; if the access failure times of the domain name reach a fusing threshold value and the currently used domain name is the main domain name, setting the client state to be a fusing state, and using a standby domain name in subsequent requests; if the number of failures for the domain name reaches the fusing threshold and the currently used domain name is the standby domain name, then the other available standby domain names are used.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
In an embodiment, a domain name connection device of a SaaS service is provided, and the domain name connection device of the SaaS service corresponds to the domain name connection method of the SaaS service in the above embodiment one to one. As shown in fig. 5, the detailed description of each functional module of the domain name connecting device of the SaaS service is as follows:
the acquisition module 10 is configured to, when receiving a SaaS service request sent by a user, acquire a domain name priority order list and determine whether a client is in a fusing state, where a domain name with a highest priority in the domain name priority order list is a main domain name, and the remaining domain names are standby domain names;
an access module 20, configured to access, if the client is not in a blown state, the SaaS service using the master domain name;
a determining module 30, configured to determine whether none of the standby domain names in the domain name priority order list is available if the client is in a blown state;
the access module 20 is further configured to access, if the standby domain name in the domain name priority order list is available, the SaaS service using the available standby domain name;
the access module 20 is further configured to access the SaaS service by using the domain name set by the user or the default domain name if none of the standby domain names in the domain name priority order list is available.
Further, the apparatus further comprises:
the determining module 30 is further configured to determine whether the SaaS service request includes a domain name of a fixed connection;
a generating module 40, configured to generate a domain name configuration list according to the domain name of the fixed connection if the domain name of the fixed connection is included;
the determining module 30 is further configured to determine whether the SaaS service request includes a domain name of a non-fixed connection if the domain name of the fixed connection is not included;
the generating module 40 is further configured to, if the domain name of the non-fixed connection is included, obtain, through the domain name of the non-fixed connection, a domain name configured by the user on the SaaS platform to obtain a domain name configuration list;
the generating module 40 is further configured to generate a domain name configuration list according to the domain name of the non-fixed connection or a built-in default domain name if the domain name of the non-fixed connection is not included or the domain name configuration list is not successfully acquired through the domain name of the non-fixed connection.
The obtaining module 10 is specifically configured to:
determining whether the detection times of the domain name configuration list are less than or equal to preset times;
if the detection times are more than or equal to preset times, traversing each domain name in the domain name configuration list, sending SaaS service requests by using each domain name and recording the times of success of each domain name request;
if the detection times are greater than the preset times, calculating the priority number of each domain name according to the times of successful domain name request and the GAP number;
and sorting the domain names in the domain name configuration list from large to small according to the priority number to obtain the domain name priority sequence list.
Further, the apparatus further comprises:
and the clearing recovery module is used for clearing the failure times of each domain name in the domain name priority sequence list and recovering the fusing state to be the normal state.
Specifically, after the SaaS service is accessed by using the main domain name, the standby domain name, a domain name set by a user, or a default domain name, the determining module 30 is configured to:
determining whether the current domain name fails to access the SaaS service;
if the domain name access is successful, clearing the number of times of current domain name access failure;
if the domain name access fails, acquiring the number of times of the current domain name access failure;
if the access failure times reach a fusing threshold value and the current domain name is the main domain name, setting the client in a fusing state, and accessing the SaaS service by using the available standby domain name;
and if the number of access failures reaches a fusing threshold and the current domain name is the standby domain name, the domain name set by the user or a default domain name, updating the next available standby domain name to access the SaaS service.
The determining module 30 is configured to determine whether the configuration of the SaaS platform changes if the number of access failures does not reach the fusing threshold;
the obtaining module 10 is specifically configured to obtain the domain name priority order list again if the configuration of the SaaS platform changes; re-accessing the SaaS service through the main domain name in the domain name priority sequence list which is obtained again; and if the configuration of the SaaS platform is not changed, adding 1 to the current domain name access failure times.
For specific limitations of the domain name connection device of the SaaS service, reference may be made to the above limitations of the domain name connection method of the SaaS service, and details thereof are not repeated here. The various modules in the above-described apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 6. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a domain name connection method of a SaaS service.
In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
when a SaaS service request sent by a user is received, acquiring a domain name priority sequence list and determining whether a client is in a fusing state, wherein the domain name with the highest priority in the domain name priority sequence list is a main domain name, and the other domain names are standby domain names;
if the client is not in a fusing state, using the main domain name to access the SaaS service;
if the client is in a fusing state, determining whether the standby domain names in the domain name priority sequence list are unavailable;
if the standby domain name in the domain name priority sequence list is available, the available standby domain name is used for accessing the SaaS service;
and if the standby domain names in the domain name priority sequence list are unavailable, accessing the SaaS service by using the domain name set by the user or the default domain name.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
when a SaaS service request sent by a user is received, acquiring a domain name priority sequence list and determining whether a client is in a fusing state, wherein the domain name with the highest priority in the domain name priority sequence list is a main domain name, and the other domain names are standby domain names;
if the client is not in a fusing state, using the main domain name to access the SaaS service;
if the client is in a fusing state, determining whether the standby domain names in the domain name priority sequence list are unavailable;
if the standby domain name in the domain name priority sequence list is available, the available standby domain name is used for accessing the SaaS service;
and if the standby domain names in the domain name priority sequence list are unavailable, accessing the SaaS service by using the domain name set by the user or the default domain name.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions.
The above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.
Claims (10)
1. A domain name connection method of SaaS service is characterized by comprising the following steps:
when a SaaS service request sent by a user is received, acquiring a domain name priority sequence list and determining whether a client is in a fusing state, wherein the domain name with the highest priority in the domain name priority sequence list is a main domain name, and the other domain names are standby domain names;
if the client is not in a fusing state, using the main domain name to access the SaaS service;
if the client is in a fusing state, determining whether the standby domain names in the domain name priority sequence list are unavailable;
if the standby domain name in the domain name priority sequence list is available, the available standby domain name is used for accessing the SaaS service;
and if the standby domain names in the domain name priority sequence list are unavailable, accessing the SaaS service by using the domain name set by the user or the default domain name.
2. The method for connecting domain names of SaaS services according to claim 1, wherein before the obtaining of the domain name priority order table, the method further comprises:
determining whether the SaaS service request contains a fixedly connected domain name;
if the domain name of the fixed connection is contained, generating a domain name configuration list according to the domain name of the fixed connection;
if the domain name of the fixed connection is not contained, determining whether the SaaS service request contains the domain name of the non-fixed connection;
if the domain name of the non-fixed connection is included, acquiring the domain name configured by the user on the SaaS platform through the domain name of the non-fixed connection to obtain a domain name configuration list;
and if the domain name configuration list is not acquired or is not successfully acquired through the domain name of the non-fixed connection, generating a domain name configuration list according to the domain name of the non-fixed connection or a built-in default domain name.
3. The method according to claim 2, wherein the obtaining a domain name priority order table includes:
determining whether the detection times of the domain name configuration list are less than or equal to preset times;
if the detection times are more than or equal to preset times, traversing each domain name in the domain name configuration list, sending SaaS service requests by using each domain name and recording the times of success of each domain name request;
if the detection times are greater than the preset times, calculating the priority number of each domain name according to the times of successful domain name request and the GAP number;
and sorting the domain names in the domain name configuration list from large to small according to the priority number to obtain the domain name priority sequence list.
4. The domain name connection method of SaaS service according to claim 3, characterized in that the method further comprises:
clearing the failure times of each domain name in the domain name priority sequence list, and recovering the fusing state to be the normal state.
5. The method for connecting domain names of SaaS services according to claim 1, wherein after accessing a SaaS service using the primary domain name, the backup domain name, a domain name set by a user, or a default domain name, the method further comprises:
determining whether the current domain name fails to access the SaaS service;
if the domain name access is successful, clearing the number of times of current domain name access failure;
if the domain name access fails, acquiring the number of times of the current domain name access failure;
if the access failure times reach a fusing threshold value and the current domain name is the main domain name, setting the client in a fusing state, and accessing the SaaS service by using the available standby domain name;
and if the number of access failures reaches a fusing threshold and the current domain name is the standby domain name, the domain name set by the user or a default domain name, updating the next available standby domain name to access the SaaS service.
6. The domain name connection method of SaaS service according to claim 5, characterized in that the method further comprises:
if the number of access failures does not reach the fusing threshold value, determining whether the configuration of the SaaS platform changes;
if the configuration of the SaaS platform changes, the domain name priority sequence list is obtained again;
re-accessing the SaaS service through the main domain name in the domain name priority sequence list which is obtained again;
and if the configuration of the SaaS platform is not changed, adding 1 to the current domain name access failure times.
7. A domain name connection apparatus of a SaaS service, the apparatus comprising:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring a domain name priority sequence list and determining whether a client is in a fusing state or not when receiving a SaaS service request sent by a user, the domain name with the highest priority in the domain name priority sequence list is a main domain name, and the other domain names are standby domain names;
the access module is used for accessing the SaaS service by using the main domain name if the client is not in a fusing state;
a determining module, configured to determine whether none of the standby domain names in the domain name priority order list is available if the client is in a blown state;
the access module is further configured to access the SaaS service by using the available standby domain name if the standby domain name in the domain name priority order list is available;
the access module is further configured to access the SaaS service using the domain name set by the user or a default domain name if none of the standby domain names in the domain name priority order list is available.
8. The domain name connection device of SaaS service according to claim 7, characterized in that the device further comprises:
the determining module is further configured to determine whether the SaaS service request includes a domain name of a fixed connection;
the generating module is used for generating a domain name configuration list according to the domain name of the fixed connection if the domain name of the fixed connection is included;
the determining module is further configured to determine whether the SaaS service request includes a domain name of a non-fixed connection if the domain name of the fixed connection is not included;
the generating module is further configured to, if the domain name of the non-fixed connection is included, obtain, through the domain name of the non-fixed connection, a domain name configured by the user on the SaaS platform to obtain a domain name configuration list;
the generating module is further configured to generate a domain name configuration list according to the domain name of the non-fixed connection or a built-in default domain name if the domain name of the non-fixed connection is not included or the domain name configuration list is not successfully acquired through the domain name of the non-fixed connection.
9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the domain name connection method of SaaS service according to any one of claims 1 to 6 when executing the computer program.
10. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the domain name connection method for SaaS service according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110193920.XA CN112954087A (en) | 2021-02-20 | 2021-02-20 | Domain name connection method and device for SaaS (software as a service), computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110193920.XA CN112954087A (en) | 2021-02-20 | 2021-02-20 | Domain name connection method and device for SaaS (software as a service), computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112954087A true CN112954087A (en) | 2021-06-11 |
Family
ID=76244814
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110193920.XA Pending CN112954087A (en) | 2021-02-20 | 2021-02-20 | Domain name connection method and device for SaaS (software as a service), computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112954087A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114465983A (en) * | 2022-01-25 | 2022-05-10 | 百融云创科技股份有限公司 | Multi-domain name based API call automatic switching method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110078278A1 (en) * | 2009-08-27 | 2011-03-31 | International Business Machines Corporation | Method and system and processing http requests |
| CN103238310A (en) * | 2010-12-01 | 2013-08-07 | 诺基亚西门子通信公司 | Apparatus and method for establishing connections |
| CN107920139A (en) * | 2017-11-06 | 2018-04-17 | 顺丰科技有限公司 | A kind of confirmation method of domain name, system, equipment and computer-readable recording medium |
| CN109769040A (en) * | 2018-12-14 | 2019-05-17 | 平安普惠企业管理有限公司 | Content delivery network service switching method, device, equipment and storage medium |
| CN110519409A (en) * | 2019-08-28 | 2019-11-29 | 北京思维造物信息科技股份有限公司 | Domain name Dynamic Configuration, device, equipment and storage medium |
| CN112202760A (en) * | 2020-09-28 | 2021-01-08 | 厦门美柚股份有限公司 | Webpage access method, device, terminal and medium |
-
2021
- 2021-02-20 CN CN202110193920.XA patent/CN112954087A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110078278A1 (en) * | 2009-08-27 | 2011-03-31 | International Business Machines Corporation | Method and system and processing http requests |
| CN103238310A (en) * | 2010-12-01 | 2013-08-07 | 诺基亚西门子通信公司 | Apparatus and method for establishing connections |
| CN107920139A (en) * | 2017-11-06 | 2018-04-17 | 顺丰科技有限公司 | A kind of confirmation method of domain name, system, equipment and computer-readable recording medium |
| CN109769040A (en) * | 2018-12-14 | 2019-05-17 | 平安普惠企业管理有限公司 | Content delivery network service switching method, device, equipment and storage medium |
| CN110519409A (en) * | 2019-08-28 | 2019-11-29 | 北京思维造物信息科技股份有限公司 | Domain name Dynamic Configuration, device, equipment and storage medium |
| CN112202760A (en) * | 2020-09-28 | 2021-01-08 | 厦门美柚股份有限公司 | Webpage access method, device, terminal and medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114465983A (en) * | 2022-01-25 | 2022-05-10 | 百融云创科技股份有限公司 | Multi-domain name based API call automatic switching method and system |
| CN114465983B (en) * | 2022-01-25 | 2024-04-05 | 百融云创科技股份有限公司 | Multi-domain name-based API call automatic switching method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109474668B (en) | CDN service switching method and device, computer equipment and storage medium | |
| CN110727499A (en) | Resource data acquisition method and device, computer equipment and storage medium | |
| US9647892B2 (en) | Cloud-based service resource provisioning based on network characteristics | |
| CN110519409B (en) | Domain name dynamic configuration method, device, equipment and storage medium | |
| CN112153170B (en) | Method, device and equipment for accessing server and storage medium | |
| CN112395140B (en) | A decentralized task scheduling method apparatus, device and medium | |
| CN110677492B (en) | Access request processing method and device, electronic equipment and storage medium | |
| CN110555041A (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN112291365B (en) | Access balance processing method, device, computer equipment and storage medium | |
| EP1728160A2 (en) | Anomaly management scheme for a multi-agent system | |
| CN108595280B (en) | Interface adaptation method and device, computer equipment and storage medium | |
| CN113467780A (en) | Data acquisition method and device, electronic equipment and storage medium | |
| CN112954087A (en) | Domain name connection method and device for SaaS (software as a service), computer equipment and storage medium | |
| CN113535262A (en) | Method, device, equipment and storage medium for controlling starting of proxy node | |
| JP5857806B2 (en) | Distributed processing system test method and distributed processing system | |
| CN109951549B (en) | Network page access method and device and computer readable storage medium | |
| CN111866203B (en) | Domain name resolution method and device, readable storage medium and equipment | |
| CN111049945A (en) | Network request optimization method, device, equipment and medium based on HTTP (hyper text transport protocol) | |
| CN110955460A (en) | Service process starting method and device, electronic equipment and storage medium | |
| CN114422576B (en) | Session cleaning method and device, computer equipment and readable storage medium | |
| CN113014633B (en) | Method and device for positioning preset equipment, computer equipment and storage medium | |
| CN114490681A (en) | Service request response method and device and server cluster | |
| CN115017027A (en) | Interface automation continuous integration test method, device, equipment and storage medium | |
| CN113507415A (en) | Table item processing method and device | |
| CN110955647A (en) | Database assistance method, database assistance device, computer equipment 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210611 |