CN107659460A - A kind of method of provisioning API visit capacity - Google Patents
A kind of method of provisioning API visit capacity Download PDFInfo
- Publication number
- CN107659460A CN107659460A CN201711108422.0A CN201711108422A CN107659460A CN 107659460 A CN107659460 A CN 107659460A CN 201711108422 A CN201711108422 A CN 201711108422A CN 107659460 A CN107659460 A CN 107659460A
- Authority
- CN
- China
- Prior art keywords
- api
- visit capacity
- theoretical
- weights
- next time
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a kind of method of provisioning API visit capacity, its method includes：Based on each application interface API resource request messages that terminal corresponding to reception is sent in the range of preset duration；Judge whether weights shared by each application programming interfaces API are more than each API history visit capacity weights, if weights shared by each application programming interfaces API are less than or equal to each API history visit capacity weights, then use services configuration protocol provisioning API visit capacity, if weights shared by each application programming interfaces API are less than or equal to each API history visit capacity weights, into dynamic configuration API Access amount process.By the embodiment of the present invention, API gateway can be realized using various ways for the calling of different application, ensure to realize different types of terminals different weight computings, ensure the load balancing in whole system.
Description
Technical field
The present invention relates to areas of information technology, and in particular to a kind of method of provisioning API visit capacity.
Background technology
Conventional application programming interface (Application Programming Interface, the API) peace of industrial quarters
Be with management platform entirely it is a set of operate in data center, the application software of cloud service center, for the API producer, API consume
The roles such as person, API managers, there is provided API gateway, API doors, API life cycle managements, API monitoring, API key managements
And the assembly function such as API practicality situation analysis, Fig. 1 show the structural representation of API safety and management platform.API safety with
The system environments of management platform operation includes：Meet J2EE specifications middleware (such as：Tomcat, Weblogic etc.),
Oracle or Mysql databases.It is different that application programming interfaces API is directly invoked from traditional application program, and information centre needs
API safety and management software are first enabled, application program can pass through one before the application programming interfaces (API) in resource are called
Individual API gateway, the gateway can realize safe access control and the dynamic call to API, i.e. API nets according to certain scheduling strategy
Module is closed to be responsible for carrying out whole API resources route agent, performance distribution.
As shown in Fig. 2 API gateway is operated between application program and server A PI resources as intermediate node, play
API scheduling of resource and the important function of control.For example assume 1 API background system, 100 concurrent requests of maximum support per second,
More than this numerical value, system will collapse, therefore request be limited.If there are 20 consumers to subscribe at present, average 1 second please
1 is asked, peak value request 10 per second, then the request each subscribed to will be limited below 10.Industry generally uses at present
A kind of " air throttle " technology, by service-level agreement (Service-Level Agreement, SLA), every layer of service association is set
The maximum available request number of view.For example, maximum 5000 requests, secondary service are maximum 50 per hour per hour for one-level service
Request.Such as set some API maximum can call number be 50, each Connection Time is 60000 milliseconds.Therefore work as and apply
When the routine call API is more than 50 times, do not allow for recalling, this application journey to some specific transactions frequent operations
It is inappropriate for sequence.
At present in the method and gateway and system of a kind of apllied dynamic configuration API Access amount of our company, make API gateway
Dynamic configuration API realizes possibility, is defined by the dynamic access time, and the resource required in its whole dynamic process is different
, corresponding weight computing how is realized in preset time, matching more suitably API Access amount requires further study,
And before dynamic configuration API processes are related to, corresponding threshold can be set, and need not all go dynamic configuration in real time
API processes, during this dynamic configuration API, the computing resource of shared system or otherwise power consumption are all compared
Greatly, it is unfavorable for the scheduling of real-time API processes.
The content of the invention
Technical scheme can not realize the technical disadvantages of dynamic Static Configuration Files primarily directed to API, using elder generation
Obtain each resource end data according to time length, then realize weight computing, so as to judge to enter dynamic configuration or
Static configuration procedure, API user is set rationally to utilize server resource.
The invention provides a kind of method of provisioning API visit capacity, methods described includes：
Based on each application interface API resource request messages that terminal corresponding to reception is sent in the range of preset duration；
The API of terminal please according to corresponding to preset duration scope generation for each application interface in each application interface
Seek bag；
API request bag based on corresponding terminal calculates API request bag the accounting on corresponding application interface
Use weights；
Weights shared by each application programming interfaces API are counted, and according to going through in the range of preset duration on last stage
History visit capacity calculates each API history visit capacity weights in the API set；
Judge whether weights shared by each application programming interfaces API are more than each API history visit capacity weights, if
Weights shared by each application programming interfaces API are less than or equal to each API history visit capacity weights, then using services
Configuration protocol provisioning API visit capacity, if weights shared by each application programming interfaces API are less than or equal to each API history
Visit capacity weights, then into dynamic configuration API Access amount process.
It is described to include into dynamic configuration API Access amount process：
Theoretical visit capacity after correcting is calculated according to the actual access amount of history visit capacity and resource；
Theoretical visit capacity judges the size of theoretical visit capacity and last theoretical visit capacity next time after being corrected based on calculating
Relation；
If it is determined that theoretical visit capacity is more than or equal to last theoretical visit capacity next time, then by last theoretical visit capacity
It is configured to API Access amount；If it is determined that theoretical visit capacity is less than last theoretical visit capacity next time, then next time theoretical will visit
Component after the amount of asking reconfigures constraint set conjunction and calculated.
It is described that theoretical visit capacity next time and last theoretical visit capacity are judged based on theoretical visit capacity after calculating amendment
Also include before magnitude relationship：
Judge amendment after resource service condition whether within load, if resource service condition within load, base
Theoretical visit capacity judges the magnitude relationship of theoretical visit capacity and last theoretical visit capacity next time after amendment is calculated；
If resource service condition, beyond load, computational load introduces parameter so that theoretical visit capacity exists after amendment
In loading range, then theoretical visit capacity judges theoretical visit capacity and upper one next time after being introduced parameter based on load and calculated amendment
The magnitude relationship of secondary theoretical visit capacity.
It is described if it is determined that theoretical visit capacity is less than last theoretical visit capacity next time, then will theoretical visit capacity next time
Component afterwards, which is reconfigured during constraint set conjunction is calculated, also to be included：
When next time, theoretical visit capacity is less than last theoretical visit capacity, then by the component after theoretical visit capacity next time
A constraint set is re-configured to, weights and API history visit capacity weight computings shared by progress API, is finally completed API visits
The configuration for the amount of asking.
Methods described also includes：
When the access request amount increased newly in some period is more than the threshold parameter that client is pre-configured with, triggering carries out API
Shared weights and API history visit capacity weight computing, is finally completed the configuration of API Access amount.
The API of terminal please according to corresponding to preset duration scope generation for each application interface in each application interface
Bag is asked to include：
In the range of the preset duration, each application interface terminal hair corresponding to statistics in the range of preset duration
The API resource request message quantity sent；
When preset duration scope reaches, by corresponding terminal type, API resource request messages, resource request message number
Amount and duration value are encapsulated in API request bag with data structure.
The API request bag based on corresponding terminal calculates the API request bag on corresponding application interface
Occupancy weights include：
Obtain the target type corresponding to API request bag；
Occupancy weights of the API request bag on corresponding application interface are calculated based on target type.
It is described that occupancy weights bag of the API request bag on corresponding application interface is calculated based on target type
Include：
Corresponding occupancy weight coefficient is matched based on the target type；
Right to occupation of the API request bag on corresponding application interface is calculated based on the occupancy weight coefficient
Value.
Technical solution of the present invention of the embodiment of the present invention is primarily based on each application interface and API resources is realized in preset time
Collection, an API request bag then is formed to API resources, service end can be directed to API request after request bag is received
Bag calculates the occupancy weights on each application interface shared by terminal, forms the Pre-Evaluation corresponded on interface before resource access
Or calculating process, so that compared with the weights on the corresponding period, then judge whether to need progress static configuration still to move
State configures.In the process, will not the inflexible calculating unremitting only for dynamic configuration go down, can also be directed to and history
The comparison of data, static configuration procedure is realized, improve resource efficiency.The no parameter limitation of calling to API, can be with application
The changes in demand and aggregate resource service condition of program and change.API gateway can adopt for the calling of different application
Realized with various ways, ensure to realize different types of terminals different weight computings, ensure the load balancing in whole system.
Brief description of the drawings
In order to illustrate more clearly about the embodiment of the present invention or technical scheme of the prior art, below will be to embodiment or existing
There is the required accompanying drawing used in technology description to be briefly described, it should be apparent that, drawings in the following description are only this
Some embodiments of invention, for those of ordinary skill in the art, on the premise of not paying creative work, can be with
Other accompanying drawings are obtained according to these accompanying drawings.
Fig. 1 is API safety of the prior art and management platform structural representation；
Fig. 2 is the system structure diagram of the prior art based on SAL provisioning API visit capacities；
Fig. 3 is the system structure diagram of the provisioning API visit capacity in the embodiment of the present invention；
Fig. 4 is the method flow diagram of the provisioning API visit capacity in the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is carried out clear, complete
Site preparation describes, it is clear that described embodiment is only part of the embodiment of the present invention, rather than whole embodiments.It is based on
Embodiment in the present invention, those of ordinary skill in the art are obtained all other under the premise of creative work is not made
Embodiment, belong to the scope of protection of the invention.
The system of dynamic configuration API Access amount as shown in Figure 3, including API gateway, multiple application terminals, multiple services
Device etc., API gateway are connected to multiple application terminals and multiple servers, wherein：It is whole with application that API gateway manages multiple servers
Service between end, there are multiple api interfaces to be communicated with corresponding application terminal on API gateway, these application terminals are general
For mobile terminal, multiple API are stored on each server in multiple servers, as API gateway according to transmitted by application terminal
API resource request messages complete the calling of corresponding API application programs.Gateway is provided with multiple api interfaces, is answered with multiple
Connected with terminal, for receiving the calling of API application programs, the plurality of api interface is received based on each application interface when default
The API resource request messages that corresponding terminal is sent in long scope, each application interface is according to described default in each application interface
The API request bag of terminal corresponding to the generation of duration scope；Multiple API servers, for storing API resources；Have on API gateway
Multiple api interfaces can be connected to multiple api interfaces, and be connected to multiple API servers, can be used for receiving API
After request bag, the API request bag based on corresponding terminal calculates API request bag the accounting on corresponding application interface
Use weights；Weights shared by each application programming interfaces API are counted, and according to the history in the range of preset duration on last stage
Visit capacity calculates each API history visit capacity weights in the API set；Judge that each application programming interfaces API is shared to weigh
Whether value is more than each API history visit capacity weights, if weights are less than or equal to institute shared by each application programming interfaces API
Each API history visit capacity weights are stated, then using services configuration protocol provisioning API visit capacity, if each application program connects
Weights shared by mouth API are less than or equal to each API history visit capacity weights, then into dynamic configuration API Access amount process.
Application program calls the API being deployed on different server by API gateway, and application program is mounted in accordingly
On application terminal, and application terminal is based on corresponding interface and sends corresponding API resource requests to API gateway.The skill of the present invention
Art scheme be API gateway management on, using the combination of Dynamic Programming optimization strategy and services configuration protocol file come
Realize.Resource workable for each server is recorded in API gateway, server maximum load capability, the API on server,
Server resource amount needed for each API history calling frequency, operation API etc., these data participate in Dynamic Programming optimization
The calculating of method, and obtain API on each server it is optimal can call number, so as to realize the dynamic control to API Calls,
Set dynamic calculation to perform triggering threshold values simultaneously, carry out dynamic calculation, distribution automatically when access request reaches threshold values；API nets
Close all types of of the same application terminal that can be identified api interface and be connected, and each API request bag based on collection come
Identification judges resource size ability shared by application terminal, in the case of a upper period resource distribution, Ke Yixuan
Dynamic Configuration Process realization is selected, and no more than in the case of a upper period resource distribution, services configuration can be used to assist
File is discussed to realize.
Accordingly, Fig. 4 shows the method flow diagram of the provisioning API visit capacity in the embodiment of the present invention, specifically include as
Lower step：
S101, based on each application interface, the API resource requests of terminal transmission disappear corresponding to reception in the range of preset duration
Breath；
It should be noted that the API resource request messages that application terminal is sent are received in the range of api interface preset duration,
Handled in units of millisecond, for example 50ms or 10ms etc. is that a unit is received, foot for this response time
Enough tackle the time demand of each application terminal.API request message transmitted by each application terminal is received based on application interface, so as to
The action found out in advance is realized, and existing dynamic configuration API is simply considered gateway and matched somebody with somebody based on the dynamic that API Access amount is realized
Process is put, and have ignored based on response time and terminal type i.e. target type to make corresponding weights anticipation process.
The API of each application interface terminal according to corresponding to preset duration scope generation in S102, each application interface
Request bag；
It should be noted that in the range of the preset duration, each application interface in each application interface is when default
The API resource request message quantity that terminal corresponding to statistics is sent in long scope；When preset duration scope reaches, by corresponding to
Terminal type, API resource request messages, resource request message quantity and duration value are encapsulated in API request bag with data structure.This
A little data form an API request bag can be subject to dissection process in API gateway.
S103, the API request bag based on corresponding terminal calculate the API request bag on corresponding application interface
Occupancy weights；
In specific implementation process, the target type corresponding to API request bag can be obtained；Institute is calculated based on target type
State occupancy weights of the API request bag on corresponding application interface.Different target type occupies resource weights difference, and root
After being calculated according to weights shared by different target type, you can provisioning API resource requirement required for drawing whole API gateway.
In specific implementation process, the API request bag should be calculated on corresponding application interface based on target type
Occupancy weights include：Corresponding occupancy weight coefficient is matched based on the target type；Based on the occupancy weight coefficient meter
Calculate occupancy weights of the API request bag on corresponding application interface.
For example target type is tablet personal computer or mobile terminal, the API request of api interface corresponding to it from acquisition
Bag, its shared type or resource matched coefficient are all different, its occupancy weight coefficients according to corresponding to each, or
Coefficient ratio possessed by different terminals type is also different, then different according to coefficient ratio possessed by each terminal type, you can
Realize the occupancy weight computing on business interface.
S104, count weights shared by each application programming interfaces API, and according on last stage in the range of preset duration
History visit capacity calculate each API history visit capacity weights in the API set, if it exceeds then entering S107, if do not surpassed
Cross and then enter S105；
For weights situation shared by each application programming interfaces API, and according on last stage in the range of preset duration
History visit capacity calculate each API history visit capacity weights in API set, history visit capacity weights here can form one
The weights of resource shared by history visit capacity, weights shared by the API on each api interface is judged are no more than corresponding
API history visit capacity weights, illustrate that this takes weights and is allowed, i.e., the API on this application interface need not additionally match somebody with somebody
Put resource；If API here, which takes weights, exceedes corresponding API history visit capacity weights, i.e. API on this application interface
Need additionally to configure resource.
Here the history visit capacity on last stage in the range of preset duration calculates each API history in the API set and visited
The amount of asking weights can be the history visit capacity of initial value facilities or a upper duration.By this set, with
When the visit capacity of a upper duration is compared, it can know that this data can or can not meet previously according to weights are taken, if
Take weights caused by visit capacity it is excessive, then need carry out dynamic configuration, if take weights caused by visit capacity not less than
History visit capacity, then carry out static configuration.
S105, judge whether weights shared by each application programming interfaces API are more than each API history visit capacity power
Value, as to be more than be present, then need to enter S107, if in the absence of more than situation if enter S106 steps；
If weights shared by S106, each application programming interfaces API are less than or equal to each API history visit capacity power
Value, then using services configuration protocol provisioning API visit capacity；
If weights shared by S107, each application programming interfaces API are less than or equal to each API history visit capacity power
Value, then into dynamic configuration API Access amount process.
In specific implementation process, include into dynamic configuration API Access amount process：According to history visit capacity and the reality of resource
Border visit capacity calculates theoretical visit capacity after amendment；Based on calculate correct after theoretical visit capacity judge next time theoretical visit capacity with it is upper
The once magnitude relationship of theoretical visit capacity；If it is determined that theoretical visit capacity is more than or equal to last theoretical visit capacity next time, then
Last theoretical visit capacity is configured to API Access amount；If it is determined that theoretical visit capacity is less than last theoretical access next time
Amount, then the component after theoretical visit capacity next time is reconfigured into constraint set conjunction and calculated.
In specific implementation process, judge that theoretical visit capacity is managed with last next time based on theoretical visit capacity after calculating amendment
Also include before by the magnitude relationship of visit capacity：Whether resource service condition is within load after judging amendment, if resource makes
With situation within load, then judge that theoretical visit capacity is visited with last theory next time based on theoretical visit capacity after calculating amendment
The magnitude relationship for the amount of asking；If resource service condition, beyond load, computational load introduces parameter so that theoretical after amendment to visit
The amount of asking is in loading range, then theoretical visit capacity judges theoretical visit capacity next time after being introduced parameter based on load and calculated amendment
With the magnitude relationship of last theoretical visit capacity.
In specific implementation process, if it is determined that theoretical visit capacity is less than last theoretical visit capacity next time, then will be next
Component after secondary theoretical visit capacity, which is reconfigured during constraint set conjunction is calculated, also to be included：When next time, theoretical visit capacity is less than
Last theoretical visit capacity, then the component after theoretical visit capacity next time is re-configured to a constraint set, carries out API
Shared weights and API history visit capacity weight computing, is finally completed the configuration of API Access amount.
During dynamic configuration API, when the access request amount increased newly in some period is more than the valve that client is pre-configured with
During value parameter, weights and API history visit capacity weight computings shared by triggering progress API, matching somebody with somebody for API Access amount is finally completed
Put.
It should be noted that the process of above dynamic configuration API resources, see 201410331882X patent correlations
Illustrate, no longer repeat one by one here.
To sum up, technical solution of the present invention is primarily based on the collection that each application interface realizes API resources in preset time,
Then an API request bag is formed to API resources, service end can calculate after request bag is received for API request bag
Occupancy weights on each application interface shared by terminal, form a Pre-Evaluation or the calculating corresponded on interface before resource access
Process, so that compared with the weights on the corresponding period, then judge whether to need to carry out static configuration or dynamic configuration.
During this, will not the inflexible calculating unremitting only for dynamic configuration go down, ratio with historical data can also be directed to
It is right, static configuration procedure is realized, improves resource efficiency.The no parameter limitation of calling to API, can be with the need of application program
Ask change and aggregate resource service condition and change.API can be real using various ways for the calling of different application
It is existing, ensure to realize different types of terminals different weight computings, ensure the load balancing in whole system.
One of ordinary skill in the art will appreciate that all or part of step in the various methods of above-described embodiment is can
To instruct the hardware of correlation to complete by program, the program can be stored in a computer-readable recording medium, storage
Medium can include：Read-only storage (ROM, Read Only Memory), random access memory (RAM, Random
Access Memory), disk or CD etc..
The method of the provisioning API visit capacity provided above the embodiment of the present invention is described in detail, and herein should
The principle and embodiment of the present invention are set forth with specific case, the explanation of above example is only intended to help and managed
Solve the method and its core concept of the present invention；Meanwhile for those of ordinary skill in the art, according to the thought of the present invention,
There will be changes in embodiment and application, in summary, this specification content should not be construed as to this hair
Bright limitation.
Claims (8)
- A kind of 1. method of provisioning API visit capacity, it is characterised in that methods described includes：Based on each application interface API resource request messages that terminal corresponding to reception is sent in the range of preset duration；The API request of each application interface terminal according to corresponding to preset duration scope generation in each application interface Bag；API request bag based on corresponding terminal calculates right to occupation of the API request bag on corresponding application interface Value；Weights shared by each application programming interfaces API are counted, and are visited according to the history in the range of preset duration on last stage Ask that gauge calculates each API history visit capacity weights in the API set；Judge whether weights shared by each application programming interfaces API are more than each API history visit capacity weights, if described Weights shared by each application programming interfaces API are less than or equal to each API history visit capacity weights, then are configured using services Protocol configuration API Access amount, if weights shared by each application programming interfaces API are less than or equal to each API history and accessed Weights are measured, then into dynamic configuration API Access amount process.
- 2. the method as described in claim 1, it is characterised in that described to include into dynamic configuration API Access amount process：Theoretical visit capacity after correcting is calculated according to the actual access amount of history visit capacity and resource；Theoretical visit capacity judges the magnitude relationship of theoretical visit capacity and last theoretical visit capacity next time after being corrected based on calculating；If it is determined that theoretical visit capacity is more than or equal to last theoretical visit capacity next time, then last theoretical visit capacity is configured For API Access amount；, then will theoretical visit capacity next time if it is determined that theoretical visit capacity is less than last theoretical visit capacity next time Component afterwards reconfigures constraint set conjunction and calculated.
- 3. method as claimed in claim 2, it is characterised in that described to be judged next time based on theoretical visit capacity after calculating amendment Theoretical visit capacity before the magnitude relationship of last theoretical visit capacity with also including：Whether resource service condition is within load after judging amendment, if resource service condition within load, is based on meter Calculate the magnitude relationship that theoretical visit capacity after correcting judges theoretical visit capacity and last theoretical visit capacity next time；If resource service condition, beyond load, computational load introduces parameter so that theoretical visit capacity is loading after amendment In the range of, then theoretical visit capacity judges that theoretical visit capacity is managed with last next time after being introduced parameter based on load and calculated amendment By the magnitude relationship of visit capacity.
- 4. method as claimed in claim 3, it is characterised in that described if it is determined that theoretical visit capacity is less than the last time next time Theoretical visit capacity, then reconfiguring the component after theoretical visit capacity next time during constraint set conjunction is calculated also includes：When next time, theoretical visit capacity is less than last theoretical visit capacity, then by the component after theoretical visit capacity next time again A constraint set is configured to, weights and API history visit capacity weight computings shared by progress API, is finally completed API Access amount Configuration.
- 5. the method as described in any one of claim 2 to 4, it is characterised in that methods described also includes：When the access request amount increased newly in some period is more than the threshold parameter that client is pre-configured with, triggering is carried out shared by API With weights and API history visit capacity weight computings, the configuration of API Access amount is finally completed.
- 6. the method as described in claim 1, it is characterised in that each application interface is according to described pre- in each application interface If the API request bag of terminal includes corresponding to the generation of duration scope：In the range of the preset duration, each application interface terminal corresponding to statistics in the range of preset duration is sent API resource request message quantity；When preset duration scope reaches, by corresponding terminal type, API resource request messages, resource request message quantity and Duration value is encapsulated in API request bag with data structure.
- 7. method as claimed in claim 6, it is characterised in that the API request bag based on corresponding terminal calculates institute Stating occupancy weights of the API request bag on corresponding application interface includes：Obtain the target type corresponding to API request bag；Occupancy weights of the API request bag on corresponding application interface are calculated based on target type.
- 8. method as claimed in claim 7, it is characterised in that described the API request bag is calculated based on target type to exist Occupancy weights on corresponding application interface include：Corresponding occupancy weight coefficient is matched based on the target type；Occupancy weights of the API request bag on corresponding application interface are calculated based on the occupancy weight coefficient.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711108422.0A CN107659460A (en) | 2017-11-09 | 2017-11-09 | A kind of method of provisioning API visit capacity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711108422.0A CN107659460A (en) | 2017-11-09 | 2017-11-09 | A kind of method of provisioning API visit capacity |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107659460A true CN107659460A (en) | 2018-02-02 |
Family
ID=61121340
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711108422.0A Pending CN107659460A (en) | 2017-11-09 | 2017-11-09 | A kind of method of provisioning API visit capacity |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107659460A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108388475A (en) * | 2018-02-27 | 2018-08-10 | 广州联智信息科技有限公司 | A kind of method and system based on terminal type provisioning API resource |
| CN109542678A (en) * | 2018-11-07 | 2019-03-29 | 郑州云海信息技术有限公司 | A kind of server key message timed backup method and device |
| WO2019178761A1 (en) * | 2018-03-21 | 2019-09-26 | 华为技术有限公司 | Control method for application programming interface (api) gateway cluster, and api gateway cluster |
| CN112350950A (en) * | 2020-10-28 | 2021-02-09 | 北京中电普华信息技术有限公司 | Request message control method and device |
-
2017
- 2017-11-09 CN CN201711108422.0A patent/CN107659460A/en active Pending
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108388475A (en) * | 2018-02-27 | 2018-08-10 | 广州联智信息科技有限公司 | A kind of method and system based on terminal type provisioning API resource |
| CN108388475B (en) * | 2018-02-27 | 2021-06-29 | 周翠敏 | Method and system for configuring API (application program interface) resources based on terminal type |
| WO2019178761A1 (en) * | 2018-03-21 | 2019-09-26 | 华为技术有限公司 | Control method for application programming interface (api) gateway cluster, and api gateway cluster |
| CN111386676A (en) * | 2018-03-21 | 2020-07-07 | 华为技术有限公司 | Control method of application programming interface API gateway cluster and API gateway cluster |
| EP3761560A4 (en) * | 2018-03-21 | 2021-03-03 | Huawei Technologies Co., Ltd. | Control method for application programming interface (api) gateway cluster, and api gateway cluster |
| CN111386676B (en) * | 2018-03-21 | 2022-01-21 | 华为技术有限公司 | Control method of application programming interface API gateway cluster and API gateway cluster |
| US11362952B2 (en) | 2018-03-21 | 2022-06-14 | Huawei Cloud Computing Technologies Co., Ltd. | Application programing interface API gateway cluster control method and API gateway cluster |
| US11743187B2 (en) | 2018-03-21 | 2023-08-29 | Huawei Cloud Computing Technolgoies Co., Ltd. | Application programing interface (API) gateway cluster control method and API gateway cluster |
| EP4250676A3 (en) * | 2018-03-21 | 2024-01-10 | Huawei Cloud Computing Technologies Co., Ltd. | Control method for application programming interface (api) gateway cluster, and api gateway cluster |
| CN109542678A (en) * | 2018-11-07 | 2019-03-29 | 郑州云海信息技术有限公司 | A kind of server key message timed backup method and device |
| CN109542678B (en) * | 2018-11-07 | 2021-12-17 | 郑州云海信息技术有限公司 | Method and device for regularly backing up key information of server |
| CN112350950A (en) * | 2020-10-28 | 2021-02-09 | 北京中电普华信息技术有限公司 | Request message control method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107659460A (en) | A kind of method of provisioning API visit capacity | |
| CN104168133B (en) | The method and gateway and system of a kind of dynamic configuration API Access amount | |
| EP2254286B1 (en) | Network real time monitoring and control method, system and computer program product | |
| CN109347947A (en) | A kind of method of load balancing, name server and cluster nas server | |
| CN1988548B (en) | Method and system for processing speech processing request | |
| CN109062658A (en) | Realize dispatching method, device, medium, equipment and the system of computing resource serviceization | |
| CN108134830A (en) | Load-balancing method, system, device and storage medium based on message queue | |
| CA2626535A1 (en) | System and method for managing use and access of a communication network | |
| CN107872402A (en) | The method, apparatus and electronic equipment of global traffic scheduling | |
| CN104995899B (en) | Server load management | |
| CN109962855A (en) | A kind of current-limiting method of WEB server, current-limiting apparatus and terminal device | |
| CN105933854A (en) | Method, system and device for realizing machine to machine service | |
| CN108366021A (en) | A kind of method and system of the concurrent web page access business of processing | |
| CN109831524A (en) | A kind of load balance process method and device | |
| Assunçao et al. | Context-aware job scheduling for cloud computing environments | |
| CN110247856A (en) | Server resource method for releasing and device | |
| CN108600034A (en) | Traffic pressure management method, device, equipment, system and storage medium | |
| CN101595680B (en) | Arrangement and method relating to performance management by distributed processing | |
| WO2024094104A1 (en) | Dynamic feedback weighted cloud storage resource scheduling method, apparatus and device | |
| CN109617750A (en) | A kind of service method for early warning and gateway | |
| CN106302211A (en) | The request amount control method of a kind of Internet resources and device | |
| CN101926124A (en) | Internet protocol service level agreement router disposes automatically | |
| CN110267351A (en) | Communication means and device | |
| CN109584105A (en) | A kind of method and system of service response | |
| CN107682316A (en) | The generation method and dynamic password sending method of dynamic password sending strategy |
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: 20180202 |