CN110113394A - API Calls method and apparatus - Google Patents
API Calls method and apparatus Download PDFInfo
- Publication number
- CN110113394A CN110113394A CN201910320362.1A CN201910320362A CN110113394A CN 110113394 A CN110113394 A CN 110113394A CN 201910320362 A CN201910320362 A CN 201910320362A CN 110113394 A CN110113394 A CN 110113394A
- Authority
- CN
- China
- Prior art keywords
- api
- gateway
- target api
- call request
- destination service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
-
- 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application provides a kind of API Calls method and apparatus, is applied to gateway system, and the gateway system provides multiple application programming interface API, which comprises receives the call request for target API that application program is sent;The target API is called, to be based on the corresponding destination service of the target API, the parameter in the call request is handled;Parameter processing result is returned into the application program.
Description
Technical field
This application involves field of computer technology more particularly to a kind of API Calls method and apparatus.
Background technique
For the Internet company large-scale for one, often there are many systems in inside, they are typically distributed across difference
Server on, pass through various agreements and various services be provided.In addition many companies all take the framework of serviceization, i.e., each industry
It is just needed to configure when being engaged in being safeguarded as a service by special team, and independently dispose, therefore access these services
Different addresses, operation is relatively complicated, is also not easy to the maintenance for each service.
Summary of the invention
The application provides a kind of API Calls method and apparatus, and specifically, the application is to be achieved through the following technical solutions
:
In a first aspect, the application provides a kind of API Calls method, the method is applied to gateway system, the gateway system
System provides multiple application programming interface API, comprising:
Receive the call request for target API from application program;
The target API is called, to be based on the corresponding destination service of the target API, to the ginseng in the call request
Number is handled;
Parameter processing result is returned into the application program.
Second aspect, the application provide a kind of API Calls device, and described device is applied to gateway system, the gateway system
System provides multiple application programming interface API, comprising:
Receiving unit, for receiving the call request for target API from application program;
Call unit, for calling the target API, to be based on the corresponding destination service of the target API, to the tune
It is handled with the parameter in request;
Return unit, for parameter processing result to be returned to the application program.
Analyze above-mentioned technical proposal it is found that by as calling API service traffics unified entrance gateway system, can
To be managed collectively to API, and the address by gateway system is only needed, different API can be called, realizes different services
Access simplifies API Calls operation, convenient for carrying out maintenance and management to different services.
Detailed description of the invention
Fig. 1 is a kind of schematic diagram of API Calls system shown in one exemplary embodiment of the application;
Fig. 2 is a kind of flow chart of API Calls method shown in one exemplary embodiment of the application;
Fig. 3 is a kind of schematic diagram of gateway system shown in one exemplary embodiment of the application;
Fig. 4 is the schematic diagram of another gateway system shown in one exemplary embodiment of the application;
Fig. 5 is the schematic diagram of another gateway system shown in one exemplary embodiment of the application;
Fig. 6 is the schematic diagram of another gateway system shown in one exemplary embodiment of the application;
Fig. 7 is a kind of hardware configuration of API Calls device place gateway system shown in one exemplary embodiment of the application
Figure;
Fig. 8 is a kind of block diagram of API Calls device shown in one exemplary embodiment of the application.
Specific embodiment
Example embodiments are described in detail here, and the example is illustrated in the accompanying drawings.Following description is related to
When attached drawing, unless otherwise indicated, the same numbers in different drawings indicate the same or similar elements.Following exemplary embodiment
Described in embodiment do not represent all embodiments consistent with the application.On the contrary, they be only with it is such as appended
The example of the consistent device and method of some aspects be described in detail in claims, the application.
It is only to be not intended to be limiting the application merely for for the purpose of describing particular embodiments in term used in this application.
It is also intended in the application and the "an" of singular used in the attached claims, " described " and "the" including majority
Form, unless the context clearly indicates other meaning.It is also understood that term "and/or" used herein refers to and wraps
It may be combined containing one or more associated any or all of project listed.
It will be appreciated that though various information, but this may be described using term first, second, third, etc. in the application
A little information should not necessarily be limited by these terms.These terms are only used to for same type of information being distinguished from each other out.For example, not departing from
In the case where the application range, the first information can also be referred to as the second information, and similarly, the second information can also be referred to as
One information.Depending on context, word as used in this " if " can be construed to " ... when " or " when ...
When " or " in response to determination ".
Referring to FIG. 1, Fig. 1 is a kind of schematic diagram of API Calls system shown in one exemplary embodiment of the application.
In API Calls system as shown in Figure 1, gateway system can be only made of a server, be also possible to by
The distributed system of multiple servers composition.
For distributed network gate system, multiple gateway examples can be divided into;Wherein, gateway example is specific
Quantity can be set according to actual needs.In practical applications, when some gateway example in these gateway examples occurs
Problem and when leading to not normally provide service, other gateway examples still can normally provide service, so as to improve point
The reliability of cloth gateway.
Gateway system, which can be used as, calls API (Application Programming Interface, application program volume
Journey interface) service traffics unified entrance, i.e. gateway system can provide multiple API, for application program
(Application, APP) is called.
Referring to FIG. 2, Fig. 2 is a kind of flow chart of API Calls method shown in one exemplary embodiment of the application.The party
Method can be applied to gateway system shown in FIG. 1, include the following steps:
Step 201: receiving the call request for target API from application program.
Step 202: calling the target API, to be based on the corresponding destination service of the target API, the calling is asked
Parameter in asking is handled.
Step 203: parameter processing result is returned into the application program.
In the present embodiment, different since gateway system can be used as the unified entrance of the service traffics of calling API
Electronic equipment on the application program that runs the calling of API can be also completed based on the IP address of gateway system.
Specifically, when needing to call some API (referred to as target API), can construct purpose IP address is application program
The call request is sent to gateway system by the call request of the IP address of gateway system;Wherein, which can use
In invocation target API.
In practical applications, in addition to may include the ginseng for needing to be handled by invocation target API in the call request
Except number, the interface identifier (such as: interface name) of target API can also be included.Gateway system after receiving the call request,
The interface identifier can be primarily based on and determine corresponding API, the application program which as sends the call request needs to call
Target API.
Subsequent, gateway system can be right to be based on the corresponding service (referred to as destination service) of target API with invocation target API
Parameter in the call request is handled;Wherein, destination service be by target API be supplied to called side be called it is pre-
The function of definition.In this case, the parameter in the call request is handled based on destination service, as by the calling
Parameter in request substitutes into predefined function and is calculated, and parameter processing result is also calculated result.
Gateway system complete based on destination service to the processing of the parameter in the call request after, can be by parameter processing
As a result the above-mentioned application program for sending the call request is returned to.The application program, can after receiving the parameter processing result
To carry out subsequent further processing based on the parameter processing result, which can also be showed user for
It checks, this is not particularly limited in this application.
In an alternative embodiment, gateway system can provide the user interface for Administration API, and user can lead to
It crosses the user interface and interface management is carried out to some API (referred to as target API), such as: target API is configured, issued, is repaired
Change, is online, the processing such as offline and sandbox test.
Gateway system detect for target API interface management instruction (such as: configuration-direct, publication instruction, modification
Instruction, upper line, lower line and sandbox test instruction etc.) when, it can be instructed based on the interface management to the target
API is performed corresponding processing.
For example, the user interface for the user management API that user can be provided by gateway system, certainly to target API
The parameter of body is configured, and after configuration is complete, clicks " confirmation " button in the user interface.Gateway system is detecting
When user is for the clicking operation for being somebody's turn to do " confirmation " button, the configuration-direct detected for target API can be considered as, and to target
The parameter of API is configured accordingly.
It in an alternative embodiment, can be right for including the distributed network gate system of multiple gateway examples
Service traffics for calling API carry out load balancing, i.e., carry out load balancing to the call request received.
Specifically, after receiving some call request, it can be primarily based on preset load-balancing algorithm, determination is used for
Handle the gateway example of the call request.
After the gateway example for handling the call request has been determined, which can be transmitted to gateway reality
Example.The gateway example can call corresponding API after receiving the call request, to be based on the corresponding service of the API to this
Parameter in call request is handled.
For example, referring to FIG. 3, Fig. 3 is a kind of signal of gateway system shown in one exemplary embodiment of the application
Figure.
As shown in figure 3, Nginx load balancing is arranged in the front end for each gateway example that can include in gateway system respectively
Device.In such a case, it is possible to first receive call request by Nginx load balancer, and determination is asked for handling the calling
The gateway example asked.It is subsequent, the call request can also be transmitted to determining gateway example by Nginx load balancer, it should
Gateway example can call corresponding API after receiving the call request, to be based on the corresponding service of the API to the calling
Parameter in request is handled.
In practical applications, it in each gateway example, can be handled based on thread pool corresponding with the gateway example
Call request, to improve cpu busy percentage.
It should be noted that Nginx load balancer can be deployed on the headend equipment of gateway system, can also dispose
On gateway system, the application to this with no restriction.
In an alternative embodiment, for the gateway system of unallocated gateway example, or it is real including multiple gateways
For each gateway example in the gateway system of example, when receiving call request, preset asynchronous non-obstruction can be based on
Algorithm, invocation target API are handled the parameter in the call request with being based on the corresponding destination service of target API.
For example, a thread pool, the thread can be set in each gateway example that gateway system includes respectively
Pond can be used for handling the call request received by the gateway example.In the per thread of the thread pool, it can be based on adopting
Call request is handled with the AsynHttpClient of asynchronous non-block techniques, to improve cpu busy percentage.
In an alternative embodiment, it for including the distributed network gate system of multiple gateway examples, usually needs
Guarantee the configuration information of each gateway example be it is synchronous, i.e., the configuration information of each gateway example needs are consistent, with
Avoid mistake occur when carrying out API Calls.
Gateway system can provide the user interface of the configuration information for modifying gateway example, and user can pass through the use
It modifies to the configuration information of some gateway example (referred to as intended gateway example) at family interface.Alternatively, intended gateway example
Certain configuration informations may also voluntarily change in the process of running.
When the configuration for detecting intended gateway example is modified, configuration can be sent to other each gateway examples respectively
Request message.Other each gateway examples can be based on the configuring request message, execute when receiving the configuring request message
The configuration information of configuration modification identical with intended gateway example, each gateway example that gateway system can be made to include in this way is protected
It holds consistent.
For example, referring to FIG. 4, Fig. 4 is showing for another gateway system shown in one exemplary embodiment of the application
It is intended to.
As shown in figure 4, ZooKeeper client can be set in each gateway example that gateway system includes respectively,
And the ZooKeeper management end for managing this multiple ZooKeeper client is set.Each ZooKeeper client can be with
According to the preset time interval, heartbeat packet periodically is sent to ZooKeeper management end, to keep itself and ZooKeeper management end
Between connection.When the configuration of intended gateway example is modified, ZooKeeper management end can be by intended gateway example
ZooKeeper client listen to the configuration of intended gateway example and modified, and other each ZooKeeper clients then may be used
To listen to corresponding synchronous configuring request by ZooKeeper management end.Other each gateway examples are passing through it
When ZooKeeper client listens to the synchronization configuring request, it can be based on the synchronization configuring request, executed real with intended gateway
The identical configuration modification of example.
In practical applications, for each gateway example, configuration information and example information be may be stored in
In ZooKeeper management end and distributed caching, i.e., each gateway example is stateless example, in this way can be according to practical need
Seek any number of gateway example of extension.
It should be noted that ZooKeeper management end can be deployed on the headend equipment of gateway system, can also dispose
On gateway system, the application to this with no restriction.
In an alternative embodiment, API Calls can be realized using three-level caching mechanism, to improve gate performance.
Specifically, referring to FIG. 5, Fig. 5 is the signal of another gateway system shown in one exemplary embodiment of the application
Figure.
As shown in figure 5, some gateway example can be determined first after receiving the call request for invocation target API
Whether target API corresponding destination service is stored in the caching of the gateway example.
It, can be directly in the gateway if being stored with the corresponding destination service of target API in the caching of the gateway example
Invocation target API in the caching of example carries out the parameter in the call request with being based on the corresponding destination service of target API
Processing.
It, can further really if not stored in the caching of the gateway example have the corresponding destination service of target API
Determine whether to be stored with the corresponding destination service of target API in the caching of gateway system.
It, can be in the slow of gateway system if being stored with the corresponding destination service of target API in the caching of gateway system
Middle invocation target API is deposited, to be based on the corresponding destination service of target API, the parameter in the call request is handled.
If not stored in the caching of gateway system have the corresponding destination service of target API, can adjust in the database
The parameter in the call request is handled with being based on target API corresponding destination service with target API.
It should be noted that the time of data is read in the caching of gateway example, less than in the caching of gateway system
Read the time of identical data;And the time of data is read in the caching of gateway system, again smaller than reading phase in the database
With the time of data.Database can be deployed on the headend equipment of gateway system, can also be deployed on gateway system, this Shen
Please with no restriction to this.
In an alternative embodiment, the log information that gateway system generates in the process of running can be counted
And analysis, statistical result is showed into user, and alarm based on the warning message that analysis obtains.
For example, referring to FIG. 6, Fig. 6 is showing for another gateway system shown in one exemplary embodiment of the application
It is intended to.
As shown in fig. 6, a log concentrator can be set in each gateway example that gateway system includes respectively, with
The log information that the gateway example generates in the process of running is pushed in Kafka storage system by the log concentrator.This
Outside, the API Calls log of MongoDB database purchase can also be used.
The Storm real time computation system available log information stored into Kafka storage system, and to getting
Log information carries out real-time statistics and analysis.It is subsequent, statistical result can be sent to monitoring system and be shown, for
Family is checked;On the other hand, it the warning messages such as obtained operation exception will can be analyzed in real time is sent to alarm system and alarm.
In addition, monitoring system can also obtain the API Calls information stored in MongoDB database, so as to count each API's
The relevant informations such as call number, and obtained relevant information is shown, so that user checks.
It should be noted that Kafka storage system, Storm real time computation system, monitoring system, alarm system or
MongoDB database can be deployed on the headend equipment of gateway system, can also be deployed on gateway system, the application is to this
With no restriction.
In an alternative embodiment, gateway system can be based on preset secure authentication algorithm, to the use received
Secure authentication is carried out in the call request of invocation target API.
It, can be with invocation target API, to be based on the corresponding target of target API if the call request secure authentication passes through
Service, handles the parameter in the call request.
For example, standard OAuth2.0 agreement, the call request for invocation target API to receiving can be based on
Carry out secure authentication;Alternatively, can be based on digital signature technology, to the call request for invocation target API received into
Row secure authentication.
It in practical applications, can also be respectively each API setting blacklist or white list.Specifically, if it is some
API is provided with blacklist, then the subsequent call request that the blacklist can not be hit to IP address is handled;Correspondingly, such as
Fruit is that some API is provided with white list, then the subsequent call request that only can hit the white list to IP address is handled.
Analyze above-mentioned technical proposal it is found that by as calling API service traffics unified entrance gateway system, can
To be managed collectively to API, and the address by gateway system is only needed, different API can be called, realizes different services
Access simplifies API Calls operation, convenient for carrying out maintenance and management to different services.
Corresponding with the embodiment of aforementioned API Calls method, present invention also provides the embodiments of API Calls device.
The embodiment of the application API Calls device can be applied on gateway system.Installation practice can pass through software
It realizes, can also be realized by way of hardware or software and hardware combining.Taking software implementation as an example, as on a logical meaning
Device, be to be read computer program instructions corresponding in nonvolatile memory by the processor of gateway system where it
Into memory, operation is formed.For hardware view, as shown in fig. 7, Fig. 7 is gateway system where the application API Calls device
A kind of hardware structure diagram of system, other than processor shown in Fig. 7, memory, network interface and nonvolatile memory,
Gateway system in embodiment where device can also include other hardware, to this generally according to the actual functional capability of the API Calls
It repeats no more.
Referring to FIG. 8, Fig. 8 is a kind of block diagram of API Calls device shown in one exemplary embodiment of the application.The device
80 can be applied to gateway system shown in Fig. 7, comprising:
Receiving unit 801, for receiving the call request for target API from application program;
Call unit 802, for calling the target API, to be based on the corresponding destination service of the target API, to institute
The parameter stated in call request is handled;
Return unit 803, for parameter processing result to be returned to the application program.
In an alternative embodiment, described device 80 can also include:
Administrative unit 804, for being based on the interface when detecting the interface management instruction for the target API
Management instruction carries out respective handling to the target API.
In an alternative embodiment, the gateway system is the distributed system for including multiple gateway examples;
The call unit 802 specifically can be used for:
Based on preset load-balancing algorithm, the gateway example for handling the call request is determined, by the net
It closes example and calls the target API, to be based on the corresponding destination service of the target API, to the parameter in the call request
It is handled.
In an alternative embodiment, described device 80 can also include:
Synchronization unit 805, when for being modified in the configuration for detecting intended gateway example, respectively to other each gateways
Example sends synchronous configuring request, so that the gateway example and the intended gateway example execute identical configuration modification.
In an alternative embodiment, the call unit 802 specifically can be used for:
Determine the corresponding destination service of the target API whether is stored in the caching of the gateway example;
If being stored with the destination service in the caching of the gateway example, adjusted in the caching of the gateway example
The parameter in the call request is handled with being based on the destination service with the target API;
If not stored in the caching of the gateway example have the destination service, it is determined that the caching of the gateway system
In whether be stored with the destination service;
If being stored with the destination service in the caching of the gateway system, adjusted in the caching of the gateway system
The parameter in the call request is handled with being based on the destination service with the target API;
If not stored in the caching of the gateway system have the destination service, the target is called in the database
API is handled the parameter in the call request with being based on the destination service.
In an alternative embodiment, the call unit 802 specifically can be used for:
Based on preset asynchronous non-blocking algorithm, the target API is called, to be based on the corresponding target of the target API
Service, handles the parameter in the call request.
In an alternative embodiment, described device 80 can also include:
Computing unit 806, for based on log information progress statistics and analysis, statistical result to be showed user, and
The warning message obtained based on analysis is alarmed.
In an alternative embodiment, described device 80 can also include:
Authenticating unit 807 carries out secure authentication to the call request for being based on preset secure authentication algorithm;
The call unit 802 specifically can be used for:
If the call request secure authentication passes through, the target API is called, with corresponding based on the target API
Destination service, the parameter in the call request is handled.
The function of each unit and the realization process of effect are specifically detailed in the above method and correspond to step in above-mentioned apparatus
Realization process, details are not described herein.
For device embodiment, since it corresponds essentially to embodiment of the method, so related place is referring to method reality
Apply the part explanation of example.The apparatus embodiments described above are merely exemplary, wherein described be used as separation unit
The unit of explanation may or may not be physically separated, and component shown as a unit can be or can also be with
It is not physical unit, it can it is in one place, or may be distributed over multiple network units.It can be according to actual
The purpose for needing to select some or all of the modules therein to realize application scheme.Those of ordinary skill in the art are not paying
Out in the case where creative work, it can understand and implement.
The foregoing is merely the preferred embodiments of the application, not to limit the application, all essences in the application
Within mind and principle, any modification, equivalent substitution, improvement and etc. done be should be included within the scope of the application protection.
Claims (10)
1. a kind of API Calls method, which is characterized in that the method is applied to gateway system, and the gateway system provides multiple
Application programming interface API, comprising:
Receive the call request for target API from application program;
Call the target API, be based on the corresponding destination service of the target API, to the parameter in the call request into
Row processing;
Parameter processing result is returned into the application program.
2. the method according to claim 1, wherein the method also includes:
When detecting the interface management instruction for the target API, instructed based on the interface management to the target API
Carry out respective handling.
3. the method according to claim 1, wherein the gateway system is the distribution for including multiple gateway examples
Formula system;
It is described to call the target API, to be based on the corresponding destination service of the target API, to the ginseng in the call request
Number is handled, comprising:
Based on preset load-balancing algorithm, the gateway example for handling the call request is determined, with real by the gateway
Example calls the target API, to be based on the corresponding destination service of the target API, carries out to the parameter in the call request
Processing.
4. according to the method described in claim 3, it is characterized in that, the method also includes:
When the configuration for detecting intended gateway example is modified, synchronous configuration is sent to other each gateway examples respectively and is asked
It asks, so that the gateway example and the intended gateway example execute identical configuration modification.
5. according to the method described in claim 3, it is characterized in that, described call the target API, to be based on the target
The corresponding destination service of API, handles the parameter in the call request, comprising:
Determine the corresponding destination service of the target API whether is stored in the caching of the gateway example;
If being stored with the destination service in the caching of the gateway example, institute is called in the caching of the gateway example
Target API is stated, to be based on the destination service, the parameter in the call request is handled;
If not stored in the caching of the gateway example have the destination service, it is determined that be in the caching of the gateway system
It is no to be stored with the destination service;
If being stored with the destination service in the caching of the gateway system, institute is called in the caching of the gateway system
Target API is stated, to be based on the destination service, the parameter in the call request is handled;
If not stored in the caching of the gateway system have the destination service, the target API is called in the database,
To be based on the destination service, the parameter in the call request is handled.
6. the method according to claim 1, wherein described call the target API, to be based on the target
The corresponding destination service of API, handles the parameter in the call request, comprising:
Based on preset asynchronous non-blocking algorithm, the target API is called, to be based on the corresponding destination service of the target API,
Parameter in the call request is handled.
7. the method according to claim 1, wherein the method also includes:
Statistics and analysis is carried out based on log information, statistical result is showed into user, and the alarm signal obtained based on analysis
Breath is alarmed.
8. the method according to claim 1, wherein the method also includes:
Based on preset secure authentication algorithm, secure authentication is carried out to the call request;
It is described to call the target API, to be based on the corresponding destination service of the target API, to the ginseng in the call request
Number is handled, comprising:
If the call request secure authentication passes through, the target API is called, to be based on the corresponding mesh of the target API
Mark service, handles the parameter in the call request.
9. a kind of API Calls device, which is characterized in that described device is applied to gateway system, and the gateway system provides multiple
Application programming interface API, comprising:
Receiving unit, for receiving the call request for target API from application program;
Call unit, to be based on the corresponding destination service of the target API, asks the calling for calling the target API
Parameter in asking is handled;
Return unit, for parameter processing result to be returned to the application program.
10. device according to claim 9, which is characterized in that described device further include:
Administrative unit, for being instructed based on the interface management when detecting the interface management instruction for the target API
Respective handling is carried out to the target API.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910320362.1A CN110113394A (en) | 2019-04-19 | 2019-04-19 | API Calls method and apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910320362.1A CN110113394A (en) | 2019-04-19 | 2019-04-19 | API Calls method and apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
CN110113394A true CN110113394A (en) | 2019-08-09 |
Family
ID=67485986
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201910320362.1A Pending CN110113394A (en) | 2019-04-19 | 2019-04-19 | API Calls method and apparatus |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN110113394A (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111026574A (en) * | 2019-11-25 | 2020-04-17 | 中盈优创资讯科技有限公司 | Method and device for diagnosing Elasticissearch cluster problems |
CN112491696A (en) * | 2020-11-30 | 2021-03-12 | 上海昌投网络科技有限公司 | Message center system based on message pushing |
CN112953731A (en) * | 2021-02-26 | 2021-06-11 | 浪潮云信息技术股份公司 | API advanced flow control and metering method based on API gateway |
CN113014587A (en) * | 2021-03-05 | 2021-06-22 | 南京领行科技股份有限公司 | API detection method and device, electronic equipment and storage medium |
CN113326409A (en) * | 2020-02-29 | 2021-08-31 | 华为技术有限公司 | Table display method, equipment and system |
CN114006754A (en) * | 2021-10-29 | 2022-02-01 | 重庆长安汽车股份有限公司 | Method for protecting API (application programming interface) interface configuration security policy data and method and system for calling open platform service based on gateway |
CN114826612A (en) * | 2022-04-20 | 2022-07-29 | 微位(深圳)网络科技有限公司 | Data interaction method, device, equipment and storage medium |
CN117221374A (en) * | 2023-09-11 | 2023-12-12 | 广州Tcl互联网小额贷款有限公司 | API (application program interface) calling method and system based on API gateway |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106686021A (en) * | 2015-11-05 | 2017-05-17 | 北京京东尚科信息技术有限公司 | Service invoking method and gateway |
CN108512748A (en) * | 2018-03-21 | 2018-09-07 | 上海艾融软件股份有限公司 | A kind of implementation method of micro services gateway |
CN108712329A (en) * | 2018-05-02 | 2018-10-26 | 山东汇贸电子口岸有限公司 | A kind of gateway and log recording retrieval device based on Elasticsearch |
CN108965007A (en) * | 2018-07-19 | 2018-12-07 | 北京车和家信息技术有限公司 | API gateway interface configures update method and device |
CN109151091A (en) * | 2018-09-21 | 2019-01-04 | 福建南威软件有限公司 | A kind of API gateway service for supporting dubbo agreement to call |
CN109218426A (en) * | 2018-09-19 | 2019-01-15 | 福建南威软件有限公司 | A kind of API gateway method of servicing for supporting webservice agreement to call |
CN109460223A (en) * | 2018-11-14 | 2019-03-12 | 沈阳林科信息技术有限公司 | A kind of API gateway management system and its method |
WO2019052526A1 (en) * | 2017-09-14 | 2019-03-21 | 北京金山云网络技术有限公司 | Api invoking system, method and apparatus, electronic device and storage medium |
-
2019
- 2019-04-19 CN CN201910320362.1A patent/CN110113394A/en active Pending
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106686021A (en) * | 2015-11-05 | 2017-05-17 | 北京京东尚科信息技术有限公司 | Service invoking method and gateway |
WO2019052526A1 (en) * | 2017-09-14 | 2019-03-21 | 北京金山云网络技术有限公司 | Api invoking system, method and apparatus, electronic device and storage medium |
CN109510846A (en) * | 2017-09-14 | 2019-03-22 | 北京金山云网络技术有限公司 | API Calls system, method, apparatus, electronic equipment and storage medium |
CN108512748A (en) * | 2018-03-21 | 2018-09-07 | 上海艾融软件股份有限公司 | A kind of implementation method of micro services gateway |
CN108712329A (en) * | 2018-05-02 | 2018-10-26 | 山东汇贸电子口岸有限公司 | A kind of gateway and log recording retrieval device based on Elasticsearch |
CN108965007A (en) * | 2018-07-19 | 2018-12-07 | 北京车和家信息技术有限公司 | API gateway interface configures update method and device |
CN109218426A (en) * | 2018-09-19 | 2019-01-15 | 福建南威软件有限公司 | A kind of API gateway method of servicing for supporting webservice agreement to call |
CN109151091A (en) * | 2018-09-21 | 2019-01-04 | 福建南威软件有限公司 | A kind of API gateway service for supporting dubbo agreement to call |
CN109460223A (en) * | 2018-11-14 | 2019-03-12 | 沈阳林科信息技术有限公司 | A kind of API gateway management system and its method |
Non-Patent Citations (3)
Title |
---|
庄夏: "API 网关架构设计实例", 《信息系统工程》 * |
王喻等: "面向服务管控的API网关设计与实现", 《中国计算机用户协会网络应用分会2017年第二十一届网络新技术与应用年会论文集》 * |
高凯: "基于Netty的网页游戏网关服务器架构的设计与实现", 《中国优秀硕士学位论文全文数据库(电子期刊)信息科技辑》 * |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111026574A (en) * | 2019-11-25 | 2020-04-17 | 中盈优创资讯科技有限公司 | Method and device for diagnosing Elasticissearch cluster problems |
CN111026574B (en) * | 2019-11-25 | 2024-03-12 | 中盈优创资讯科技有限公司 | Method and device for diagnosing elastiscearch cluster problem |
CN113326409A (en) * | 2020-02-29 | 2021-08-31 | 华为技术有限公司 | Table display method, equipment and system |
CN112491696A (en) * | 2020-11-30 | 2021-03-12 | 上海昌投网络科技有限公司 | Message center system based on message pushing |
CN112953731A (en) * | 2021-02-26 | 2021-06-11 | 浪潮云信息技术股份公司 | API advanced flow control and metering method based on API gateway |
CN113014587A (en) * | 2021-03-05 | 2021-06-22 | 南京领行科技股份有限公司 | API detection method and device, electronic equipment and storage medium |
CN114006754A (en) * | 2021-10-29 | 2022-02-01 | 重庆长安汽车股份有限公司 | Method for protecting API (application programming interface) interface configuration security policy data and method and system for calling open platform service based on gateway |
CN114826612A (en) * | 2022-04-20 | 2022-07-29 | 微位(深圳)网络科技有限公司 | Data interaction method, device, equipment and storage medium |
CN114826612B (en) * | 2022-04-20 | 2024-01-30 | 微位(深圳)网络科技有限公司 | Data interaction method, device, equipment and storage medium |
CN117221374A (en) * | 2023-09-11 | 2023-12-12 | 广州Tcl互联网小额贷款有限公司 | API (application program interface) calling method and system based on API gateway |
CN117221374B (en) * | 2023-09-11 | 2024-05-24 | 广州Tcl互联网小额贷款有限公司 | API (application program interface) calling method and system based on API gateway |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110113394A (en) | API Calls method and apparatus | |
US10904277B1 (en) | Threat intelligence system measuring network threat levels | |
US10693734B2 (en) | Traffic pattern detection and presentation in container-based cloud computing architecture | |
US8261346B2 (en) | Detecting attacks on a data communication network | |
US8806550B1 (en) | Rules engine for troubleshooting video content delivery network | |
CN102484653B (en) | Measuring attributes of client-server applications | |
US8670448B2 (en) | Methods, systems, and computer program products for providing traffic control services | |
US9558043B2 (en) | System and method for abstracting and orchestrating mobile data networks in a network environment | |
KR20180095798A (en) | Systems and methods for security and risk assessment and testing of applications | |
CN104169937B (en) | Chance system scans | |
US11924058B2 (en) | Extensible analytics and recommendation engine for network traffic data | |
CN108259554A (en) | Dynamic allocation of the network entity among monitoring agent | |
US20110191223A1 (en) | Internet Control Management and Accounting in a Utility Computing Environment | |
CN109787827B (en) | CDN network monitoring method and device | |
CN110943884B (en) | Data processing method and device | |
US20120311611A1 (en) | Extendable event processing through services | |
JP6220625B2 (en) | Delay monitoring system and delay monitoring method | |
CN112737800B (en) | Service node fault positioning method, call chain generating method and server | |
US20150012647A1 (en) | Router-based end-user performance monitoring | |
CN107959696A (en) | A kind of daily record bill processing method and system | |
US10445136B1 (en) | Randomized subrequest selection using request-specific nonce | |
US11516138B2 (en) | Determining network flow direction | |
US9900230B2 (en) | Dissemination of quality of service information in a distributed environment | |
CN109495319A (en) | The fault message of CDN node determines method, device and equipment | |
US20070136575A1 (en) | Method and data processing system for determining user specific usage of a network |
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: 20190809 |