CN115509523A - API service rapid establishing method and system - Google Patents
API service rapid establishing method and system Download PDFInfo
- Publication number
- CN115509523A CN115509523A CN202211478825.5A CN202211478825A CN115509523A CN 115509523 A CN115509523 A CN 115509523A CN 202211478825 A CN202211478825 A CN 202211478825A CN 115509523 A CN115509523 A CN 115509523A
- Authority
- CN
- China
- Prior art keywords
- component
- api service
- flow logic
- standard
- data information
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- 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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method and a system for quickly establishing API service, wherein the method comprises the steps of acquiring data information of API, and determining flow logic according to the data information; sending demand information to a component library according to the data information and the flow logic; the component library confirms a plurality of standard components according to the demand information; and respectively sequencing the standard components according to the data information and the flow logic, and logically linking the standard components to form standard API service. According to the technical scheme, the modularization of service requirements is achieved according to the component library, the logic flow and the existing standard components in the component library are quickly confirmed according to the actual API requirements, the aggregation service, the atomic service interface and the third-party self-defined request URL address in the gateway platform are quickly and compatibly linked, and the quick and efficient API service assembly is achieved.
Description
Technical Field
The invention relates to the technical field of API, in particular to a method and a system for quickly establishing API service.
Background
With the implementation of front-end and back-end separation architecture, micro-service architecture, middle strategy and industry interconnection and intercommunication, enterprises must generate a large number of API services of various protocols, the APIs become digital assets of the enterprises and are more and more, and the mutual calling and dependence situations among the API services are more and more complicated. The API between the business system and between the associated enterprises correspondingly has a large amount of API mutual calling and logic recombination requirements, the existing solution is that the enterprise proposes corresponding business requirements as a demand end, a supplier realizes the requirements in a programming mode, and the traditional solution has certain hysteresis and cannot meet the characteristic of the existing business agile delivery, so that the API service quick construction method and the API service quick construction system need to be provided, and the quick and efficient API service assembly is realized.
Disclosure of Invention
The invention mainly aims to provide a method and a system for quickly establishing an API service, which realize quick and efficient API service assembly.
In order to achieve the above object, the present invention provides a method for quickly establishing an API service, including:
acquiring data information of an API (application program interface), and determining a flow logic according to the data information;
sending demand information to a component library according to the data information and the flow logic;
the component library confirms a plurality of standard components according to the requirement information;
and respectively sequencing the standard components according to the data information and the flow logic, and logically linking the standard components to form standard API service.
Preferably, the standard component includes a metadata field and a UI interface corresponding to the standard component.
Preferably, the component library includes a start component, an end component, a routing component and a plurality of service components, and the standard component is at least one of the start component, the end component, the routing component and the service component.
Preferably, the step of confirming the plurality of standard components by the component library according to the requirement information includes:
the component library confirms the starting component, the ending component, the routing component and at least one business component according to the requirement information;
the step of sequencing each standard component according to the data information and the flow logic, and forming an API service by linking each standard component includes:
and sequencing the starting assembly, the ending assembly and each business assembly according to the data information and the flow logic, and sequentially constructing logic links among the starting assembly, the ending assembly and each business assembly through the routing assembly to form API service.
Preferably, the step of confirming, by the component library, the starting component, the ending component, the routing component, and at least one of the service components according to the requirement information includes:
the component library confirms the starting component, the ending component, the routing component and at least two temporary component packages according to the requirement information, wherein the temporary component packages comprise a plurality of service components;
forming a plurality of virtual API services according to the starting assembly, the ending assembly and each temporary assembly package;
sending each virtual API service to a user, and acquiring the virtual API service confirmed by the user;
and determining each business component according to the confirmed virtual API service.
Preferably, the step of sending each of the virtual API services to a user and obtaining the virtual API service confirmed by the user further includes:
judging whether the number of the virtual APIs confirmed by the user is greater than one;
when the number of the virtual APIs confirmed by the user is more than one, testing each virtual API service, sending the virtual API service with the best test result to the user, and executing the step of obtaining the virtual API service confirmed by the user;
when the number of the virtual APIs confirmed by the user is equal to one, executing the step of determining each service component according to the confirmed virtual API service;
and when the number of the virtual API confirmed by the user is less than one, after a preset time period, executing the step of sending each virtual API service to the user and acquiring the virtual API service confirmed by the user.
Preferably, the step of determining the flow logic according to the data information further includes:
sending the flow logic to a user, and acquiring the confirmed flow logic;
the step of sending the demand information to the component library according to the data information and the flow logic includes:
sending demand information to the component library according to the data information and the confirmed flow logic;
the step of sequencing each standard component according to the data information and the flow logic, and forming a standard API service by logically linking each standard component includes:
and sequencing each standard component according to the data information and the confirmed flow logic, and logically linking the standard components to form standard API service.
Preferably, the step of sending the flow logic to a user and acquiring the flow logic after confirmation further includes: judging whether the confirmed flow logic is the original flow logic;
the step of sending the demand information to the component library according to the data information and the flow logic includes:
when the confirmed flow logic is the original flow logic, first requirement information is sent to the component library according to the data information and the original flow logic;
when the confirmed flow logic is not the original flow logic, first requirement information is sent to the component library according to the data information and the original flow logic, and second requirement information is sent to the component library according to the data information and the confirmed flow logic;
the step of confirming a plurality of standard components by the component library according to the requirement information comprises the following steps:
the component library confirms a plurality of standard components according to the first requirement information and/or the second requirement information;
the step of sorting the standard components respectively according to the data information and the confirmed flow logic, and forming a standard API service by logically linking the standard components comprises:
the standard components are respectively sequenced according to the data information and the confirmed flow logic, and the standard components are logically linked to form standard API service;
the standard components are respectively sequenced according to the data information and the original flow logic, and logical linkage is carried out between the standard components to form a post-supplement API service;
respectively carrying out operation tests on a standard API service and a post-supplement API service, and respectively obtaining a first operation result obtained by operating the standard API service and a second operation result of the post-supplement API service;
and sending the first operation result and the second operation result to a user, acquiring the API service selected by the user according to the first operation result and the second operation result, and confirming the API service selected by the user as the actual operation API service.
In addition, to achieve the above object, the present invention further provides an API service rapid configuration system, which is applied to any one of the above regional medical prescription supervision methods based on a blockchain, and the system includes:
the server acquires data information of the API and determines flow logic according to the data information;
the component library confirms a plurality of standard components according to the demand information;
the processing module is used for sending demand information to the component library according to the data information and the flow logic; and respectively sequencing the standard components according to the data information and the flow logic, and logically linking the standard components to form standard API service.
Preferably, the system further comprises a control module for controlling the movement of each of the modules.
The method comprises the steps of realizing modularization of service requirements according to a component library, quickly confirming logic flows and existing standard components in the component library according to actual API requirements, quickly and compatibly linking aggregation services, atomic service interfaces and third-party self-defined request URL addresses in a gateway platform, and realizing quick and efficient API service assembly.
Drawings
FIG. 1 is a schematic flow chart of a method for quickly building an API service according to the present invention;
fig. 2 is a schematic diagram of functional modules of a rapid API service building system according to the present invention.
The objects, features and advantages of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and do not limit the invention.
In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in itself. Thus, "module", "component" or "unit" may be used mixedly.
Referring to fig. 1, to achieve the above object, a first embodiment of the present invention provides a method for quickly building an API service, including:
step S10, acquiring data information of the API, and determining flow logic according to the data information;
step S20, sending demand information to a component library according to the data information and the process logic;
s30, confirming a plurality of standard components by the component library according to the demand information;
and S40, sequencing the standard components according to the data information and the flow logic, and logically linking the standard components to form standard API service.
The method comprises the steps of realizing modularization of service requirements according to a component library, quickly confirming logic flows and existing standard components in the component library according to actual API requirements, quickly and compatibly linking aggregation services, atomic service interfaces and third-party self-defined request URL addresses in a gateway platform, and realizing quick and efficient API service assembly.
Specifically, the data information includes API participation data, an API name, and an API request mode.
The standard component comprises a metadata field and a UI interface corresponding to the standard component. In particular, the metadata field includes parameters in the flow schedule that specify the component during operation.
The component library comprises a starting component, an ending component, a routing component and a plurality of service components, and the standard components are at least one of the starting component, the ending component, the routing component and the service components respectively. The starting component, the ending component and the routing component are optional components forming the whole process, and the service component is selected according to different data information.
Specifically, each service component in the component library is added in actual use, and service components of service components with different functions in the component library are continuously added in the service process, so that the whole service component is modularized.
In a second embodiment of the API service fast configuration method provided in the present invention, based on the first embodiment, step S30 includes:
step S31, the component library confirms a starting component, an ending component, a routing component and at least one service component according to the requirement information;
step S40, comprising:
and S41, sequencing the starting component, the ending component and each service component according to the data information and the flow logic, and sequentially constructing logic links among the starting component, the ending component and each service component through the routing component to form API service.
In a third embodiment of the method for quickly establishing an API service provided by the present invention, based on the second embodiment, step S31 includes:
step S32, the component library confirms a starting component, an ending component, a routing component and at least two temporary component packages according to the demand information, wherein the temporary component packages comprise a plurality of service components;
step S33, forming a plurality of virtual API services according to the starting assembly, the ending assembly and each temporary assembly package; specifically, the number of virtual API services is consistent with the number of temporary component packages;
step S34, sending each virtual API service to a user, and acquiring the virtual API service confirmed by the user;
and step S35, determining each business component according to the confirmed virtual API service.
The temporary component package is a service component composition scheme which is formed according to the same flow logic and can realize a service target, and a plurality of schemes are sent to a user for selection, so that a plurality of operation schemes can be provided for a client, and the diversity of services can be improved.
In a fourth embodiment of the method for quickly establishing an API service according to the present invention, based on the third embodiment, step S34 further includes:
step S36, judging whether the number of the virtual APIs confirmed by the user is more than one;
step S37, when the number of the virtual APIs confirmed by the user is more than one, testing each virtual API service, sending the virtual API service with the best test result to the user, and executing the step of obtaining the virtual API service confirmed by the user;
step S38, when the number of the virtual APIs confirmed by the user is equal to one, executing step S35;
and step S39, when the number of the virtual APIs confirmed by the user is less than one, and after a preset time period, executing step S34.
The virtual API service is tested in a virtual environment, more accurate selection is improved for users, multi-thread tracking is achieved, the users can confirm final draft more quickly, and overall efficiency is improved.
Specifically, step S39 includes:
step S310, when the number of the virtual APIs confirmed by the user is less than one, judging whether the number of the virtual APIs sent to the user at the last time point is more than 1;
step S311, when the number of the virtual APIs which are sent to the user at the last time point is larger than 1, executing step S34;
in step S312, when the number of virtual APIs sent to the user confirmation at the previous time point is greater than 1, step S37 is performed.
In a fifth embodiment of the method for quickly establishing an API service according to the present invention, based on the first to fourth embodiments, the step of determining the flow logic according to the data information further includes:
s11, sending the flow logic to a user to acquire the confirmed flow logic;
step S20, comprising:
step S21, sending demand information to a component library according to the data information and the confirmed flow logic;
step S40, comprising:
and S41, sequencing the standard components respectively according to the data information and the confirmed flow logic, and logically linking the standard components to form standard API service.
And sending the flow logic to a user for confirmation, wherein the flow logic mainly determines the arrangement sequence of each service component, for example, the flow logic is the sequence of ABCD, wherein B and C are in a parallel relationship, and the user can select to adjust the sequence of B and C, but not change all the flow logic.
In a sixth embodiment of the method for quickly establishing an API service according to the present invention, based on the fifth embodiment, step S11 further includes:
step S12, judging whether the confirmed flow logic is the original flow logic;
step S21, including:
step S22, when the confirmed flow logic is the original flow logic, first requirement information is sent to the component library according to the data information and the original flow logic;
step S23, when the confirmed flow logic is not the original flow logic, first requirement information is sent to the component library according to the data information and the original flow logic, and second requirement information is sent to the component library according to the data information and the confirmed flow logic;
step S30, including:
step S313, the component library confirms a plurality of standard components according to the first requirement information and/or the second requirement information;
step S41, including:
step S42, according to the data information and the confirmed flow logic, sequencing the standard components respectively, and logically linking the standard components to form standard API service;
s43, respectively sequencing the standard components according to the data information and the original flow logic, and logically linking the standard components to form a post-supplement API service;
step S44, respectively carrying out operation tests on the standard API service and the post-compensation API service, and respectively obtaining a first operation result obtained by operating the standard API service and a second operation result of the post-compensation API service;
and step S45, sending the first operation result and the second operation result to the user, acquiring the API service selected by the user according to the first operation result and the second operation result, and confirming the API service selected by the user as the actual operation API service.
And forming different API services according to different logic flows, respectively performing trial operation, and sending each operation structure to user confirmation so that the user confirms the actually operated API service. The standard components are all built by software engineers, compatibility among different standard components has certain error with virtual detection in the actual use process, and the optimal result can be selected by a user through the final stage.
Specifically, step S45 further includes:
step S46, when the standard API service is confirmed to be the API service which is actually operated, establishing user files according to the data information, and storing the post-supplement API service into the user files;
and S47, acquiring the running state of the standard API service, and replacing the standard API service with a post-compensation API service when the error value of the standard API service exceeds a preset warning value.
And a post-compensation scheme is provided for error reporting in later operation and in the process of daily maintenance, and the stability of operation is ensured through a plurality of sets of API service schemes.
Referring to fig. 2, a system for quickly establishing an API service is applied to any one of the above methods, and includes:
the server acquires the data information of the API and determines the flow logic according to the data information;
the component library confirms a plurality of standard components according to the demand information;
the processing module is used for sending the demand information to the component library according to the data information and the flow logic; and respectively sequencing the standard components according to the data information and the flow logic, and logically linking the standard components to form standard API service.
The system also includes a control module for controlling movement of each of the modules. Visual UI interfaces for dragging, pulling and dragging the API are realized through the control module, the difficulty of arrangement in the API service construction process is simplified, and the construction speed is improved.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention or the portions contributing to the prior art may be embodied in the form of a software product, which is stored in a computer readable storage medium (such as ROM/RAM, magnetic disk, optical disk) as described above, and includes several instructions for causing a terminal device to enter the method according to the embodiments of the present invention.
In the description herein, references to the description of the term "an embodiment," "another embodiment," "other embodiments," or "first through Xth embodiments," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, method steps, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of other like elements in a process, method, article, or system comprising the element.
The above-mentioned serial numbers of the embodiments of the present invention are only for description, and do not represent the advantages and disadvantages of the embodiments.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention, and all equivalent structures or equivalent processes performed by the present invention or directly or indirectly applied to other related technical fields are also included in the scope of the present invention.
Claims (10)
1. A method for quickly establishing an API service is characterized by comprising the following steps:
acquiring data information of an API (application program interface), and determining a flow logic according to the data information;
sending demand information to a component library according to the data information and the flow logic;
the component library confirms a plurality of standard components according to the requirement information;
and respectively sequencing the standard components according to the data information and the flow logic, and logically linking the standard components to form standard API service.
2. The API service rapid construction method according to claim 1, wherein the standard component comprises a metadata field and a UI interface corresponding to the standard component.
3. The API service rapid building method of claim 1, wherein the component library comprises a start component, an end component, a routing component and a plurality of business components, and the standard component is at least one of the start component, the end component, the routing component and the business components.
4. The method for quickly building the API service according to claim 3, wherein the step of the component library confirming the standard components according to the requirement information comprises the following steps:
the component library confirms the starting component, the ending component, the routing component and at least one business component according to the requirement information;
the step of sorting each standard component according to the data information and the flow logic, and linking each standard component to form an API service comprises:
and sequencing the starting assembly, the ending assembly and each business assembly according to the data information and the flow logic, and sequentially constructing logic links among the starting assembly, the ending assembly and each business assembly through the routing assembly to form API service.
5. The method for quickly building the API service according to claim 4, wherein the step of the component library identifying the start component, the end component, the routing component and at least one of the business components according to the requirement information includes:
the component library confirms the starting component, the ending component, the routing component and at least two temporary component packages according to the requirement information, wherein the temporary component packages comprise a plurality of service components;
forming a plurality of virtual API services according to the starting component, the ending component and each temporary component package;
sending each virtual API service to a user, and acquiring the virtual API service confirmed by the user;
and determining each business component according to the confirmed virtual API service.
6. The method for quickly building the API service according to claim 5, wherein the step of sending each of the virtual API services to the user and obtaining the virtual API service confirmed by the user further comprises:
judging whether the number of the virtual APIs confirmed by the user is greater than one;
when the number of the virtual APIs confirmed by the user is more than one, testing each virtual API service, sending the virtual API service with the best test result to the user, and executing the step of obtaining the virtual API service confirmed by the user;
when the number of the virtual API confirmed by the user is equal to one, executing the step of determining each service component according to the confirmed virtual API service;
and when the number of the virtual API confirmed by the user is less than one, after a preset time period, executing the step of sending each virtual API service to the user and acquiring the virtual API service confirmed by the user.
7. The method for quickly building an API service according to any one of claims 1-6, wherein said step of determining a flow logic according to said data information further comprises:
sending the flow logic to a user, and acquiring the confirmed flow logic;
the step of sending the demand information to the component library according to the data information and the flow logic includes:
sending demand information to the component library according to the data information and the confirmed flow logic;
the step of sequencing each standard component according to the data information and the flow logic, and forming a standard API service by logically linking each standard component includes:
and sequencing each standard component according to the data information and the confirmed flow logic, and logically linking the standard components to form standard API service.
8. The method for quickly building the API service according to claim 7, wherein the step of sending the flow logic to the user and obtaining the confirmed flow logic further comprises: judging whether the confirmed flow logic is the original flow logic or not;
the step of sending the demand information to the component library according to the data information and the flow logic includes:
when the confirmed flow logic is the original flow logic, first requirement information is sent to the component library according to the data information and the original flow logic;
when the confirmed flow logic is not the original flow logic, first requirement information is sent to the component library according to the data information and the original flow logic, and second requirement information is sent to the component library according to the data information and the confirmed flow logic;
the step of confirming a plurality of standard components by the component library according to the requirement information comprises the following steps:
the component library confirms a plurality of standard components according to the first requirement information and/or the second requirement information;
the step of sorting the standard components respectively according to the data information and the confirmed flow logic, and forming a standard API service by logically linking the standard components comprises:
the standard components are respectively sequenced according to the data information and the confirmed flow logic, and the standard components are logically linked to form standard API service;
the standard components are respectively sequenced according to the data information and the original flow logic, and logical linkage is carried out between the standard components to form a post-supplement API service;
respectively carrying out operation tests on a standard API service and a post-supplement API service, and respectively obtaining a first operation result obtained by operating the standard API service and a second operation result of the post-supplement API service;
and sending the first operation result and the second operation result to a user, acquiring the API service selected by the user according to the first operation result and the second operation result, and confirming the API service selected by the user as the actual operation API service.
9. A rapid API service construction system, which is applied to a rapid API service construction method according to any one of claims 1-8, and comprises:
the server acquires data information of the API and determines flow logic according to the data information;
the component library confirms a plurality of standard components according to the demand information;
the processing module is used for sending demand information to the component library according to the data information and the flow logic; and respectively sequencing the standard components according to the data information and the flow logic, and logically linking the standard components to form standard API service.
10. The API service rapid building system of claim 9, further comprising a control module for controlling movement of each of said standard components.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211478825.5A CN115509523B (en) | 2022-11-24 | 2022-11-24 | API service rapid construction method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211478825.5A CN115509523B (en) | 2022-11-24 | 2022-11-24 | API service rapid construction method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115509523A true CN115509523A (en) | 2022-12-23 |
| CN115509523B CN115509523B (en) | 2023-03-03 |
Family
ID=84513819
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211478825.5A Active CN115509523B (en) | 2022-11-24 | 2022-11-24 | API service rapid construction method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115509523B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160127454A1 (en) * | 2014-10-30 | 2016-05-05 | Equinix, Inc. | Interconnection platform for real-time configuration and management of a cloud-based services exchange |
| CN106790536A (en) * | 2016-12-21 | 2017-05-31 | 国网江西省电力公司信息通信分公司 | Composite Web services system of selection based on affairs and QoS |
| CN109901838A (en) * | 2019-01-17 | 2019-06-18 | 平安证券股份有限公司 | Front end development approach, device, equipment and storage medium based on modularization |
| CN110286903A (en) * | 2019-05-21 | 2019-09-27 | 深圳壹账通智能科技有限公司 | Construction method, device, equipment and the storage medium of user information list |
| CN111142867A (en) * | 2019-12-31 | 2020-05-12 | 谷云科技(广州)有限责任公司 | Service visual arrangement system and method under micro-service architecture |
| US20200151038A1 (en) * | 2018-11-13 | 2020-05-14 | American Express Travel Related Services Company, Inc. | Automated web service and api build configuration framework |
| CN111736821A (en) * | 2020-06-28 | 2020-10-02 | 中国电子产品可靠性与环境试验研究所（（工业和信息化部电子第五研究所）（中国赛宝实验室）） | Visual modeling analysis method, system, computer device and readable storage medium |
| CN111767047A (en) * | 2020-06-28 | 2020-10-13 | 北京思特奇信息技术股份有限公司 | Micro-service component management method and device |
| CN114879939A (en) * | 2022-04-27 | 2022-08-09 | 深圳市惟客数据科技有限公司 | Method, system, electronic device and storage medium for generating micro service |
| CN115185496A (en) * | 2022-07-20 | 2022-10-14 | 杭州指令集智能科技有限公司 | Service arrangement method based on Flowable workflow engine |
| CN115309387A (en) * | 2022-08-24 | 2022-11-08 | 南威软件股份有限公司 | Method for generating API (application program interface) based on dynamic SQL (structured query language) configuration |
-
2022
- 2022-11-24 CN CN202211478825.5A patent/CN115509523B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160127454A1 (en) * | 2014-10-30 | 2016-05-05 | Equinix, Inc. | Interconnection platform for real-time configuration and management of a cloud-based services exchange |
| CN106790536A (en) * | 2016-12-21 | 2017-05-31 | 国网江西省电力公司信息通信分公司 | Composite Web services system of selection based on affairs and QoS |
| US20200151038A1 (en) * | 2018-11-13 | 2020-05-14 | American Express Travel Related Services Company, Inc. | Automated web service and api build configuration framework |
| CN109901838A (en) * | 2019-01-17 | 2019-06-18 | 平安证券股份有限公司 | Front end development approach, device, equipment and storage medium based on modularization |
| CN110286903A (en) * | 2019-05-21 | 2019-09-27 | 深圳壹账通智能科技有限公司 | Construction method, device, equipment and the storage medium of user information list |
| CN111142867A (en) * | 2019-12-31 | 2020-05-12 | 谷云科技(广州)有限责任公司 | Service visual arrangement system and method under micro-service architecture |
| CN111736821A (en) * | 2020-06-28 | 2020-10-02 | 中国电子产品可靠性与环境试验研究所（（工业和信息化部电子第五研究所）（中国赛宝实验室）） | Visual modeling analysis method, system, computer device and readable storage medium |
| CN111767047A (en) * | 2020-06-28 | 2020-10-13 | 北京思特奇信息技术股份有限公司 | Micro-service component management method and device |
| CN114879939A (en) * | 2022-04-27 | 2022-08-09 | 深圳市惟客数据科技有限公司 | Method, system, electronic device and storage medium for generating micro service |
| CN115185496A (en) * | 2022-07-20 | 2022-10-14 | 杭州指令集智能科技有限公司 | Service arrangement method based on Flowable workflow engine |
| CN115309387A (en) * | 2022-08-24 | 2022-11-08 | 南威软件股份有限公司 | Method for generating API (application program interface) based on dynamic SQL (structured query language) configuration |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115509523B (en) | 2023-03-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7519917B2 (en) | Method and apparatus for graphically displaying compatible workflow steps | |
| US6856679B2 (en) | System and method to provide automated scripting for customer service representatives | |
| US5838969A (en) | System and method for collecting and dispatching selected events in a computer application program | |
| US20080126987A1 (en) | Graphical representation of compatible workflow steps | |
| Lau et al. | Partner selection and information infrastructure of a virtual enterprise network | |
| US20070156878A1 (en) | System and method for managing workflow execution in a distributed system | |
| CN1464401A (en) | Object oriented system and method using shadow object for verification control | |
| CN109522527A (en) | A method of site construction technology establishment is carried out using software systems | |
| CN107122232A (en) | A kind of Multimedia Task processing unit and method | |
| CN112579455B (en) | Automatic interface testing method and device, electronic equipment and storage medium | |
| CN111340378A (en) | Product project scheduling method and related device | |
| CN115617780A (en) | Data import method, device, equipment and storage medium | |
| Gerosa et al. | Development of groupware based on the 3C collaboration model and component technology | |
| CN115509523B (en) | API service rapid construction method and system | |
| CN113326026B (en) | Method and terminal for generating micro-service business process interface | |
| AU2002258345A1 (en) | An enterprise knowledge and information acquisition, management and communications system with intelligent user interfaces | |
| CN104040537B (en) | The system and method for automatically generating and performing of data base querying | |
| CN1410917A (en) | Circuit principle graph automatic checking method | |
| US8234597B2 (en) | Tool and method to graphically correlate process and test data with specific chips on a wafer | |
| CN105302728A (en) | Testing method and device of SAP (System Applications and Products) interface | |
| CN112541732A (en) | Intelligent bidding contract generation method and device and readable storage medium | |
| CN116911393B (en) | Quantum chip design system, quantum chip design method, electronic equipment and storage medium | |
| Zellmer et al. | Decision Making for Managing Automotive Platforms: An Interview Survey on the State-of-Practice | |
| EP1850227A1 (en) | Data processing system and metod for providing a status management service | |
| CN112181803B (en) | Data processing method and device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |