CN111324843A - Front-end request processing method, device, equipment and readable storage medium - Google Patents
Front-end request processing method, device, equipment and readable storage medium Download PDFInfo
- Publication number
- CN111324843A CN111324843A CN202010097174.XA CN202010097174A CN111324843A CN 111324843 A CN111324843 A CN 111324843A CN 202010097174 A CN202010097174 A CN 202010097174A CN 111324843 A CN111324843 A CN 111324843A
- Authority
- CN
- China
- Prior art keywords
- end request
- service
- processing
- background service
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- 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/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- 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/953—Querying, e.g. by the use of web search engines
Abstract
The application discloses a front-end request processing method, a device, equipment and a readable storage medium; in the method, a gateway is added between a front-end webpage and a background service to serve as an intermediate layer. The gateway can acquire the front-end requests, determine a target background service corresponding to each front-end request, and forward the front-end requests to the target background services, so that the target background services process the corresponding front-end requests. Therefore, the front-end page and the background service do not need to be subjected to different processing due to different services, but are unified interfaces, namely gateways, so that the background service can process the front-end request, decoupling between the front-end page and the background service is realized, the front-end request of the front-end page can be further subjected to unified management, and the logic complexity of the front-end page is reduced.
Description
Technical Field
The present application relates to the field of computer application technologies, and in particular, to a front-end request processing method, apparatus, device, and readable storage medium.
Background
The web pages exist as windows for interaction between the user and the website background, and the web pages in different expression forms bring difficulties for web page development, service/business logic processing, management and the like besides presenting unique characteristics to the user. For example, in an e-commerce site, there is often a case where the top page, shop page, and product detail page of different businesses are different from each other, and the difference is large, and it is difficult to perform convergence and unification processing.
At present, in order to solve the differentiated processing of front-end pages, there are two solutions using more: firstly, each service develops own page function. However, the method is difficult to form a uniform style and user habits, and has low efficiency and poor effect; and secondly, processing the unified page, judging in the front-end code, calling different service interfaces, and performing differential processing. However, the processing logic of the method is complex, the page display is coupled with different service judgment logics, the maintenance cost is high, and the expansibility is poor.
Therefore, the existing solution still has many defects for the differentiated processing of the front-end request generated by the front-end page. Therefore, how to effectively solve the problems of differential processing of front-end pages and the like is a technical problem that needs to be solved urgently by those skilled in the art at present.
Disclosure of Invention
The application aims to provide a front-end request processing method, a front-end request processing device and a readable storage medium, so that front-end requests of different front-end pages are uniformly forwarded to corresponding services through a gateway for processing, the logic complexity of the front-end pages is reduced, and decoupling between the front-end pages and the back-end services is realized.
In order to solve the technical problem, the application provides the following technical scheme:
a front-end request processing method is applied to a gateway and comprises the following steps:
acquiring a front-end request generated by a front-end page;
acquiring a service identifier carried by the front-end request;
determining a target background service corresponding to the service identifier by utilizing a routing rule;
forwarding the front-end request to the target backend service so as to process the front-end request with the target backend service.
Preferably, the obtaining a front-end request generated by a front-end page includes:
intercepting the front-end request by using a reverse proxy server;
and receiving the front-end request sent by the reverse proxy server.
Preferably, the receiving the front-end request sent by the reverse proxy server includes:
and receiving the front-end request sent by the reverse proxy server after load balancing processing.
Preferably, forwarding the front-end request to the target background service includes:
inquiring an equipment list corresponding to the deployment background service from the registry;
and selecting target equipment corresponding to the target background service from the equipment list, and sending the front-end request to the target equipment.
Preferably, the routing rule records a mapping relationship between the service identifier and a service, and the determining, by using the routing rule, a target background service corresponding to the service identifier includes:
determining the target background service corresponding to the service identifier by using the mapping relation; the service identification is any one of a URL, a domain name, and a number.
Preferably, processing the front-end request by using the target background service includes:
receiving response data fed back by the target background service;
and sending the response data to the corresponding front-end page.
Preferably, sending the response data to the corresponding front-end page includes:
performing data processing on the response data, and feeding back a processing result to the front-end page; the data processing comprises at least one of encryption and decryption processing, data screening processing, backup processing and blocking processing.
A front-end request processing device applied to a gateway comprises:
the front-end request acquisition module is used for acquiring a front-end request generated by a front-end page;
a service identifier obtaining module, configured to obtain a service identifier carried by the front-end request;
the service query module is used for determining a target background service corresponding to the service identifier by utilizing a routing rule;
and the front-end request forwarding module is used for forwarding the front-end request to the target background service so as to process the front-end request by using the target background service.
A front-end request processing device, comprising:
a memory for storing a computer program;
and the processor is used for realizing the steps of the front-end request processing method when executing the computer program.
A readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the above-described front-end request processing method.
The method provided by the application is applied to the gateway and comprises the following steps: acquiring a front-end request generated by a front-end page; acquiring a service identifier carried by a front-end request; determining a target background service corresponding to the service identifier by using a routing rule; the front-end request is forwarded to the target backend service for processing of the front-end request with the target backend service.
In the method, a gateway is added between a front-end webpage and a background service to serve as an intermediate layer. The gateway can acquire the front-end requests, determine a target background service corresponding to each front-end request, and forward the front-end requests to the target background services, so that the target background services process the corresponding front-end requests. It can be seen that, different front-end pages and background services do not need to perform different processing due to different services, but are unified interfaces, that is, the gateway forwards the front-end request to implement association between the front-end page and the background service, so that the background service processes the front-end request, decoupling between the front-end page and the background service is implemented, the front-end request of the front-end page can be further managed in a unified manner, and the logic complexity of the front-end page is reduced.
Accordingly, embodiments of the present application further provide a front-end request processing apparatus, a device, and a readable storage medium corresponding to the front-end request processing method, which have the above technical effects and are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart illustrating an implementation of a front-end request processing method according to an embodiment of the present application;
fig. 2 is a schematic diagram of a gateway application system architecture in an embodiment of the present application;
fig. 3 is a timing diagram of a gateway process according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a front-end request processing apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a front-end request processing device in an embodiment of the present application;
fig. 6 is a schematic structural diagram of a front-end request processing device in an embodiment of the present application.
Detailed Description
In order that those skilled in the art will better understand the disclosure, the following detailed description will be given with reference to the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The first embodiment is as follows:
referring to fig. 1, fig. 1 is a flowchart illustrating a front-end request processing method according to an embodiment of the present invention, which can be applied to a gateway (also referred to as an internet connector, a protocol converter). Fig. 2 shows a specific association relationship between the gateway and the front-end page and the background service. Namely, a layer of gateway is added between a front-end request generated by the existing front-end page and a background service, and the gateway is used as an intermediate layer and is uniformly distributed to different business back-end services according to a regular route. Specifically, the method comprises the following steps:
a first layer: the front end converges the page, and different services do not need to be subjected to difference processing;
a second layer: the gateway performs unified processing, and forwards the data to different service backend services according to different rules;
and a third layer: the background services process the received front-end request based on the business logic of the background services.
Specifically, a method for processing a front-end request applied to a gateway includes the following steps:
s101, acquiring a front-end request generated by a front-end page.
The front-end page may be a web page visible to the user/display page, such as any one of a home page of different services in an e-commerce website, a shop page, and a commodity detail page.
In the present application, a gateway may obtain a front-end request generated by a front-end page. The front-end request may specifically be a REST request initiated by a display page to a background service. REST (representational State transfer), namely a software architecture style, is a design and development mode aiming at network application, can reduce the development complexity and improve the scalability of a system.
Specifically, the gateway may obtain the front-end requests corresponding to different front-end pages by setting a front-end request intercepting logic (for example, a functional logic such as a reverse proxy server may be set), or may directly obtain the front-end requests by using the reverse proxy server. The process of obtaining the front-end request through the reverse proxy server may include:
intercepting a front-end request by using a reverse proxy server;
and step two, receiving a front-end request sent by the reverse proxy server.
For convenience of description, the above two steps will be described in combination.
The Reverse Proxy (Reverse Proxy) mode is that a Proxy server receives a connection request on the internet, then forwards the request to a server on an internal network, and returns a result obtained from the server to a client requesting connection on the internet, and at this time, the Proxy server externally appears as a server.
In the application, the reverse proxy server can intercept the front-end requests of the front-end pages, and then the reverse proxy server can obtain the front-end requests by receiving the front-end requests sent by the reverse proxy server.
For example, the following steps are carried out: and the nginx intercepts the front-end request to the gateway service, and the load balancing function of the nginx is fully utilized in the step, so that the gateway avoids too many single-point requests. Nginx is a high performance HTTP and reverse proxy server, and is also an IMAP/POP3/SMTP server.
Preferably, considering the type and number of front-end pages in practical application, and further making the number of front-end requests larger, in order to avoid the occurrence of a single gateway performance upper limit limiting the response speed of the whole system, a plurality of gateways may be further provided, and load balancing of the gateways may be realized through the reverse proxy server. That is, the gateway may receive the front-end request sent by the reverse proxy server after load balancing processing. Therefore, the gateway can avoid excessive single-point requests.
That is, different front-end pages initiate front-end requests, and different services are not distinguished, and the entries are unified, so that the front-end requests are all acquired by the gateway.
S102, acquiring a service identifier carried by the front-end request.
The service identifier may be specifically an identifier capable of uniquely determining a service for processing the front-end request.
In each front-end request, its corresponding service identification may be carried. The service identifier may specifically be a domain name, a URL (Uniform Resource Locator, also called a web Address, which is an Address of a standard Resource on the internet), a service number, and other identifiers of the service.
S103, determining the target background service corresponding to the service identifier by using the routing rule.
The routing rule describes the corresponding relationship between each service identifier and each service, so as to determine the route of each front-end request. In other words, by querying the routing rule, the target background service corresponding to each service identifier can be determined. It should be noted that, in the present application, a service refers to a background service, and corresponds to a service logic processing layer.
Specifically, the routing rule records a mapping relationship between the service identifier and the service, and determines a target background service corresponding to the service identifier, that is, the target background service corresponding to the service identifier is determined by using the mapping relationship; the service identification is any one of a URL, a domain name, and a number. That is, one front-end request can only correspond to one target background service.
And S104, forwarding the front-end request to the target background service so as to process the front-end request by using the target background service.
After the corresponding relation between the front-end request and the target background service is determined, the front-end request can be forwarded to the corresponding target background service.
Specifically, the process of forwarding the front-end request to the target background service may include:
step one, inquiring an equipment list corresponding to deployment background service from a registry;
and step two, selecting target equipment corresponding to the target background service from the equipment list, and sending a front-end request corresponding to the target background service to the target equipment.
For convenience of description, the above two steps will be described in combination.
Since both the backend service and the gateway are registered in the registry when being started, in the application, the gateway can inquire the device list corresponding to the deployed target background service from the registry, and then select the target device from the device list. And then, sending the front-end request corresponding to the target background service to the target equipment so that the target background service can process the front-end request.
Preferably, in order to improve system performance, a background service may be deployed on multiple devices, so that when a front-end request is forwarded, when a target background service corresponding to the front-end request is deployed on multiple devices, the front-end request may also be forwarded through load balancing.
The method for processing the front-end request by using the target background service comprises the following steps:
step one, receiving response data fed back by a target background service;
and step two, sending the response data to the corresponding front-end page.
That is, each target background service processes the front-end request based on its own business processing logic after receiving the front-end request. And in the processing process, the target background service responds to the gateway fed back by the data. After receiving the response data, the gateway can feed back the response data to the front-end page.
Preferably, when the gateway forwards the response data, the gateway can also perform data processing on the response data to implement functions of data encryption, data screening, block transmission and the like. That is, the second step may specifically be to perform data processing on the response data and feed back the processing result to the front-end page; the data processing comprises at least one of encryption and decryption processing, data screening processing, backup processing and blocking processing. The specific implementation logic of data processing may refer to the existing processing logic, and is not described in detail herein.
In order to make those skilled in the art better understand the front-end request processing method provided in the embodiments of the present application, the following describes the above steps in detail with reference to a specific timing diagram of the gateway.
Referring to fig. 3, the specific implementation process of the method includes:
step 1, the front end page initiates a front end request.
The front-end page does not need to distinguish different services and unifies the entries.
And 2, the nginx intercepts the front-end request to the gateway service.
Particularly, in step 2, when a plurality of gateways exist, the load balancing function of nginx can be fully utilized, so that the gateways avoid excessive single-point requests.
And 3, forwarding the request to different services by the gateway according to the routing rule.
For example, each background service (i.e., traffic) may have its own separate domain name, and routing rules may be handled according to different domain names.
And 4, the service back-end processes own logic and returns data to the front-end page.
The gateway configuration comprises a corresponding relation between a domain name and a service backend service; the method comprises the following steps that both a back-end service and a gateway are registered in a registration center when being started, and after the gateway analyzes a gateway configuration rule, the gateway can find a corresponding address in the registration center according to the id of the back-end service; when the same back-end service is deployed on multiple devices, the gateway can also perform load balancing on the back-end service.
The method provided by the application is applied to the gateway and comprises the following steps: acquiring a front-end request generated by a front-end page; acquiring a service identifier carried by a front-end request; determining a target background service corresponding to the service identifier by using a routing rule; the front-end request is forwarded to the target backend service for processing of the front-end request with the target backend service.
In the method, a gateway is added between a front-end webpage and a background service to serve as an intermediate layer. The gateway can acquire the front-end requests, determine a target background service corresponding to each front-end request, and forward the front-end requests to the target background services, so that the target background services process the corresponding front-end requests. It can be seen that, different front-end pages and background services do not need to perform different processing due to different services, but are unified interfaces, that is, the gateway forwards the front-end request to implement association between the front-end page and the background service, so that the background service processes the front-end request, decoupling between the front-end page and the background service is implemented, the front-end request of the front-end page can be further managed in a unified manner, and the logic complexity of the front-end page is reduced.
Example two:
corresponding to the above method embodiments, the present application further provides a front-end request processing apparatus, which can be applied in a gateway, and the front-end request processing apparatus described below and the front-end request processing method described above can be referred to correspondingly.
Referring to fig. 4, the apparatus includes the following modules:
a front-end request obtaining module 101, configured to obtain a front-end request generated by a front-end page;
a service identifier obtaining module 102, configured to obtain a service identifier carried by a front-end request;
the service query module 103 is configured to determine, by using the routing rule, a target background service corresponding to the service identifier;
a front-end request forwarding module 104, configured to forward the front-end request to the target background service, so as to process the front-end request by using the target background service.
The device provided by the application is applied to the gateway and comprises the following components: acquiring a front-end request generated by a front-end page; acquiring a service identifier carried by a front-end request; determining a target background service corresponding to the service identifier by using a routing rule; the front-end request is forwarded to the target backend service for processing of the front-end request with the target backend service.
In the device, a gateway is added between a front-end webpage and a background service to serve as an intermediate layer. The gateway can acquire the front-end requests, determine a target background service corresponding to each front-end request, and forward the front-end requests to the target background services, so that the target background services process the corresponding front-end requests. It can be seen that, different front-end pages and background services do not need to perform different processing due to different services, but are unified interfaces, that is, the gateway forwards the front-end request to implement association between the front-end page and the background service, so that the background service processes the front-end request, decoupling between the front-end page and the background service is implemented, the front-end request of the front-end page can be further managed in a unified manner, and the logic complexity of the front-end page is reduced.
In a specific embodiment of the present application, the front-end request obtaining module 101 is specifically configured to intercept a front-end request by using a reverse proxy server; and receiving a front-end request sent by the reverse proxy server.
In a specific embodiment of the present application, the front-end request obtaining module 101 is specifically configured to receive a front-end request sent by a reverse proxy server after load balancing processing.
In a specific embodiment of the present application, the front-end request forwarding module 104 is specifically configured to query, from a registry, an equipment list corresponding to deployment background services; and selecting target equipment corresponding to the target background service from the equipment list, and sending the front-end request to the target equipment.
In a specific embodiment of the present application, the routing rule records a mapping relationship between the service identifier and the service, and accordingly, the service query module 103 is specifically configured to determine, by using the mapping relationship, a target background service corresponding to the service identifier; the service identification is any one of a URL, a domain name, and a number.
In a specific embodiment of the present application, the front-end request forwarding module 104 is specifically configured to receive response data fed back by the target background service; and sending the response data to the corresponding front-end page.
In a specific embodiment of the present application, the front-end request forwarding module 104 is specifically configured to perform data processing on the response data, and feed back a processing result to the front-end page; the data processing comprises at least one of encryption and decryption processing, data screening processing, backup processing and blocking processing.
Example three:
corresponding to the above method embodiment, the present application further provides a front-end request processing device, and a front-end request processing device described below and a front-end request processing method described above may be referred to correspondingly.
Referring to fig. 5, the front-end request processing apparatus includes:
a memory D1 for storing computer programs;
the processor D2 is configured to implement the steps of the front-end request processing method of the above-mentioned method embodiment when executing the computer program.
Specifically, referring to fig. 6, a specific structural diagram of a front-end request processing device provided in this embodiment is shown, where the front-end request processing device may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 322 (e.g., one or more processors) and a memory 332, and one or more storage media 330 (e.g., one or more mass storage devices) storing an application 342 or data 344. Memory 332 and storage media 330 may be, among other things, transient storage or persistent storage. The program stored on the storage medium 330 may include one or more modules (not shown), each of which may include a series of instructions operating on a data processing device. Still further, the central processor 322 may be configured to communicate with the storage medium 330 to execute a series of instruction operations in the storage medium 330 on the front-end request processing device 301.
The front-end request processing apparatus 301 may also include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input-output interfaces 358, and/or one or more operating systems 341. Such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
The steps in the front-end request processing method described above may be implemented by the structure of the front-end request processing device.
Example four:
corresponding to the above method embodiment, this application embodiment further provides a readable storage medium, and a readable storage medium described below and a front-end request processing method described above may be referred to correspondingly.
A readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the front-end request processing method of the above-mentioned method embodiment.
The readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and various other readable storage media capable of storing program codes.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
Claims (10)
1. A front-end request processing method is applied to a gateway and comprises the following steps:
acquiring a front-end request generated by a front-end page;
acquiring a service identifier carried by the front-end request;
determining a target background service corresponding to the service identifier by utilizing a routing rule;
forwarding the front-end request to the target backend service so as to process the front-end request with the target backend service.
2. The front-end request processing method according to claim 1, wherein the obtaining of the front-end request generated by the front-end page comprises:
intercepting the front-end request by using a reverse proxy server;
and receiving the front-end request sent by the reverse proxy server.
3. The front-end request processing method according to claim 2, wherein receiving the front-end request sent by the reverse proxy server comprises:
and receiving the front-end request sent by the reverse proxy server after load balancing processing.
4. The front-end request processing method according to claim 1, wherein forwarding the front-end request to the target background service comprises:
inquiring an equipment list corresponding to the deployment background service from the registry;
and selecting target equipment corresponding to the target background service from the equipment list, and sending the front-end request to the target equipment.
5. The front-end request processing method according to claim 1, wherein the routing rule records a mapping relationship between the service identifier and a service, and the determining, by using the routing rule, a target background service corresponding to the service identifier includes:
determining the target background service corresponding to the service identifier by using the mapping relation; the service identification is any one of a URL, a domain name, and a number.
6. The front-end request processing method according to claim 1, wherein processing the front-end request by using the target background service comprises:
receiving response data fed back by the target background service;
and sending the response data to the corresponding front-end page.
7. The front-end request processing method according to claim 6, wherein sending the response data to the corresponding front-end page comprises:
performing data processing on the response data, and feeding back a processing result to the front-end page; the data processing comprises at least one of encryption and decryption processing, data screening processing, backup processing and blocking processing.
8. A front-end request processing apparatus, applied to a gateway, comprising:
the front-end request acquisition module is used for acquiring a front-end request generated by a front-end page;
a service identifier obtaining module, configured to obtain a service identifier carried by the front-end request;
the service query module is used for determining a target background service corresponding to the service identifier by utilizing a routing rule;
and the front-end request forwarding module is used for forwarding the front-end request to the target background service so as to process the front-end request by using the target background service.
9. A front-end request processing device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the front-end request processing method as claimed in any one of claims 1 to 7 when executing the computer program.
10. A readable storage medium, having stored thereon a computer program which, when being executed by a processor, carries out the steps of the front-end request processing method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010097174.XA CN111324843A (en) | 2020-02-17 | 2020-02-17 | Front-end request processing method, device, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010097174.XA CN111324843A (en) | 2020-02-17 | 2020-02-17 | Front-end request processing method, device, equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111324843A true CN111324843A (en) | 2020-06-23 |
Family
ID=71172112
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010097174.XA Pending CN111324843A (en) | 2020-02-17 | 2020-02-17 | Front-end request processing method, device, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111324843A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111881394A (en) * | 2020-07-28 | 2020-11-03 | 万商云集(成都)科技股份有限公司 | Request processing method and system for application intermediate layer |
| CN112351059A (en) * | 2020-07-30 | 2021-02-09 | 中兴通讯股份有限公司 | Request processing method and device, electronic equipment and computer-readable storage medium |
| CN112463324A (en) * | 2020-11-25 | 2021-03-09 | 银盛支付服务股份有限公司 | Method for realizing front-end and back-end separation, computer equipment and storage medium |
| CN112528274A (en) * | 2020-12-24 | 2021-03-19 | 微医云(杭州)控股有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN112667204A (en) * | 2020-12-15 | 2021-04-16 | 南方电网数字电网研究院有限公司 | Data processing method and device for microservice application and computer equipment |
| CN113204405A (en) * | 2021-05-21 | 2021-08-03 | 乐视致新信息技术(武汉)有限公司 | Page data acquisition method, device, equipment and computer readable storage medium |
| CN113641579A (en) * | 2021-08-10 | 2021-11-12 | 中国平安人寿保险股份有限公司 | Data processing method, device, equipment and storage medium |
| CN114760357A (en) * | 2022-03-23 | 2022-07-15 | 北京字节跳动网络技术有限公司 | Request processing method and device, computer equipment and storage medium |
| CN115102939A (en) * | 2022-06-02 | 2022-09-23 | 珠海格力电器股份有限公司 | Shortcut application interaction method, system and computer storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130204838A1 (en) * | 2009-08-18 | 2013-08-08 | Verising, Inc | Method and system for intelligent many-to-many service routing over epp |
| US20150310126A1 (en) * | 2014-04-23 | 2015-10-29 | Akamai Technologies, Inc. | Creation and delivery of pre-rendered web pages for accelerated browsing |
| CN107645508A (en) * | 2017-10-16 | 2018-01-30 | 深圳市买买提乐购金融服务有限公司 | A kind of data handling system, method, client and server |
| CN109542427A (en) * | 2018-11-30 | 2019-03-29 | 深圳市元征科技股份有限公司 | A kind of system customization method, apparatus and electronic equipment and storage medium |
| US20190227856A1 (en) * | 2018-01-19 | 2019-07-25 | Boe Technology Group Co., Ltd. | Application programming interface (api) service apparatus and application programming interface (api) service system |
| CN110225099A (en) * | 2019-05-20 | 2019-09-10 | 中国平安财产保险股份有限公司 | A kind of data processing method, front-end client, back-end server and storage medium |
-
2020
- 2020-02-17 CN CN202010097174.XA patent/CN111324843A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130204838A1 (en) * | 2009-08-18 | 2013-08-08 | Verising, Inc | Method and system for intelligent many-to-many service routing over epp |
| US20150310126A1 (en) * | 2014-04-23 | 2015-10-29 | Akamai Technologies, Inc. | Creation and delivery of pre-rendered web pages for accelerated browsing |
| CN107645508A (en) * | 2017-10-16 | 2018-01-30 | 深圳市买买提乐购金融服务有限公司 | A kind of data handling system, method, client and server |
| US20190227856A1 (en) * | 2018-01-19 | 2019-07-25 | Boe Technology Group Co., Ltd. | Application programming interface (api) service apparatus and application programming interface (api) service system |
| CN109542427A (en) * | 2018-11-30 | 2019-03-29 | 深圳市元征科技股份有限公司 | A kind of system customization method, apparatus and electronic equipment and storage medium |
| CN110225099A (en) * | 2019-05-20 | 2019-09-10 | 中国平安财产保险股份有限公司 | A kind of data processing method, front-end client, back-end server and storage medium |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111881394A (en) * | 2020-07-28 | 2020-11-03 | 万商云集(成都)科技股份有限公司 | Request processing method and system for application intermediate layer |
| CN111881394B (en) * | 2020-07-28 | 2024-01-12 | 万商云集(成都)科技股份有限公司 | Request processing method and system for application middle layer |
| CN112351059A (en) * | 2020-07-30 | 2021-02-09 | 中兴通讯股份有限公司 | Request processing method and device, electronic equipment and computer-readable storage medium |
| CN112463324A (en) * | 2020-11-25 | 2021-03-09 | 银盛支付服务股份有限公司 | Method for realizing front-end and back-end separation, computer equipment and storage medium |
| CN112667204A (en) * | 2020-12-15 | 2021-04-16 | 南方电网数字电网研究院有限公司 | Data processing method and device for microservice application and computer equipment |
| CN112667204B (en) * | 2020-12-15 | 2024-01-23 | 南方电网数字平台科技(广东)有限公司 | Data processing method and device for micro-service application and computer equipment |
| CN112528274A (en) * | 2020-12-24 | 2021-03-19 | 微医云(杭州)控股有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN112528274B (en) * | 2020-12-24 | 2023-09-22 | 微医云(杭州)控股有限公司 | Data processing method, device, electronic equipment and storage medium |
| CN113204405A (en) * | 2021-05-21 | 2021-08-03 | 乐视致新信息技术(武汉)有限公司 | Page data acquisition method, device, equipment and computer readable storage medium |
| CN113641579A (en) * | 2021-08-10 | 2021-11-12 | 中国平安人寿保险股份有限公司 | Data processing method, device, equipment and storage medium |
| CN114760357A (en) * | 2022-03-23 | 2022-07-15 | 北京字节跳动网络技术有限公司 | Request processing method and device, computer equipment and storage medium |
| CN115102939A (en) * | 2022-06-02 | 2022-09-23 | 珠海格力电器股份有限公司 | Shortcut application interaction method, system and computer storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111324843A (en) | Front-end request processing method, device, equipment and readable storage medium | |
| CN109618005B (en) | Method for calling server and proxy server | |
| US9712422B2 (en) | Selection of service nodes for provision of services | |
| US10601767B2 (en) | DNS query processing based on application information | |
| US7822839B1 (en) | Method and system for accessing network services | |
| CN107528862B (en) | Domain name resolution method and device | |
| CN110049022B (en) | Domain name access control method and device and computer readable storage medium | |
| US10148741B2 (en) | Multi-homing load balancing system | |
| CN113452592B (en) | Cross-cloud data access method and device under hybrid cloud architecture | |
| CN109729187B (en) | Proxy communication method, system, device and storage medium | |
| WO2017177437A1 (en) | Domain name resolution method, device, and system | |
| US11582153B2 (en) | Load-balancing establishment of connections among groups of connector servers | |
| CN112104640B (en) | Data processing method, device and equipment of gateway and readable storage medium | |
| JP2019525604A (en) | Network function NF management method and NF management apparatus | |
| WO2015039475A1 (en) | Method, server, and system for domain name resolution | |
| CN111917900A (en) | Request processing method and device for domain name proxy | |
| CN110677475A (en) | Micro-service processing method, device, equipment and storage medium | |
| EP4033719A1 (en) | System for providing exact communication delay protection of request response for distributed service | |
| CN111726400A (en) | Reverse connection method, device and server-side system | |
| CN111600929B (en) | Transmission line detection method, routing strategy generation method and proxy server | |
| US20150304442A1 (en) | Website product integration and caching via domain name routing rules | |
| CN112968965A (en) | Metadata service method, server and storage medium for NFV network node | |
| CN104092751A (en) | Service access method and device | |
| US20150304235A1 (en) | Allocating and accessing website resources via domain name routing rules | |
| CN112231566B (en) | Information pushing method, device, system and readable 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 |