CN114338783A - API management platform based on technical middlebox and management method thereof - Google Patents
API management platform based on technical middlebox and management method thereof Download PDFInfo
- Publication number
- CN114338783A CN114338783A CN202111314389.3A CN202111314389A CN114338783A CN 114338783 A CN114338783 A CN 114338783A CN 202111314389 A CN202111314389 A CN 202111314389A CN 114338783 A CN114338783 A CN 114338783A
- Authority
- CN
- China
- Prior art keywords
- api
- management
- user
- gateway
- 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
Images
Abstract
The invention relates to an API management platform based on a technical middle platform, which comprises: the system comprises a service providing system, a service consuming system, an API management layer and an API gateway; the service providing system includes: a backend application that can provide services; the service consumption system includes: a consumer user system having a need to use a service; the API management layer comprises: the system comprises a user management module, an API access module and an API market; the user management module provides the registration of the user and the management function of the registration system; the API access module is used for exposing an API of a back-end application of the service providing system to the outside through an interface and registering the API on an API gateway; the API marketplace provides unified and common modules and standards that enable consumer user systems of the service consumption system to use services provided by backend applications of the service provision system registered on the API management platform based on the technical middlebox through API subscription. The invention has the advantage of improving the efficiency of system integration.
Description
Technical Field
The invention relates to an API management platform based on a technical middle platform and a management method thereof.
Background
Over time, there is an increasing number of information systems within an enterprise, since different developers and developers are involved, and the probability between systems is the relationship of an island system, which has a great influence on the multiplexing of the internal capacity of the enterprise and the series connection of business systems. Often enterprises will address these issues through system integration. At present, the main flow scheme of intercommunication and integration of the capability between systems is solved by some modes such as interface integration, message middleware and the like, the modes are various, and no unified standard exists in the industry.
Most heterogeneous system integration needs to design a personalized integration scheme, needs to be designed and matched independently, has a large influence on enterprise research and development cost, and has different integration difficulty according to enterprise conditions. In addition, generally, the test integration speed between systems is slow, and the period is long, so that a bottleneck is formed to a certain extent, and the rapid innovation and development of the actual business of an enterprise can be restricted. Secondly, the more integrated systems, the failure probability is increased correspondingly, and the overall availability is reduced.
Disclosure of Invention
The present invention is directed to provide an API management platform based on a technical middleware and a management method thereof, so as to solve the problems set forth in the background art.
In order to achieve the purpose, the invention provides the following technical scheme:
an API management platform based on a technical middleware, comprising: the system comprises a service providing system, a service consuming system, an API management layer and an API gateway; the service providing system includes: a backend application that can provide services; the service consumption system includes: a consumer user system having a need to use a service;
the API management layer comprises: the system comprises a user management module, an API access module and an API market; the user management module provides the registration of the user and the management function of the registration system; the API access module is used for exposing an API of a back-end application of the service providing system to the outside through an interface and registering the API on an API gateway; the API market provides unified public modules and standards, so that a consumer user system of the service consumption system can use the service provided by the back-end application of the service providing system registered on the API management platform based on the technical middle platform through API subscription;
the API gateway is based on the transformation and the extension of the Spring Cloud gateway, combines the subscription and the authority service provided by the API market, and forwards the request required by the service consumption system with the subscription authority to the service providing system.
As a further scheme of the invention: the management functions of the user management module include: organization architecture management, tenant management, user management, role management, and rights management.
As a further scheme of the invention: an API access module: an API registration module and an API management module; the API registration module completes the function of registering the API by filling form information; the API management module is able to view the list of APIs and details that have passed the verification.
As a further scheme of the invention: the registration of the API realized by the API access module comprises the following steps:
inputting a source interface path of an original application of the service providing system, and mapping an address;
the method comprises the following steps that two sets of environments are set up in advance by the aid of the original ability of a spring closed gateway at the rear end of a system, wherein the two sets of environments are respectively a testing environment and a formal environment;
the front-end system displays the testing gateway address and the formal gateway address in a page according to the configuration address of the back-end environment;
integrating an http tool at the back end of the page, accessing the address of the test gateway through the http tool, updating the configured route to a test gateway server in real time by using a dynamic refreshing mechanism of a spring closed gateway, if the request returns to normal, storing the route record to a database, and marking the route record as passing the test environment verification;
synchronously updating the configuration of the test gateway to the formal gateway;
and after approval, releasing the API to the API market.
As a further scheme of the invention: the API gateway is provided with a graphical interface and a form flow system; the configuration information of the user can be translated into the content which can be recognized by the spring group gateway and dynamically refreshed.
As a further scheme of the invention: the dynamic refreshing mechanism of the API gateway is realized by adopting the following modes:
after the user enters or updates the routing information, the routing information is updated to the cache redis, the latest routing information in the cache redis is obtained by using a dynamic routing interface RouteDefinitionReposability through an event trigger operation mechanism, and the latest routing information is loaded into a memory of a spring cluster gateway.
As a further scheme of the invention: the open source activi4 is used as a workflow engine, the mysql is combined to store user information, and the user id and the workflow process id are bound, so that the workflow module facing the user system is realized.
As a further scheme of the invention: the API marketplace includes: the system comprises an API home page portal module, an API capability query module, an API document query module and an API subscription module; seeing the API which passes the audit through an API home page portal module; the API can be retrieved by the API capability query module by using the keywords;
the API document query module can maintain and record the documents accessed and used by the user; and allowing the user to subscribe the API published by the system through the API subscription module.
As a further scheme of the invention: a wiki platform is built by utilizing the open-source mm-wiki, and document service is provided according to the opening of the authority; full-text retrieval capability is achieved by using an open-source elastic search.
The management method of the API management platform based on the technical middlebox is characterized by comprising the following steps;
registering a service of the service providing system to an API management platform based on a technical platform;
after the auditing is completed, the service of the service providing system is issued to an API market;
services that have been published to the API marketplace can be subscribed to through the technical middleware based API management platform.
Compared with the prior art, the invention has the beneficial effects that:
a standard scheme and an implementation system which are adaptive to mainstream system integration are defined, the cost of system integration is reduced, and the efficiency of system integration is improved.
The speed of enterprise integration is accelerated, and therefore the innovation speed of actual business of the enterprise is accelerated.
Through the standardization step set by the platform, the integration mode and the capability release mode which are integrally optimized, various tiny problems of the system can be avoided integrally, the error rate is reduced, and the integral usability of the system is improved.
The capabilities of any system are quickly integrated into the capability layer of the company as a whole, and the capabilities are reused for other systems.
The API gateway integrates the capability of protocol conversion and expands the capability of the gateway.
There are gateways that open the market for APIs. This fundamentally changes the way applications are integrated, and firstly, personalized customization is no longer needed for integration. And secondly, the capability propagation range of the service provider is also improved by the search function of the API market. The purpose of this combination is to essentially change the way in which system capabilities are discovered and used. The online and offline capability propagation of the enterprise system is connected in series.
With a tenant management module. The module takes all departments of the whole company as users to use the platform, and is different from a tenant management system in an internet mode.
Drawings
Fig. 1 is a block diagram of an API management platform based on a technical middleware, in which an exemplary flow of external capability registration to the platform is shown above a dotted line, and an exemplary flow of platform opening to the use of external system capability is shown below the dotted line.
The system comprises an API management platform 100 based on a technical middle platform, a service providing system 10, a service consuming system 20, an API management layer 30, a user management module 31, an API access module 32, an API market 33 and an API gateway 40.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the 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 invention.
Referring to fig. 1, in an embodiment of the present invention, an API management platform 100 based on a technical middleware includes: a service providing system 10, a service consuming system 20, an API management layer 30 and an API gateway 40.
As a preferred embodiment, the service providing system 10 is a system used by a user who provides a service. For the sake of distinction and description, the user is identified as user a in fig. 1, and the user providing the service may also be referred to as a service providing user. The service providing system 10 includes: a backend application of the service may be provided. The service providing system 10 may include a plurality of backend applications. As a specific embodiment, referring to fig. 1, the service providing system 10 includes a backend application a and a backend application B. The service providing system 10 is the system of the user a.
The service consumption system 20 is a system used by a user having a demand for using a service. For ease of differentiation and description, the user is identified as user B in fig. 1, and users having a need to use the service may also be referred to as service consuming users. The service consumption system 20 includes: a consumer user system having a need to use a service. The service consumption system 20 is the system of user B.
As a preferred embodiment, the API management layer 30 includes: a user management module 31, an API access module 32 and an API market 33.
The user management module 31 provides registration of users and management functions of the registration system. The user may be either a service providing user or a service consuming user. As a specific embodiment, the management functions of the user management module 31 include: organization architecture management, tenant management, user management, role management, and rights management. The method is mainly developed and modified based on an RBAC authority model.
The API access module 32 is configured to expose an API of a backend application of the service providing system 10 to the outside through an interface, and register the API onto the API gateway 40. The API access module 32 allows the user a to expose the API of the single backend application to the outside through an interface through a flow set by the API management platform 100 based on the technical middleware.
As a preferred embodiment, the API access module 32: an API registration module and an API management module. The API registration module completes the function of registering the API by filling form information. The API management module is able to view the list of APIs and details that have passed validation. Specifically, the form information filled in by the API registration module comprises three forms of basic information, back-end service and verification submission. The API management module, which may also be referred to as my API, may view the API list and details that it submits itself and passes the validation.
As a preferred embodiment, the API access module 32 implements registration of the API including the following steps:
inputting a source interface path of an original application of the service providing system 10, mapping an address;
the method comprises the following steps that two sets of environments are set up in advance by the aid of the original ability of a spring closed gateway at the rear end of a system, wherein the two sets of environments are respectively a testing environment and a formal environment;
and the front-end system displays the testing gateway address and the formal gateway address in a page according to the configuration address of the back-end environment.
Integrating an http tool at the back end of the page, accessing the address of the test gateway through the http tool, updating the configuration route to a test gateway server in real time by using a dynamic refreshing mechanism of a spring closed gateway, if the request returns to normal, storing the route record in a database, and marking that the test environment passes verification
Synchronously updating the configuration of the test gateway to the formal gateway;
after approval, the API is released to the API marketplace 33. Specifically, the user enters the relevant information of the API opened to the API marketplace 33 and submits to the release that implements the API. The system has simple workflow capabilities with open source activi4 integration. The approval flow is to review the submitted information by the administrator and if the review passes, to publish the information to the API marketplace 33. The interface capabilities published to the API marketplace 33 can be searched by all users. The system provides a publishing function, and the interface passing the test verification allows publishing to a formal environment. I.e. the configuration of the test gateway is updated to the official gateway synchronously.
In a preferred embodiment, the API gateway 40 has a graphical interface and a form flow architecture. The configuration information of the user can be translated into the content which can be recognized by the spring group gateway and dynamically refreshed. The use of a patterned cross-section is advantageous for non-skilled personnel to use and manage.
As a preferred embodiment, the dynamic refresh mechanism of the API gateway 40 is implemented as follows:
after entering or updating the routing information, the user updates the routing information to the cache redis, obtains the latest routing information in the cache redis by using a dynamic routing interface Route Definition repeatability through an event trigger operation mechanism, and loads the latest routing information into a memory of the spring closed gateway.
The workflow is integrated into activi4, and the system needs the workflow for approval. The open source activi4 is used as a workflow engine, the mysql is combined to store user information, and the user id and the workflow process id are bound, so that the workflow module facing the user system is realized. The difficulty that the original activi4 workflow engine is difficult to be independent into SaaS service is expanded.
As a specific implementation mode, the processing logic of the spring closed gateway component gateway is rewritten by adopting the natural concurrency performance of the go language, so that the processing efficiency of the gateway is improved. Currently, the logging of gateway service logs is realized through logging records of logback and ngnix. The data flow can be communicated with the monitoring service cloud of the middle station.
As a preferred embodiment, the API marketplace 33 provides unified common modules and standards that enable the consumer user systems of the service consumption system 20 to use the services provided by the backend applications of the service provision system 10 registered to the technical desk-based API management platform 100 through API subscription. For example, user B in the figure subscribes to and uses the services of user A's system through the API marketplace 33.
As a specific embodiment, it is possible to use,
the API market 33 includes: the system comprises an API home page portal module, an API capability query module, an API document query module and an API subscription module. And the API which passes the audit is seen through the API home page portal module. The API may be retrieved by the API capability query module using the keywords. Documents accessed and used by a user can be maintained and recorded through the API document query module. And allowing the user to subscribe the API published by the system through the API subscription module.
The main processes or functions involved in the API market 33 are as follows.
1. After the API capability provided by the user is approved, the system updates the configuration to the gateway of the formal environment through the event processing mechanism. 2. Other users can query for open capabilities published to the API and respond to short introductions. 3. The user applies for a subscription API, which may select a test environment or a production environment. 4. The system administrator approves the subscription application. 5. And the user confirms the approval state and carries out production environment verification test. 6. And after the verification is passed, using a certain signature rule to complete the production on-line.
As a specific implementation mode, a wiki platform is built by using open-source mm-wiki, and the document service is provided by opening the API management platform 100 of the middle platform according to the authority. Full-text retrieval capability is achieved by using an open-source elastic search.
In a preferred embodiment, the API gateway 40, based on the Spring Cloud gateway modification and extension, combines with the subscription and permission services provided by the API market 33, and forwards the request required by the service consumption system 20 having the subscription permission to the service providing system 10. The API Gateway 40 is transformed and expanded based on the Spring Cloud Gateway, and the Spring Cloud Gateway is used as an open source Gateway and has url mapping and reverse proxy functions; allowing the user to extend the filters needed by the user; the performance is relatively good. In the whole architecture, for example, the system of the user B subscribes to the capability of the platform, and in combination with the subscription and permission services provided by the API market 33, the request required by the system having the subscription permission is forwarded to the system actually providing the service, for example, the backend service a of the user a, through the routing agent. Meanwhile, the functions of authentication, flow control, protocol conversion and the like are realized by combining the rules of a service system.
The API management platform 100 based on the technical middle platform unifies the access and use of the API, so that the efficiency and difficulty of system integration are greatly reduced, and the system architecture using the API as a core has agile, extensible and connectable capabilities.
A management method of an API management platform 100 based on technical middleboxes comprises the following steps.
One service of the service providing system 10 is registered with the technical middleware based API management platform 100.
The service of the service providing system 10 is released to the API market 33 after the audit is completed.
Services that have been published to the API marketplace 33 may be subscribed to by the technical middleware based API management platform 100.
Specifically, for example, 1, the user a develops and implements a short message service. 2. User a registers the short message service with the technical midrange based API management platform 100. The step of registering the short message service to the technical middesk-based API management platform 100 by the user A comprises the following steps:
step 1, registering an account number of the API management platform 100 based on the technical middle platform to become a legal authentication user of the platform (for convenience of description, the API management platform 100 based on the technical middle platform is simply referred to as the platform);
step 2, the system provides a single API registration function and a batch registration function (swagger is imported); if the API is registered singly, the API address of the original system is provided, a signature mode needing platform verification is selected, and the system needs to be developed and realized, so that the platform verifies the registered API according to the setting and can register after the verification is passed; specifically, the platform can be applied for accessing the API's appid and appkey (provided by the platform) in advance, and the platform is allowed to pass the legal appid and appkey combination according to the authorization time, thereby completing the API registration function;
and 3, testing the effect of the API. If ok is tested, the system will "translate" the registered associated configuration of the associated API into the system API gateway's routing configuration, and perform dynamic refresh on the API gateway 40 (i.e., the spring closed gateway), at which time the system may have called the API gateway to forward or map the API capabilities to be published. But has not yet been formally released.
And 4, formally submitting and publishing the API to the API market 33 through a publishing function.
3. And issuing the API which needs to be audited by an administrator or a person with corresponding authority, and after the platform administrator passes the audits, formally issuing the API to the API market 33, wherein other third parties can see the introduction of the API in the API market 33 through a search function.
4. Other third parties can subscribe to the API. Such as user B who wants to use the capability of short message distribution and has previously become a user of the platform through a similar registration function. User B may find that the platform has provided the sms capability by searching. The user B applies for the ability of subscribing the API to the platform, the platform issues a token to the user B which needs authorization for using the API, the platform can be used for publishing an address by using the platform when the API gateway of the platform is called, the token is added, the API gateway of the platform carries out translation through internal routing configuration, and then the result responded by the user A system is transmitted to the calling system of the user B after being packaged. Therefore, the user B can directly find the corresponding interface through platform registration and use the corresponding interface rapidly according to the interface document without independently and integrally developing the service for sending the short message.
The API management platform 100 based on the technical middle platform realizes the same communication protocol, shields the protocol between different bottom services and realizes the unification of different services under different protocols.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.
Furthermore, it should be understood that although the present description refers to embodiments, not every embodiment may contain only a single embodiment, and such description is for clarity only, and those skilled in the art should integrate the description, and the embodiments may be combined as appropriate to form other embodiments understood by those skilled in the art.
Claims (10)
1. An API management platform based on a technical middle platform, comprising: the system comprises a service providing system, a service consuming system, an API management layer and an API gateway; the service providing system includes: a backend application that can provide services; the service consumption system includes: a consumer user system having a need to use a service;
the API management layer comprises: the system comprises a user management module, an API access module and an API market; the user management module provides the registration of the user and the management function of a registration system; the API access module is used for exposing an API of the back-end application of the service providing system to the outside through an interface and registering the API on the API gateway; the API marketplace provides unified common modules and standards that enable the consumer user system of the service consumption system to use services provided by the backend application of the service provision system registered on the technical middlebox-based API management platform through API subscription;
the API gateway is based on the transformation and the extension of the Spring Cloud gateway, combines the subscription and permission services provided by the API market, and forwards the request required by the service consumption system with the subscription permission to the service providing system.
2. The technical middesk based API management platform of claim 1,
the management functions of the user management module comprise: organization architecture management, tenant management, user management, role management, and rights management.
3. The technical middesk based API management platform of claim 1,
the API access module: an API registration module and an API management module; the API registration module completes the function of registering the API by filling form information; the API management module is able to view the list of APIs and details that have passed validation.
4. The technical middesk based API management platform of claim 3,
the registration of the API realized by the API access module comprises the following steps:
inputting a source interface path of an original application of the service providing system, and mapping an address;
the method comprises the following steps that two sets of environments are set up in advance by the aid of the original ability of a spring closed gateway at the rear end of a system, wherein the two sets of environments are respectively a testing environment and a formal environment;
the front-end system displays the testing gateway address and the formal gateway address in a page according to the configuration address of the back-end environment;
integrating an http tool at the back end of the page, accessing the address of the test gateway through the http tool, updating the configured route to a test gateway server in real time by using a dynamic refreshing mechanism of a spring closed gateway, if the request returns to normal, storing the route record to a database, and marking the route record as passing the test environment verification;
synchronously updating the configuration of the test gateway to the formal gateway;
and after the approval is passed, the API is issued to the API market.
5. The technical middesk based API management platform of claim 1,
the API gateway is provided with a graphical interface and a form flow system; the configuration information of the user can be translated into the content which can be recognized by the spring group gateway and dynamically refreshed.
6. The technical middesk based API management platform of claim 5,
the dynamic refreshing mechanism of the API gateway is realized by adopting the following modes:
after entering or updating the routing information, the user updates the routing information to the cache redis, obtains the latest routing information in the cache redis by using a dynamic routing interface Route Definition repeatability through an event trigger operation mechanism, and loads the latest routing information into a memory of the spring closed gateway.
7. The technical middesk based API management platform of claim 1,
the open source activi4 is used as a workflow engine, the mysql is combined to store user information, and the user id and the workflow process id are bound, so that the workflow module facing the user system is realized.
8. The technical middesk based API management platform of claim 1,
the API marketplace includes: the system comprises an API home page portal module, an API capability query module, an API document query module and an API subscription module; seeing the API which passes the audit through the portal module of the API home page; the API can be retrieved by the API capability query module by using keywords;
the API document query module can maintain and record the documents accessed and used by the user; and allowing the user to subscribe the API published by the system through the API subscription module.
9. The technical midfield-based API management platform of claim 8,
a wiki platform is built by utilizing the open-source mm-wiki, and document service is provided according to the opening of the authority; full-text retrieval capability is achieved by using an open-source elastic search.
10. A management method of API management platform based on technical middleboxes according to any claim 1 to 9, characterized by comprising the following steps;
registering a service of the service providing system with the technical middleware-based API management platform;
after the auditing is completed, the service of the service providing system is issued to the API market;
services that have been published to the API marketplace can be subscribed to by the technology middleware based API management platform.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111314389.3A CN114338783A (en) | 2021-11-08 | 2021-11-08 | API management platform based on technical middlebox and management method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111314389.3A CN114338783A (en) | 2021-11-08 | 2021-11-08 | API management platform based on technical middlebox and management method thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114338783A true CN114338783A (en) | 2022-04-12 |
Family
ID=81045456
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111314389.3A Pending CN114338783A (en) | 2021-11-08 | 2021-11-08 | API management platform based on technical middlebox and management method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114338783A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114866479A (en) * | 2022-04-24 | 2022-08-05 | 中电万维信息技术有限责任公司 | Service gateway-based service fusion method |
| CN115103008A (en) * | 2022-06-13 | 2022-09-23 | 北京奇艺世纪科技有限公司 | Service request forwarding system |
| CN115102749A (en) * | 2022-06-16 | 2022-09-23 | 上海商汤阡誓科技有限公司 | Resource interaction method, device, equipment and storage medium |
| CN116846975A (en) * | 2023-06-07 | 2023-10-03 | 浪潮智慧科技有限公司 | Consumption service method, equipment and medium based on API gateway |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160246592A1 (en) * | 2015-02-20 | 2016-08-25 | International Business Machines Corporation | Dynamic extensibility of application programming interfaces |
| CN107872484A (en) * | 2016-09-27 | 2018-04-03 | 中国电信股份有限公司 | REST API fast registration methods, devices and systems |
| CN108259432A (en) * | 2016-12-29 | 2018-07-06 | 亿阳安全技术有限公司 | A kind of management method of API Calls, equipment and system |
| CN109728974A (en) * | 2018-12-27 | 2019-05-07 | 北京航天智造科技发展有限公司 | Online interface debugging platform |
| CN112448978A (en) * | 2019-08-30 | 2021-03-05 | 中国移动通信集团河北有限公司 | Data management method and system |
| CN112612629A (en) * | 2020-12-28 | 2021-04-06 | 广东广宇科技发展有限公司 | Method and system for realizing component type data interface |
| CN113485685A (en) * | 2021-06-30 | 2021-10-08 | 平安银行股份有限公司 | API interface creating method and device, electronic equipment and medium |
-
2021
- 2021-11-08 CN CN202111314389.3A patent/CN114338783A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160246592A1 (en) * | 2015-02-20 | 2016-08-25 | International Business Machines Corporation | Dynamic extensibility of application programming interfaces |
| CN107872484A (en) * | 2016-09-27 | 2018-04-03 | 中国电信股份有限公司 | REST API fast registration methods, devices and systems |
| CN108259432A (en) * | 2016-12-29 | 2018-07-06 | 亿阳安全技术有限公司 | A kind of management method of API Calls, equipment and system |
| CN109728974A (en) * | 2018-12-27 | 2019-05-07 | 北京航天智造科技发展有限公司 | Online interface debugging platform |
| CN112448978A (en) * | 2019-08-30 | 2021-03-05 | 中国移动通信集团河北有限公司 | Data management method and system |
| CN112612629A (en) * | 2020-12-28 | 2021-04-06 | 广东广宇科技发展有限公司 | Method and system for realizing component type data interface |
| CN113485685A (en) * | 2021-06-30 | 2021-10-08 | 平安银行股份有限公司 | API interface creating method and device, electronic equipment and medium |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114866479A (en) * | 2022-04-24 | 2022-08-05 | 中电万维信息技术有限责任公司 | Service gateway-based service fusion method |
| CN115103008A (en) * | 2022-06-13 | 2022-09-23 | 北京奇艺世纪科技有限公司 | Service request forwarding system |
| CN115103008B (en) * | 2022-06-13 | 2024-03-08 | 北京奇艺世纪科技有限公司 | Service request forwarding system |
| CN115102749A (en) * | 2022-06-16 | 2022-09-23 | 上海商汤阡誓科技有限公司 | Resource interaction method, device, equipment and storage medium |
| CN115102749B (en) * | 2022-06-16 | 2024-03-19 | 上海商汤阡誓科技有限公司 | Resource interaction method, device, equipment and storage medium |
| CN116846975A (en) * | 2023-06-07 | 2023-10-03 | 浪潮智慧科技有限公司 | Consumption service method, equipment and medium based on API gateway |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114338783A (en) | API management platform based on technical middlebox and management method thereof | |
| US7774485B2 (en) | Dynamic service composition and orchestration | |
| JP5583769B2 (en) | Virtual object indirection in the host computer environment | |
| US20100005443A1 (en) | System and Methods to Create a Multi-Tenancy Software as a Service Application | |
| US20050015619A1 (en) | Integration infrastrucuture | |
| US20080162205A1 (en) | Validity path node pattern for structure evaluation of time-dependent acyclic graphs | |
| US20080162563A1 (en) | Generic graph services utilizing anonymous and identified graph pattern | |
| US20080162777A1 (en) | Graph abstraction pattern for generic graph evaluation | |
| US20070124344A1 (en) | Method, apparatus and program storage device for providing web services-based data replication for Heterogeneous storage systems | |
| WO2013000027A1 (en) | Information management systems and methods | |
| US8788533B2 (en) | Read access logging | |
| JP2019501437A (en) | Automatic motion detection on protected fields with support for federated search | |
| US20210233126A1 (en) | Customizable formula based dynamic api evaluation using a database system | |
| US20230107925A1 (en) | Modeling individual interfaces for executing interface queries over multiple interfaces | |
| US20230096376A1 (en) | Unified automation of application development | |
| US20220311595A1 (en) | Reducing transaction aborts in execute-order-validate blockchain models | |
| Fernando | Building Enterprise Software Systems with Microservice Architecture | |
| US20230095852A1 (en) | Translating between versions of data object schemas for data producers and data consumers | |
| US11609747B1 (en) | Decentralized application development and deployment | |
| US11880720B2 (en) | Extensible change control management | |
| AU2017204903A1 (en) | Further improved Information management systems and methods | |
| US20230099061A1 (en) | Multi-tenant hosting of inverted indexes for text searches | |
| de Oliveira | Patterns And Development Strategies Used on a Microservices Architecture | |
| Oliveira | Patterns and development strategies used on a microservices architecture | |
| Bellini et al. | Automating Heterogeneous IoT Device Networks from Multiple Brokers with Multiple Data Models |
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 |