Service interface processing method and device, computer device and storage medium

Abstract

The application relates to a service interface processing method and device, computer equipment and a storage medium. The method comprises the following steps: acquiring service definition data specified in a service interface generation interface; generating a corresponding service interface based on the service definition data; in response to an arrangement operation in a service arrangement interface, processing a selected public interface and a service interface selected from the generated service interface to generate a new service interface; the new service interface is used for calling the selected service interface and the public interface; performing automatic testing on the generated service interface to obtain a service interface to be registered; and after the service interface to be registered is registered in a micro-service center, the registered service interface is published. Therefore, the service interface can be delivered agilely.

Description

TECHNICAL FIELD

[0001] The present application relates to the software technical field, in particular to a service processing method and device, computer equipment and storage medium. BACKGROUND

[0002] With the rapid development of digital transformation, the continuous expansion of business of companies and organizations, the increasing demand and the increasing number of users, the traditional monolithic architecture has been unable to adapt to the rapid changes of cloud computing era applications, and the micro-service architecture is considered to be the direction of building a new generation of distributed architecture applications in the future. By dividing the application into smaller service interfaces, it is convenient for upgrading and expansion. Enterprises can assemble various products by calling various service interfaces to provide personalized services to the outside and the inside.

[0003] However, due to the excessive number of service interfaces, it takes a lot of resources to generate and publish service interfaces, and cannot be delivered agilely. Therefore, it is necessary to improve the efficiency to realize agile delivery. SUMMARY

[0004] Therefore, it is necessary to provide a service interface processing method and device, computer equipment, storage medium and computer program product capable of agile delivery.

[0005] In a first aspect, the present application provides a service interface processing method. The method comprises:

[0006] obtaining service definition data specified in a service interface generation interface;

[0007] generating a corresponding service interface based on the service definition data;

[0008] In response to an arrangement operation in a service arrangement interface, processing a selected public interface and a service interface selected from the generated service interfaces to generate a new service interface; the new service interface is used to call the selected service interface and the public interface;

[0009] performing automatic testing on the generated service interface to obtain a service interface to be registered;

[0010] After registering the service interface to be registered to the micro-service center, publishing the registered service interface.

[0011] In one embodiment, the service definition data includes at least one of structured query language data, data source information, data processing model identifier and data model identifier; and the generating a corresponding service interface based on the service definition data comprises at least one of the following processing:

[0012] determine a data processing model and a data model specified in the service interface generation interface, and generate a first service interface; the first service interface is used to process data obtained by the data model through the data processing model;

[0013] determine structured query language data and a data source specified in the service interface generation interface, and generate a second service interface; the second service interface is used to perform structured query in the data source through the structured query language data.

[0014] In one of the embodiments, the service definition data includes at least one of cross-platform service code and database stored procedure information; and the generating the corresponding service interface based on the service definition data includes at least one of the following processes:

[0015] confirm the database stored procedure information specified in the service interface generation interface, and generate a third service interface; the third service interface is used to run the database stored procedure information based on the input parameter passed by the calling party and obtain the database return result;

[0016] confirm the cross-platform service code specified in the service interface generation interface, and generate a fourth service interface; the fourth service interface is used to run the cross-platform service code and return the running result.

[0017] In one of the embodiments, the orchestration operation includes interface selection operation and interface movement operation; and the processing the selected public interface and the service interface selected from the generated service interface in response to the orchestration operation in the service orchestration interface to generate a new service interface; the new service interface is used to call the selected service interface and the public interface includes:

[0018] display a service orchestration interface;

[0019] determine the selected public interface and the service interface selected from the generated service interface in response to the interface selection operation in the service orchestration interface;

[0020] determine the running order between the selected service interface and the public interface in response to the interface movement operation for the selected service interface and the public interface;

[0021] process the selected service interface, the public interface and the running order to generate a new service interface; the new service interface is used to call the selected service interface and the public interface according to the running order.

[0022] In one of the embodiments, the performing the automatic test on the generated service interface to obtain the service interface to be registered includes:

[0023] in response to a configuration operation in the test interface, constructing an automated test environment for the service interface;

[0024] in response to a test orchestration operation in the test interface, determining a test scenario for the service interface;

[0025] automatically testing the service interface in the automated test environment using the test scenario to obtain a service interface to be registered.

[0026] In one of the embodiments, after the service interface to be registered is registered to the micro-service center, publishing the registered service interface comprises:

[0027] after the service interface to be registered is registered to the micro-service center, publishing the service interface to be published through a gateway unit, so that a calling party calls the published service interface;

[0028] In the process of the calling party calling the published service interface, at least one of access permission control, access routing control and security control is performed through the gateway unit.

[0029] In one of the embodiments, after the service interface to be registered is registered to the micro-service center, publishing the registered service interface, the method further comprises:

[0030] monitoring the running service interface through a service monitoring unit to obtain at least one of running performance data, call frequency statistical data and call link topology diagram.

[0031] In one of the embodiments, the service interface comprises at least one of a research and development processing interface, an engineering and operation processing interface, a collaborative design interface, a supply chain collaboration interface, a construction and manufacturing service interface, a production operation service interface and a retirement service interface.

[0032] In a second aspect, the application further provides a service interface processing device. The device comprises:

[0033] an interface definition module configured to obtain service definition data specified in a service interface generation interface, and generate a corresponding service interface based on the service definition data;

[0034] an interface orchestration module configured to, in response to an orchestration operation in a service orchestration interface, process a selected public interface and a service interface selected from the generated service interfaces to generate a new service interface, wherein the new service interface is used to call the selected service interface and the public interface;

[0035] an interface test module, configured to perform automatic testing on the generated service interface to obtain a service interface to be registered;

[0036] an interface publishing module, configured to publish the registered service interface after the service interface to be registered is registered to the micro-service center.

[0037] In a third aspect, the present application provides a computer device. The computer device comprises a memory and a processor, the memory stores a computer program, and the processor executes the steps of the service interface processing method.

[0038] In a fourth aspect, the present application provides a computer readable storage medium. The computer readable storage medium stores a computer program, and the computer program is executed by a processor to perform the steps of the service interface processing method.

[0039] In a fifth aspect, the present application provides a computer program product. The computer program product comprises a computer program, and the computer program is executed by a processor to perform the steps of the service interface processing method.

[0040] The service interface processing method, device, computer device, storage medium and computer program product can obtain service definition data specified in a service interface generation interface, generate a corresponding service interface based on the service definition data. In this way, the service interface can be generated through the operation of the interface, and the generation efficiency of the service interface is improved. In the case where the service interface needs to be arranged, at least one service interface and at least one public interface are determined based on the arrangement operation in the service arrangement interface, and a new service interface running the at least one service interface and the at least one public interface is generated. In this way, multiple interfaces can be arranged through the arrangement operation of the interface to generate a new service interface, and the generation efficiency of the service interface is improved. The service interface is tested automatically to obtain a service interface to be published, thereby improving the testing efficiency of the service interface. The service interface to be published is published, so that the calling party can call the published service interface. In this way, the user does not need to write related codes for each function point of the service interface, but only needs to operate the related interface to quickly define, arrange, test and publish the service interface, thereby meeting the requirement of agile delivery for the service interface. BRIEF DESCRIPTION OF DRAWINGS

[0041] Figure 1 An application environment diagram of the service interface processing method in an embodiment;

[0042] Figure 2 A flowchart of the service interface processing method in an embodiment;

[0043] Figure 3 Fig. 1 is a schematic diagram of a principle of a service interface processing method in an embodiment;

[0044] Figure 4 Fig. 1 is a schematic diagram of a principle of a service interface processing method in an embodiment;

[0045] Figure 5 Fig. 2 is a structural block diagram of a service interface processing method device in an embodiment;

[0046] Figure 6 Fig. 3 is an internal structural diagram of a computer device in an embodiment. DETAILED DESCRIPTION

[0047] In order to make the objects, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and not used to limit the present application.

[0048] The service interface processing method provided by the present application can be applied in an application environment as shown in Figure 1 . The terminal 110 communicates with the server 120 through a network. The data storage system can store data required to be processed by the server 120. The data storage system can be integrated on the server 120, or placed on a cloud or other network server. The terminal 110 can be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers and portable wearable devices, and the server 120 can be implemented by an independent server or a server cluster composed of multiple servers.

[0049] The terminal 110 can display a service interface generation interface, a service orchestration interface and other service interface processing related interfaces. The server 120 obtains service definition data specified in the service interface generation interface, and generates a corresponding service interface based on the service definition data. The server 120 responds to the orchestration operation in the service orchestration interface, processes the selected public interface and the service interface selected from the generated service interface, and generates a new service interface; the new service interface is used to call the selected service interface and the public interface. The server 120 performs automatic testing on the generated service interface to obtain a service interface to be registered. The server 120 publishes the registered service interface after registering the service interface to the micro service center. The terminal 110 can access the published service interface.

[0050] In an embodiment, as Figure 2As shown, a service interface processing method is provided, and the embodiment is exemplified by applying the method to a server. It can be understood that the method can also be applied to a terminal, and can also be applied to a system including a terminal and a server, and is implemented through the interaction of the terminal and the server. In the embodiment, the method includes the following steps:

[0051] In S202, service definition data specified in a service interface generation interface is acquired; and a corresponding service interface is generated based on the service definition data.

[0052] The service definition data is data used for defining the service interface.

[0053] Specifically, a user performs a service definition related operation in a service interface generation interface displayed by a terminal to specify service definition data. A server acquires the service definition data specified in the service interface generation interface, and generates a corresponding service interface based on the service definition data.

[0054] In one embodiment, S202 is performed by a service interface integration unit. The service interface integration unit supports at least one of creating a service interface through an entity model, creating a service interface through a business model, creating a service interface through a script, creating a service interface through a stored procedure, etc. The service interface integration unit can also support service simulation, and provide at least one of role management, view template, resource file, application configuration, etc.

[0055] Specifically, the service interface integration unit supports creating a service interface through a data processing model. The server creates an entity model of a table by selecting a created data source, and creates a service interface through the entity model. The entity model is a data processing model that can carry and process data of a table, rather than an abstract model. The service interface integration unit can also support creating a service interface through a business model, support creating a business model of a table by selecting a created data source, and support creating a service interface through a structured query language (SQL) statement. The business model is related to a business and is implemented through multiple data processing models. The service interface integration unit can also support creating a service interface through a script, support creating a service interface through a script code such as SQL, Java, JavaScript, Python, Shell, and the like. The service interface integration unit can also support creating a service interface through a Java Bean, and publishing a key-value pair, a path, and a JSON (JavaScript Object Notation) parameter of the service interface through a platform annotation to implement creation of the service interface. The service interface integration unit can also support creating a service interface through a database stored procedure.

[0056] Specifically, the service interface integration unit can also support service simulation. The service simulation mainly includes simulation data management, a simulation data generator, and a data simulation rule. The simulation data is uniformly managed for all service interface data that needs to be simulated, and can be used in routing configuration and service interface registration. The server can output simulation data to a calling end through the simulation data generator and the data simulation rule, thereby implementing a service interface data simulation function.

[0057] Specifically, the service interface integration unit can also support role management, and implements adding a role and associating a user, a role, and a permission through the role management. The role management can enable a user to manage service interfaces belonging to the user.

[0058] Specifically, the service interface integration unit can also provide a view template function. The service interface integration development platform provides a view template technology, and can develop a page service interface mixed with a front end. The service interface integration unit can view a resource file of a service interface. The service interface integration unit provides an application configuration function to make development more convenient, fast, and beneficial to management.

[0059] S204, in response to the arrangement operation in the service arrangement interface, processing the selected public interface and the service interface selected from the generated service interface, generating a new service interface; the new service interface is used to call the selected service interface and the public interface.

[0060] The public interface is a public interface providing basic functions and can be called by multiple service interfaces. The public interface can be at least one of a process basic component, a script execution component, a message queue component, a process time component, process monitoring, publishing a service interface, arranging a service interface, data conversion and data mapping configuration, rule management, application configuration, service interface arrangement application, a public component library, and platform monitoring function.

[0061] Specifically, the server generates a new service interface in response to the arrangement operation in the service arrangement interface, processing the selected public interface and the service interface selected from the generated service interface. The new service interface is used to call the selected service interface and the public interface.

[0062] In one embodiment, the server executes step S204 through a service interface arrangement unit. The process basic component of the service interface arrangement unit is used for process management and supports calling service interfaces provided by other systems, which mainly includes at least one of a Restful (a design style and development method of a network application, based on HTTP (Hypertext Transfer Protocol), which can use XML (Extensible Markup Language) format definition or JSON format definition) service interface, a WebService (a platform-independent, low-coupling, self-contained, programmable web-based application, which can use open XML (Standard Generalized Markup Language) standard to describe, publish, discover, coordinate and configure these applications, for developing distributed interactive applications), Dubbo (an open source distributed service framework), TCP / IP (Transmission Control Protocol / Internet Protocol) message, variable setting, manual approval, asynchronous callback, asynchronous queue, gateway node, sub-process, data merging, data splitting, file upload, file download, etc.

[0063] The Restful service interface is mainly used to call the Rest (Representational State Transfer) type service interface, and the main input and output is the JSON data format. The WebService node is mainly used to call the interface type data published as WebService in the business system. The Dubbo interface is mainly used to call the RPC (Remote Procedure Call) interface published by Dubbo, so as to realize the mixed arrangement and calling of the Restful interface.

[0064] The manual approval supports the manual approval data flow, only the data flow passing through the manual approval can enter the subsequent execution node, and the service interface approval interface can be connected with each system.

[0065] Sub-process, the service arrangement existing and enabled in the system can be arranged as a sub-process and nested in other service arrangements.

[0066] Service asynchronous execution capability, through the distributed deployment of the arrangement server, any large flow of HTTP service interface request can be coped with. The arrangement server first persists the request flow into MongoDB (a distributed file storage based database), and then schedules the arrangement process through the distributed scheduling coordinator to schedule the arrangement process.

[0067] The gateway node realizes the aggregation of multiple branches through the aggregation type gateway node. Only after all branches are executed and reach the aggregation gateway, the subsequent node will be executed. Therefore, the gateway node must have an aggregation gateway node for branch aggregation.

[0068] The script execution component supports JavaBean, Java rules, SQL, WebService, Dubbo, MQ (message queue), Python, Shell and other types of services for mixed arrangement and can automatically convert data formats between multiple protocols. The JSON data format can be automatically converted to the XML format data of the next service interface node. At the same time, through the mixed arrangement mode of Java code, any business logic and service interface can be recombined and fused, which can solve the complex business process arrangement logic of China General Nuclear.

[0069] The message queue component mainly includes at least one of Kafka (a high-throughput distributed publish / subscribe message system) message, RabbitMQ (an open source message broker software implementing an advanced message queue protocol) message, Mqtt (a message queue transmission protocol adopting a subscription / publish mechanism, and a subscriber only receives data that the subscriber has subscribed to, and does not receive non-subscription data) message, and JMS (Java Message Service) message.

[0070] The flow event component mainly includes at least one of a debug log, an auto-increment setting, a timer, a WeChat message, a DingTalk message, a mail sending, an explanatory text, a start node, and an end node. The debug log supports viewing a debug log generated when a flow is in a debugging state.

[0071] The flow monitoring content mainly includes at least one of a flow to be approved, a flow to be compensated, a compensation failure flow, a node to be compensated, all compensation nodes, an asynchronous waiting queue, a flow not ended, and a flow ended. The flow running statistics can view total running times, success times, failure times, and compensation times of the flow. Clicking the total running times can open all running flow records. The node to be compensated can view a flow list needing forward compensation, and if the compensation is successful, the flow is automatically deleted from the list. The node not ended supports a flow being in running, and the flow in the node not ended is running. If it is desired to forcibly end the flow, the flow can be forcibly ended. The flow ended supports querying all running ended flows.

[0072] Further, the arranged flow can be republished as a new service interface service, so that each time the service interface service is called, the flow is executed once and the execution result of the flow is output to the calling end. The service interface arrangement can realize adding, modifying, deleting, and running operations of the service interface. The data conversion and data mapping configuration support configuring three types of data mapping, namely, fixed value, reference value, and script. Through them, the assembly of the service arrangement interface, the request interface input parameter, and the processing of the return result can be completed. The data conversion includes result data clipping, field name mapping, field value conversion, data cleaning rule, XML to JSON, format conversion template, and mapping configuration template. The fixed value is mainly used for a hard-coded scene, the reference value is mainly used for reference between steps or from input, and the script supports configuring a script for a field, and a return result of the field is used as a value of the field. An asterisk wildcard can receive a return object type reference value, and fields in the return object are merged into a target object.

[0073] The rule management supports unified management and publishing of rule codes executed in event nodes in process orchestration, and can add, modify, delete, etc. rules.

[0074] The application configuration mainly includes public variable configuration, which is used to configure some common parameters and referenced in nodes or codes.

[0075] The process classification realizes classification and management of orchestration processes, and manages the classification in rules, which can add, delete, modify, etc. the classification.

[0076] The public component library includes at least one component of authentication components, authentication components, traffic control components, cache components, service routing components and log components. The authentication component includes at least one of Basic authentication, standard Token authentication, etc.

[0077] Further, the authentication component includes Basic authentication (basic authentication) and standard Token (token) authentication.

[0078] The Basic authentication, the client accesses the service interface in each HTTP request header. The ID gateway receives the request and obtains the corresponding application ID and password from the HTTP header. The values stored in the local database are compared, and if successful, the execution continues.

[0079] Standard Token authentication, first access the authentication interface provided by the gateway to obtain Token, and then access the service interface with Token in the request header.

[0080] The authentication component is used to identify whether the client application has permission to access the current service interface. The permission of the client application can be authorized through the group to which the service interface belongs or directly through the service interface to be accessed.

[0081] The traffic control component limits the calling frequency of the service interface to avoid the service provider of the service interface from collapsing due to high concurrency.

[0082] The cache component is used to cache the data returned by the backend service interface. If the service interface starts the cache gateway, it will first try to obtain data from the cache. If the data expires or does not hit the cache, the backend service is called to query the data.

[0083] The service routing component forwards the request of the client application received by the gateway to the backend service provider, supports protocol conversion, load balancing, etc. The platform currently supports Restful and Webservice service registration and exposure. Other types of protocols can be implemented through custom routing components.

[0084] A log component is configured to record access logs of the service interface, including the number of calls per minute, average response time, total traffic, accuracy, etc. All report displays of the monitoring center are based on the data collected by the component. The component is bound by default when the service interface is created, and the user can also choose not to collect monitoring data.

[0085] The service interface service orchestration monitoring content mainly includes management platform logs, orchestrated service interfaces, process running statistics, process scheduling statistics, cluster servers, registration center service instances, memory thread monitoring, etc.

[0086] S206, performing automated testing on the generated service interface to obtain a service interface to be registered.

[0087] Specifically, the server performs automated testing on the generated service interface, outputs an automated testing report, and further obtains a service interface to be registered.

[0088] In one embodiment, the automated testing is implemented based on a service test unit. The service is used to build an automated testing environment for the service interface based on a web interface, and can implement complex testing scenarios for the service interface and output a testing report, thereby greatly improving the service interface testing efficiency.

[0089] Further, the service interface integration unit supports custom test cases, can set service addresses and input parameters for service interfaces in related business fields, arrange according to certain business logic, add test plans, and then perform automated testing. According to the test use syntax of the service interface, the results are asserted, different business logics are executed according to different assertion results, and complex service interface testing scenarios can be completed.

[0090] S208, after registering the service interface to be registered to the micro-service center, publishing the registered service interface.

[0091] Specifically, the server registers the service interface to be registered to the micro-service center, and publishes the registered service interface, so that the calling party can call the published service interface.

[0092] In one embodiment, the server registers the service interface based on a service registration and configuration unit. The service registration and configuration unit includes a service registration center and a service configuration center.

[0093] Further, the service registry center is a customized registry center, providing a complete solution of micro-service framework, and the service interface gateway and the configuration center keep close communication with the service registry center. The service interface gateway will find all available server lists from the registry center according to the instance name and use different load balancing algorithms for distribution, and all micro-services will report the state information, performance data, etc. of the application to the registry center through heartbeat.

[0094] The service registry center includes cluster server management, online service instance management and offline service instance management. The cluster server management supports multiple registry center servers for clustering, and all service registration and discovery center cluster servers can be managed uniformly in the Web interface and the data consistency can be highly guaranteed. The online service instance management supports management of the current effective servers, and supports manual adjustment of the performance parameter weight of each server, and also supports manual registration of third-party server instances. The offline service instance management puts the service instances into invalid service instances for unified management when the service instances do not report the state to the registry center for a period of time, and when the service instances are active again, they will automatically enter the available service instances, and the service instance data will be persisted to the database and will not be lost due to server restart.

[0095] The positioning of the service configuration center is a configuration center solution for enterprise distributed deployment architecture, full-web configuration, simple and easy to use, non-intrusive, without modifying the SpringBoot (an open source framework) annotation and any code, the platform automatically takes over the configuration, mainly including configuration center homepage, all configuration list, pending release configuration, public configuration, edit configuration, change log, configuration snapshot, environment management, application management, etc.

[0096] The service configuration center includes configuration management, environment management and application management. The configuration management supports modification, release, deletion and other operations of the configuration, and the configuration value is in the unissued state after modification, and only after active release can it take effect, and after release, the old configuration will form a historical version relationship, and at any time can be rolled back to any version of the configuration value. The environment management has a self-defined environment management function, and users can define multiple configuration environments according to the actual development and online situation. The application management can be defined as a micro-application or a business system, and when an application is upgraded from 1.0 to 2.0, only a 2.0 application configuration needs to be built to be compatible with the old and new versions, and the 1.0 application can still use the 1.0 configuration and the 2.0 application can use the latest 2.0 configuration.

[0097] The service interface processing method can generate a service interface through the operation of an interface, thereby improving the generation efficiency of the service interface. In the case where the service interface needs to be arranged, at least one service interface and at least one public interface are determined based on the arrangement operation in the service arrangement interface, and a new service interface running the at least one service interface and the at least one public interface is generated. In this way, a plurality of interfaces can be arranged through the arrangement operation of the interface to generate a new service interface, thereby improving the generation efficiency of the service interface. The service interface is subjected to automatic testing to obtain a service interface to be published, thereby improving the testing efficiency of the service interface. The service interface to be published is published to enable a calling party to call the published service interface. In this way, the user does not need to write relevant codes for each function point of the service interface, but only needs to operate the relevant interface to quickly define, arrange, test and publish the service interface, thereby meeting the requirement of agile delivery of the service interface.

[0098] In one embodiment, the service definition data includes at least one of structured query language data, data source information, data processing model identification and data model identification; and generating the corresponding service interface based on the service definition data includes at least one of the following processing: determining the data processing model and the data model specified in the service interface generation interface, and generating a first service interface; wherein the first service interface is used to process data obtained by the data model through the data processing model; determining the structured query language data and the data source specified in the service interface generation interface, and generating a second service interface; wherein the second service interface is used to perform structured query in the data source through the structured query language data.

[0099] Specifically, the service definition data includes at least one of structured query language data, data source information, data processing model identification and data model identification. The server can determine the data processing model and the data model specified in the service interface generation interface, and generate a first service interface. The first service interface is used to process data obtained by the data model through the data processing model. The server can determine the structured query language data and the data source specified in the service interface generation interface, and generate a second service interface. The second service interface is used to perform structured query in the data source through the structured query language data.

[0100] In one embodiment, the server can select a service interface type, name a data processing model, reference a unique identification of a data model, read a database table through association of a database, specify a database table primary key identification, and bind the data processing model with the database table, thereby creating a service interface through the data processing model.

[0101] In one embodiment, the server can also create the service interface of the business model by selecting the service interface type, naming the name of the plurality of data processing models, referencing the unique identifier of the data model, connecting the data source and determining the database table and database primary key identifier by using the SQL statement.

[0102] In one embodiment, the server can also create the service interface by connecting the database, selecting the data model (including the data model, entity model, business model), and selecting the execution mode according to the SQL statement to return the data by writing the code script.

[0103] In this embodiment, the service interface is obtained based on the data processing model specified on the interface and based on the data model, and the service interface is obtained based on the structured query language data specified on the interface and the data source, so that the service interface can be conveniently generated.

[0104] In one embodiment, the service definition data includes at least one of cross-platform service code and database stored procedure information; and generating the corresponding service interface based on the service definition data includes at least one of the following processing: confirming the database stored procedure information specified on the service interface generation interface, generating a third service interface; the third service interface is used to run the database stored procedure information based on the input parameter passed by the calling party and obtain the database return result; confirming the cross-platform service code specified on the service interface generation interface, generating a fourth service interface; the fourth service interface is used to run the cross-platform service code and return the running result.

[0105] Specifically, the service definition data includes at least one of cross-platform service code and database stored procedure information. The server can confirm the database stored procedure information specified on the service interface generation interface, and generate a third service interface. The third service interface is used to run the database stored procedure information based on the input parameter passed by the calling party and obtain the database return result. The server can also confirm the cross-platform service code specified on the service interface generation interface, and generate a fourth service interface. The fourth service interface is used to run the cross-platform service code and return the running result.

[0106] In one embodiment, the cross-platform service code can be Java code. Specifically, the server can customize the name of the Bean (a software component model describing Java), register the Java Bean through the Rest service (a Web service architecture aiming to create a distributed system with good scalability), and then write the Java code. The Java code writing is divided into three ways, one is to write directly, one is to read the code from the local project or other path, and the other is to write through the template code. Finally, the service interface is created through the Java Bean.

[0107] In one embodiment, the server can implement the new data storage procedure by selecting the data source, then generating the storage procedure ID by loading the database storage procedure information, and bringing in the stored input and output parameters by automatically importing the parameters, and finally exposing the URL (Uniform Resource Locator) to realize the creation of the service interface through the data storage procedure information.

[0108] In the embodiment, the service interface is created through the data storage procedure information and the cross-platform service code, thereby improving the diversity of the service interface creation.

[0109] In one embodiment, the arrangement operation includes an interface selection operation and an interface movement operation; in response to the arrangement operation in the service arrangement interface, the selected public interface and the service interface selected from the generated service interface are processed to generate a new service interface; the new service interface is used to call the selected service interface and the public interface, including: displaying the service arrangement interface; in response to the interface selection operation in the service arrangement interface, the selected public interface and the service interface selected from the generated service interface are determined; in response to the interface movement operation for the selected service interface and the public interface, the running order between the selected service interface and the public interface is determined; the selected service interface and the public interface and the running order are processed to generate a new service interface; the new service interface is used to call the selected service interface and the public interface according to the running order.

[0110] Specifically, the arrangement operation includes an interface selection operation and an interface movement operation. The server can display the service arrangement interface. In response to the interface selection operation in the service arrangement interface, the server determines the selected public interface and the service interface selected from the generated service interface. In response to the interface movement operation for the selected service interface and the public interface, the server determines the running order between the selected service interface and the public interface. The server processes the selected service interface and the public interface and the running order to generate a new service interface; the new service interface is used to call the selected service interface and the public interface according to the running order.

[0111] In the embodiment, by selecting and moving the service interface and the public interface, the relevant running order is obtained, thereby obtaining the new service interface running the service interface and the public interface according to the running order, thereby simplifying the generation process of the service interface, making the operation visual and simple, and providing the generation efficiency of the service interface.

[0112] In one embodiment, the automatic testing is performed on the generated service interface to obtain the service interface to be registered, including: constructing an automatic testing environment for the service interface in response to a configuration operation in a testing interface; determining a test scenario for the service interface in response to a test arrangement operation in the testing interface; and performing automatic testing on the service interface in the automatic testing environment using the test scenario to obtain the service interface to be registered.

[0113] Specifically, the server constructs an automatic testing environment for the service interface in response to a configuration operation in a testing interface. The server determines a test scenario for the service interface in response to a test arrangement operation in the testing interface. The server performs automatic testing on the service interface in the automatic testing environment using the test scenario to obtain the service interface to be registered.

[0114] In the embodiment, the automatic testing environment and the test scenario are constructed by operations in the interface to perform automatic testing on the service interface, thereby reducing the testing cost of the service interface and improving the efficiency of service interface generation.

[0115] In one embodiment, after the service interface to be registered is registered in the micro service center, publishing the registered service interface includes: after the service interface to be registered is registered in the micro service center, publishing the service interface to be published through a gateway unit, so that a calling party calls the published service interface; and in the process of the calling party calling the published service interface, at least one of access permission control, access routing control and security control is performed through the gateway unit.

[0116] Specifically, the server can publish the service interface to be published through a gateway unit after the service interface to be registered is registered in the micro service center, so that a calling party calls the published service interface. The server performs at least one of access permission control, access routing control and security control through the gateway unit in the process of the calling party calling the published service interface.

[0117] Specifically, the gateway unit, as a unified entrance for all business system integrated service interfaces, provides at least one of centralized authentication, error early warning, data encryption and decryption, protocol conversion, security protection, log auditing and other core functions for all business system service interfaces. The gateway unit is distributedly deployed and supports custom component extension, supports multi-tenant capability, and can realize service interface registration, plug-in configuration, service interface auditing and monitoring of the service interface gateway by different teams and different developers at the same time.

[0118] Further, the gateway unit supports service interface registration, mainly registers and forwards the service interface of the backend service individually, can configure mapping parameters and address information, and can convert Rest to webservice service interface.

[0119] The gateway unit supports service interface routing configuration. By configuring certain forwarding rules, mainly according to the path of the URL to calculate an address matching the backend server, and then batch forwarding all http requests requesting this URL to the backend server.

[0120] The gateway unit supports gateway configuration management, including backend service management, routing classification management, and global variable configuration:

[0121] Backend service management. Customer developers can develop different routing conversion components according to the type of backend service interface, package them into Jar (Java Archive) format according to the agreed format, and publish them through the management center for use. The gateway provides Rest-style service routing by default;

[0122] Routing classification management. A new routing classification can be created, or a routing can be created under an existing routing classification. It is recommended to create a corresponding routing classification according to the business system requirements;

[0123] Global variable configuration. The host address of the backend service interface can be modified by referencing the gateway variable in the backend service interface path.

[0124] The gateway unit supports data management, including simulation data management, data conversion rules, and data caching rules:

[0125] Simulation data is a unified management of all service interface data that needs to be simulated and can be used in routing configuration and service interface registration;

[0126] A new conversion rule is added to append a header to the registered service interface, modify the body parameter of the request, or clip the return body data of the registered service interface through a script to add or reduce fields;

[0127] For query-type service interfaces with infrequent data changes, appropriate caching can effectively reduce the pressure on the backend service. Management personnel can configure whether to cache and update the policy according to the characteristics of the service interface service.

[0128] Through client identity authentication, call permission configuration, data encryption configuration, IP whitelist, blacklist mechanism, secondary development extensible customized security function, and flow limiting rule configuration, the security of the service interface is protected.

[0129] The gateway unit can realize timeout warning, error code warning, rate warning, service warning, etc. through early warning setting.

[0130] The gateway unit supports gateway monitoring, including management platform log, gateway topology diagram, server link monitoring, gateway cluster server, real-time request service interface monitoring, Hystrix (a fault-tolerant component, which realizes timeout mechanism and circuit breaker mode) fuse monitoring, and registration center service instance.

[0131] The gateway unit is a distributed deployment architecture and supports custom component extension.

[0132] The gateway unit supports viewing service interface publishing history (such as version, publishing description, publishing time and publishing environment), and supports rolling back to any service interface historical version, so as to meet the needs of business gray release, version upgrade, rollback, etc.

[0133] The gateway unit supports calling different back-end services in different environments through creating environment variables for the same service interface.

[0134] The gateway unit supports using a unified identity authentication service to manage the permissions of the service interface gateway service it owns.

[0135] The gateway unit supports creating a VPC (a kind of cloud computing service) channel to access resources in the VPC environment, and opening service interfaces for back-end services deployed in the VPC. At the same time, the VPC channel has a load balancing function, so as to realize load balancing of the back-end services.

[0136] The gateway unit supports signature keys, which are used for back-end service to verify the identity of the service interface gateway. When the gateway unit requests the back-end service, the security of the back-end service is guaranteed.

[0137] The gateway unit supports service interface intelligent identification, including Restful WebService automatic identification, automatic registration and one-key publishing, and intelligent identification of service interface parameters.

[0138] In the embodiment, at least one of access permission control, access routing control and security control is performed through the gateway unit, thereby improving the standardization, security and effectiveness of the access to the service interface.

[0139] In one embodiment, after registering the service interface to be registered to the micro-service center, and after publishing the registered service interface, the method further comprises: monitoring the running service interface through the service monitoring unit to obtain at least one of running performance data, call frequency statistical data and call link topology diagram.

[0140] Specifically, after the service interface to be registered is registered to the micro-service center, the server monitors the running service interface through the service monitoring unit to obtain at least one of running performance data, call frequency statistical data, and call link topology graph.

[0141] Specifically, the service monitoring unit is a micro-service real-time monitoring center. Through the monitoring center, the running status and performance data of the service interface can be understood and analyzed in real time. Meanwhile, as a unified monitoring center of micro-services, the monitoring center collects running performance data of all micro-service instances in real time. All micro-service instances aggregate monitoring data through heartbeat or log. The monitoring center analyzes and counts through unified monitoring charts or panels. The main functions of the monitoring center include: service interface runtime monitoring, service interface call statistical analysis, application server monitoring, cache and container monitoring, link analysis, service interface asynchronous queue, and system running log.

[0142] Further, the main functions of the monitoring center include: service interface runtime monitoring, service interface call statistical analysis, application server monitoring, cache and container monitoring, link analysis, service interface asynchronous queue, and system running log.

[0143] Through the Rest service, a list of running conditions of all service interfaces can be opened, including service interface real-time request monitoring, service interface real-time running data, service interface execution exception monitoring, non-HTTP 200 status code request, etc.

[0144] Through service interface call statistical analysis, the following information can be viewed: service interface daily call frequency, service interface call frequency and performance, service interface average performance distribution graph, application call frequency Top statistics, user call frequency Top statistics, service interface status code distribution statistics, each cluster server call frequency, and invalid or repeated service interface list.

[0145] Through application server monitoring, the following can be achieved: cluster server monitoring, local service instance cache, memory and thread monitoring, network connectivity monitoring, etc.

[0146] Through cache and container monitoring, the following can be monitored: JavaBean object container, instantiation error Bean, SpringBean (an object instantiated, assembled, and managed by a Spring control inversion container), loaded Jar package list, all platform caches, Bean instance cache, Bean configuration cache, service interface configuration cache, etc.

[0147] Through the service monitoring unit, the calling conditions of all service interfaces are automatically collected and a topology graph of the calling link is formed, so that the service instance is tracked according to the user, the service interface is tracked according to the user, the service interface dependency is viewed, the service instance is tracked, the global service dependency graph is tracked, and the tracking is tracked according to the tracking identifier.

[0148] Through the service interface asynchronous queue calling library, the application service interface sends a notification message, puts the operation into the message queue for step-by-step consumption, and after the previous logic is completed, the service interface of another application is called to notify the result.

[0149] Through the system operation log, the platform log, the service interface calling log, the system operation log, the search service interface log, the user login log, the log library management, and the system recycling station can be managed. The log storage mode supports storage in a database and a table, and can clean up unnecessary log data at regular intervals, and can record detailed all request and response end data to facilitate auditing of the calling condition. Various charts are supported to analyze the log and obtain a problem solution.

[0150] In the embodiment, at least one of the running performance data, the calling frequency statistical data and the calling link topology graph is obtained through the service monitoring unit to monitor the running service interface, so that the service interface can be further optimized.

[0151] In one embodiment, the service interface includes at least one of a research and development processing interface, an engineering and operation processing interface, a collaborative design interface, a supply chain collaboration interface, a construction and manufacturing service interface, a production operation service interface, and a retirement service interface.

[0152] Specifically, the research and development processing interface, the engineering and operation processing interface, the collaborative design interface, the supply chain collaboration interface, the construction and manufacturing service interface, the production operation service interface, and the retirement service interface are interfaces provided by a research and development processing unit, an engineering and operation management unit, a collaborative design unit, a supply chain collaboration unit, a construction and manufacturing service unit, a production operation service unit, and a retirement service unit. These units are used for integration and unified management of various micro-service components of nuclear power business. A total of 7 categories, including research and development processing, engineering and operation management, collaborative design, supply chain collaboration, construction and manufacturing service, production operation service, and retirement service, 62 industrial micro-service components are formed, and services are provided externally in a standard form.

[0153] The research and development processing unit specifically includes a research and development project management component, a research and development fund management component, a research and development achievement management component, a collaborative research and development management component, a research and development evaluation management component, a research and development knowledge management component, a research and development performance management component, an achievement transformation management component, a system and standard management component, and a research and development decision analysis component.

[0154] The R&D project management component enables full lifecycle management of model R&D projects, effectively controlling project application and approval, progress, funding, quality, and documentation. The R&D funding management component provides precise budgeting, funding control, and cost quantification, enabling pre-planning, in-process control, and post-event statistical management of R&D funding. The R&D results management component manages the application, confirmation, and processing of R&D results. The collaborative R&D management component provides project leaders, partners, and the R&D team with R&D management tools through real-time project planning and task execution tracking, achieving clear management of project tasks. The R&D review management component can be applied to innovation and idea solicitation review, project initiation review, project acceptance review, and project stage review; it is a dedicated review system for model R&D operations. The R&D knowledge management component enables knowledge sharing within R&D units, solidifies the knowledge achievements of R&D personnel, improves knowledge reuse rates, and helps R&D units form an automated knowledge base construction system. The R&D performance management component manages the performance evaluation of R&D departments, projects, and personnel, allowing for dynamic setting of assessment indicators and rules. The results transformation management component manages the application, confirmation, and processing of R&D results. The system and standards management component mainly includes enterprise standard system management, standard implementation and supervision management, enterprise standard development management, and external standard development management. The R&D decision analysis component provides enterprise leaders, expert teams, and leaders of various model R&D departments with model R&D information retrieval and statistics, facilitating users to readily grasp the model R&D capabilities of their respective units.

[0155] The engineering operation management unit includes design management components, engineering document management components, engineering project management components, decision support components, comprehensive business management components, and comprehensive safety, quality, and environmental management components.

[0156] The design management component is built upon the design, development, and control system, and consists of a project management system, a process management system, and a technical status management system. The engineering document management component provides document management, file distribution, meeting minutes management, and search services throughout the company. The engineering project management component covers all stages of a nuclear power project lifecycle, from market development and project contracting to design, procurement, construction, commissioning, and handover. The decision support component sets KPIs for engineering project management based on three dimensions: schedule, cost, and quality, covering the entire business operation of an EPCSO throughout the nuclear power project lifecycle. The comprehensive business management component includes several systems / platforms for business management, such as online bidding and procurement, supplier collaboration, PBA management, cost and quotation management, contract management, performance evaluation management, and model development management. The comprehensive safety, quality, and environmental management component includes the management and improvement of the entire process of safety, quality, and environmental inspection standards, inspection plans, supervision and inspection, performance evaluation, personnel qualifications, and information reporting within the scope of nuclear safety, occupational health and safety, quality, environment, security, counter-terrorism, and emergency response.

[0157] Co-design unit, including co-design component, overall design component, system design component, layout design component, civil design component, equipment design component, electrical design component, instrument control design component, technical and economic design component, radiation protection design component, reactor engineering design component, high-performance computing component, design data component.

[0158] Among them, the collaborative design component provides advanced digital collaborative design tools, methods and computing services for overall professional design work. The overall design component realizes the informatization of design input, centralized control, online sharing and distribution of design data, online collaborative editing of documents, and improves the collaboration level within the overall department and with other professionals. The system design component takes the system design management system as the core, combined with Flowmaster (thermal fluid system simulation analysis software), pipenet (pipe network fluid analysis software), apros and CAD (computer aided design) software, through the control of data and process, it realizes the design data collaboration of system professional and other upstream and downstream professionals to form a complete process system design tool. The layout design component takes the factory design management system as the core, integrates mechanical calculation, material management and drawing tools, and establishes an information-based design based on a unified three-dimensional design basic component library, three-dimensional design specifications and design process. The civil design component integrates the design data and necessary software of site, general layout, building and structure, and establishes an information-based design system based on a unified basic component library and standardized design process, providing digital collaborative design tools, methods and computing services for civil design related professionals. The equipment design component takes simulation data and three-dimensional equipment model management function as the core, driven by design tasks, integrates strength calculation tools, ANSYS (computer aided engineering software) and other nuclear power equipment design and calculation analysis software, realizes the integration of design tools, design process specification, data specification management and knowledge accumulation of equipment design and simulation, and realizes the digital design. The electrical design component is based on AutoCAD software, integrating digital design tools such as main wiring design, system design, drawing design and termination design, and establishing an electrical information-based design system based on a unified electrical equipment database, electrical design engineering database, electrical design specifications and design process, providing advanced digital collaborative design tools, methods and computing services for electrical primary and secondary professional design work. The instrument control design component is developed based on AutoCAD software, and cooperates with process, electrical and layout design, providing advanced digital collaborative design tools, methods and computing services for instrument control first and second level design work. The technical and economic design component effectively controls various technical and economic data, meets the measurement and pricing requirements of each design stage of technical and economic design, and has the functions of technical and economic data penetration, database sorting and analysis in each design stage and link. The radiation screen design component provides an integrated design platform for radiation screen design work, realizes rapid transmission and process saving of design data based on the smallest design unit, and finally provides design tools, knowledge pushing, design collaboration and other functions for designers.The stack work design component is based on a calculation simulation general integrated tool, integrates core calculation software and design process of the reactor core design and fuel design, centrally manages business process, data, knowledge and the like by establishing a unified working environment, realizes fast transmission and process saving of design data based on the design module component, and finally provides an integrated design platform with functions of design tool, knowledge pushing, design collaboration and the like for the design personnel. The high-performance calculation component has a calculation service capacity of 1000 billion times per second, adopts a task scheduling and visual monitoring mode, integrates large commercial calculation software, and effectively improves the design and simulation efficiency. The design data component is a design result data sharing, integration and release center, which ensures the consistency of data of each platform and realizes effective exchange of data among platforms.

[0159] The supply chain coordination unit includes a material management component, a supplier management component, a procurement management component, a quotation management component, a material receiving management component, a warehouse management component, a material issuing component, a contract execution component, a device construction management component, and a device supply chain information component.

[0160] The material management component system is connected with the design data center to generate a material list for signing a contract, placing an order and supplying goods. The supplier management component system manages all suppliers participating in the bidding business of China General Nuclear. The procurement management component system includes procurement of equipment and materials within the general contract scope. The quotation management component system realizes starting procurement after determining the procurement equipment and materials, and clearly defines the bidding mode to complete the whole process of contract bidding. The material receiving management component system realizes the management of receiving raw materials and equipment provided by the supplier and prefabricated products. The warehouse management component system mainly includes three businesses, namely, maintenance of materials during warehouse management, inventory checking, and recording the status of inventory materials. The material issuing component system mainly includes five businesses, namely, prefabrication / installation contractor technical department making material demand combined with design information and engineering plan, engineering company installation professionals auditing the rationality of the demand, prefabrication / installation contractor technical department making a material requisition slip combined with the demand after auditing and inventory information, prefabrication / installation contractor splitting the material requisition slip and taking materials from the warehouse, and warehouse administrator issuing materials. The contract execution component system realizes the whole process management of contract execution, including contract, payment, change, claim, confirmation, customs declaration, performance guarantee, and archiving. The device construction management component covers important aspects of quality supervision work and provides a platform for standardization of quality supervision work. The device supply chain information component includes device supplier evaluation, supplier qualification and capability assessment, supplier credit management, and decision support module.

[0161] The construction and manufacturing service unit includes a construction production management component, a construction quality process control component, a construction technology management component, a construction scheme planning component, a field personnel management component, a construction measurement payment management component, a construction virtual simulation component, a debugging management component, a commissioning debugging test component, a debugging test report and intelligent calculation component, and an integrated handover and production component.

[0162] The construction production management component establishes construction work packages of different professional and regional operation lists, automatically loads construction resources such as man-machine-material-method and environment into the work package when the work package is designed and issued, and interacts with the progress plan to dynamically adjust the field progress and plan. The construction quality process control component realizes quality control tracking management of the whole construction process. The construction technology management component includes design information management, drawing file management, technical change management, and completion file management. The construction scheme planning component prepares a crane station layout and site demand report as an interface file to provide input information for corridor design and progress plan preparation. The field personnel management component accurately masters the specific personnel situation of all types of contractor construction personnel and construction management personnel on the construction site to master the human input cost of the nuclear power construction site. The construction measurement payment management component realizes the on-site work of the contractor according to the construction contract and construction drawings, the contractor's application for progress payment by filling in the on-site completed quantities, the audit of the quantities and progress payment by the engineering company according to the actual progress, and the payment of the progress payment after the approval of the engineering company. The construction virtual simulation component uses virtual simulation technology, combines with the needs of nuclear power, develops key plant virtual roaming, provides immersive experience for users, and simulates construction progress and construction steps to improve construction efficiency. The debugging management component includes debugging safety management, debugging quality management, debugging environment management, debugging progress management, debugging cost management, debugging experience feedback management, equipment disassembly and repair, system modification, special maintenance, and tail item processing. The commissioning debugging test component includes main control room operation and special test work. The debugging test report and intelligent calculation component includes preparation and publication, handover file preparation, ticket preparation, tool and spare parts preparation, equipment state inspection, prerequisite confirmation, test implementation and data recording, unexpected event and change, debugging report preparation, test result analysis and evaluation, site recovery and handover, and tail item processing. The integrated handover and production component builds an integrated handover and production management intermediate database based on the existing system application, realizes unified query, interface, and interface service by planning handover and production business standard processes, legacy item standard data formats, and interface schemes.

[0163] The production operation service unit includes a device management component, a nuclear emergency decision-making command and management component, a nuclear power plant physical protection component, a DCS (Distributed Control System) system component, a multi-base technical support component, a production plan management component, a nuclear power plant overhaul management system component, and a group plant production operation management component.

[0164] Among them, the equipment management component provides a unified management means for various problems found in the operation of important equipment in nuclear power plants, and realizes the addition, tracking, upgrading, progress evaluation, closing, query, statistics, export and outlook reminder of equipment problems and their derivative problems, as well as hierarchical, integrated and electronic management. The nuclear emergency decision-making and management component integrates and utilizes various emergency data resources of nuclear power plants to realize data acquisition and monitoring, emergency level auxiliary judgment, accident state research and decision-making, and emergency action process. The nuclear power plant physical protection component is specially applied to the comprehensive security management software for the operation management of the nuclear power plant physical protection system. The DCS system component realizes the basic functions including nuclear power unit operation data acquisition, calculation, data transmission, monitoring, etc. through the sensor network and the central control system. The multi-base technical support component is specially used for the management and settlement of nuclear power plant contractor technical support work, and realizes the functions of multi-base technical support service demand application, task assignment, system authorization, task execution, work hour calculation, material borrowing, financial settlement, etc. The production plan management component realizes the functions of nuclear power plant production three-day rolling plan compilation, seven-day plan compilation, daily production milestone plan, work order management, work order statistics, high-risk statistics, etc. The nuclear power plant overhaul management system component includes nuclear power plant overhaul index management, overhaul task preparation, overhaul plan management, overhaul technical problem, overhaul safety management, overhaul quality management, overhaul contractor management, overhaul document management and overhaul change management modules. The group plant production and operation management component includes five modules of system procedures and reports, daily and overhaul, hidden danger investigation, major meetings and holidays, and special work of group plant weekly meeting, TEF daily meeting, TEF weekly meeting, special report, exchange and discussion.

[0165] The decommissioning service unit includes a decommissioning project management component, a decommissioning collaborative design component, a decommissioning impact analysis component, and a decommissioning process management component.

[0166] Among them, the decommissioning project management component is suitable for the decommissioning of facilities with radioactivity and the decommissioning engineering and demolition process of conventional facilities. The decommissioning collaborative design component includes radiation protection design, ventilation system design, process design and comprehensive report modules, and realizes the optimization of radiation protection dose analysis in the decommissioning construction stage. The decommissioning impact analysis component includes safety evaluation, three-dimensional radiation evaluation and visual decommissioning treatment impact analysis functions, which are used for decommissioning feasibility study, safety analysis and environmental impact assessment, and guide decommissioning design and construction. The decommissioning process management component includes the management of various technical methods and treatment processes in the decontamination, cutting and demolition processes, to ensure the improvement of decommissioning process quality.

[0167] In the embodiment, the micro-service center supports rapid access of various services, and realizes integration and unified management with existing nuclear power business components, and provides services in a standard form.

[0168] In one embodiment, as shown in Figure 3 The micro-service management platform includes a service interface management platform and an industrial micro-service center. The service interface management platform includes design, development, management, testing, release, monitoring, and opening. From the module, the service interface integration unit, the service testing unit, the gateway unit, the service monitoring unit, the service registration and configuration unit, and the service orchestration unit are obtained. The service interface management platform also includes a service interface management portal unit. The service interface management portal unit is mainly used for the service interface developers, third-party developers, and partners of the enterprise. The service interface management platform pools the computing, storage, and network resources through virtualization technology, provides meterable and elastic resource services to users, and builds service interfaces on this basis. The service interface management platform realizes efficient management of various complex service interfaces, sorts out the mutual calling and dependency relationship between the service interfaces, integrates, creates, tests, gateway configures, manages, monitors, registers, configures, and orchestrates the service interfaces, realizes micro-service agile delivery, and provides a comprehensive and convenient service environment for the industrial internet edge cloud collaborative system. The industrial micro-service center includes a research and development processing unit, an engineering and operation management unit, a collaborative design unit, a supply chain collaboration unit, a construction and manufacturing service unit, a production operation service unit, and a decommissioning service unit. The industrial micro-service center supports rapid access of various services, and realizes integration and unified management with existing nuclear power business components, and provides services in a standard form.

[0169] In one embodiment, as shown in Figure 4As shown, a principle schematic diagram of a service interface processing method is shown. Specifically, a service interface developer invokes each function provided by a service interface integration unit, a service orchestration unit, a service test unit and a service registration and configuration unit through a service interface management portal unit. The server can publish the service interface through a gateway unit, and a user can call the published service interface through the service interface management portal unit. The service interface can include at least one of a research and development processing interface, an engineering and operation processing interface, a collaborative design interface, a supply chain collaboration interface, a construction and manufacturing service interface, a production operation service interface and a decommissioning service interface, which belong to a micro service center. The service monitoring unit can monitor each service of the micro service center and collect heartbeat and log information.

[0170] It should be understood that, although each step in the flowchart in some embodiments of the present application is shown in sequence according to the arrow, these steps are not necessarily executed in sequence according to the arrow. Unless otherwise specified herein, the execution of these steps is not strictly limited in sequence, and these steps can be executed in other sequences. Moreover, at least part of the steps in the flowchart can include multiple steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution sequence of these steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least part of other steps or steps or stages in other steps.

[0171] In one embodiment, as shown in Figure 5 A service interface processing apparatus 500 is provided, comprising: an interface definition module 502, an interface orchestration module 504, an interface test module 506 and an interface publishing module 508, wherein:

[0172] The interface definition module 502 is configured to obtain service definition data specified in a service interface generation interface, and generate a corresponding service interface based on the service definition data.

[0173] The interface orchestration module 504 is configured to respond to an orchestration operation in a service orchestration interface, process a selected common interface and a service interface selected from the generated service interfaces, and generate a new service interface; the new service interface is used to call the selected service interface and the common interface.

[0174] The interface test module 506 is configured to perform automated testing on the generated service interface to obtain a service interface to be registered.

[0175] The interface publishing module 508 is configured to publish the registered service interface after registering the service interface to be registered to the micro service center.

[0176] In an embodiment, the service definition data comprises at least one of structured query language data, data source information, data processing model identification and data model identification; the interface definition module 502 is further configured to determine the data processing model and the data model specified in the service interface generation interface, and generate a first service interface; the first service interface is configured to process data obtained by the data processing model on the data model; determine the structured query language data and the data source specified in the service interface generation interface, and generate a second service interface; the second service interface is configured to perform structured query on the data source through the structured query language data.

[0177] In an embodiment, the service definition data comprises at least one of cross-platform service code and database stored procedure information; the interface definition module 502 is further configured to determine the database stored procedure information specified in the service interface generation interface, and generate a third service interface; the third service interface is configured to run the database stored procedure information based on the input parameter passed by the calling party and obtain the database return result; determine the cross-platform service code specified in the service interface generation interface, and generate a fourth service interface; the fourth service interface is configured to run the cross-platform service code and return the running result.

[0178] In an embodiment, the orchestration operation comprises an interface selection operation and an interface movement operation; the interface orchestration module is further configured to display a service orchestration interface; in response to the interface selection operation in the service orchestration interface, determine the selected public interface and the service interface selected from the generated service interface; in response to the interface movement operation for the selected service interface and the public interface, determine the running order between the selected service interface and the public interface; process the selected service interface, the public interface and the running order to generate a new service interface; the new service interface is configured to call the selected service interface and the public interface according to the running order.

[0179] In an embodiment, the interface test module is further configured to, in response to the configuration operation in the test interface, build an automated test environment for the service interface; in response to the test orchestration operation in the test interface, determine a test scenario for the service interface; use the test scenario to automatically test the service interface in the automated test environment to obtain the service interface to be registered.

[0180] In an embodiment, the interface publishing module is further configured to, after registering the service interface to be registered to the micro service center, publish the service interface to be published through the gateway unit, so that the calling party calls the published service interface; in the process of calling the published service interface by the calling party, at least one of access permission control, access routing control and security control is performed through the gateway unit.

[0181] In an embodiment, after the service interface to be registered is registered to the micro-service center to which the service interface belongs, and after the registered service interface is published, the service interface processing apparatus is further configured to monitor the running service interface through the service monitoring unit to obtain at least one of running performance data, call frequency statistical data, and call link topology graph.

[0182] The specific limitations of the service interface processing apparatus can be referred to the limitations of the service interface processing method described above, which will not be repeated here. Each module in the service interface processing apparatus can be realized by software, hardware, and combinations thereof, in whole or in part. Each module can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory in the computer device in software form, so as to be called and executed by the processor to perform the operations corresponding to each module.

[0183] In an embodiment, a computer device is provided, which can be a server, and the internal structure diagram thereof can be as shown in Figure 6 The computer device includes a processor, a memory, and a network interface connected through a system bus. The processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operating system and the computer program in the non-volatile storage medium to run. The database of the computer device is configured to store service interface processing data. The network interface of the computer device is configured to communicate with an external terminal through a network connection. The computer program is executed by the processor to implement a service interface processing method.

[0184] Those skilled in the art can understand that Figure 6 The structure shown in the figure is only a block diagram of part of the structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device can include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0185] In an embodiment, a computer device is also provided, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps in each method embodiment described above.

[0186] In an embodiment, a computer readable storage medium is provided, which stores a computer program. The computer program is executed by a processor to implement the steps in each method embodiment described above.

[0187] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in any non-volatile computer readable storage medium, and when the computer program is executed, the processes of the above-mentioned embodiments of the methods can be included. Any reference to memory, storage, database or other medium used in each embodiment provided by the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration but not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0188] Each technical feature of the above embodiments can be combined arbitrarily. In order to make the description simple, all possible combinations of each technical feature in the above embodiments are not described, but as long as the combination of the technical features does not exist, it should be considered as the scope of the present application.

[0189] The above embodiments only express several implementation manners of the present application, and the description is more specific and detailed, but it should not be understood as a limitation on the scope of the patent. It should be pointed out that for those skilled in the art, without departing from the concept of the present application, some modifications and improvements can be made, which are all within the protection scope of the present application. Therefore, the protection scope of the patent of the present application should be subject to the appended claims.

Claims

1. A service interface processing method, characterized in that, The method includes: Retrieve the service definition data specified in the service interface generation interface; Based on the service definition data, generate the corresponding service interface; In response to the orchestration operation in the service orchestration interface, the selected public interface and the service interface selected from the generated service interfaces are processed to generate a new service interface; the new service interface is used to call the selected service interface and the public interface. Automated testing is performed on the generated service interfaces to obtain the service interfaces to be registered; After registering the service interface to be registered with its respective microservice center, the registered service interface is published.

2. The method according to claim 1, characterized in that, The service definition data includes at least one of structured query language data, data source information, data processing model identifier, and data model identifier; the generation of the corresponding service interface based on the service definition data includes at least one of the following processes: The data processing model and data model specified in the service interface generation interface are determined, and a first service interface is generated; wherein, the first service interface is used to process the data obtained by the data model through the data processing model; Determine the structured query language data and data source specified in the service interface generation interface, and generate a second service interface; wherein, the second service interface is used to perform structured queries on the data source using the structured query language data.

3. The method according to claim 1, characterized in that, The service definition data includes at least one of cross-platform service code and database stored procedure information; the generation of the corresponding service interface based on the service definition data includes at least one of the following processes: Confirm the database stored procedure information specified on the service interface generation interface, and generate a third service interface; the third service interface is used to run the database stored procedure information based on the input parameters passed by the caller and obtain the database return result; Confirm the cross-platform service code specified on the service interface generation interface, and generate a fourth service interface; the fourth service interface is used to run the cross-platform service code and return the running result.

4. The method according to claim 1, characterized in that, The orchestration operation includes interface selection operation and interface movement operation; in response to the orchestration operation in the service orchestration interface, the selected public interface and the service interface selected from the generated service interface are processed to generate a new service interface. The new service interface is used to invoke the selected service interface, and the public interface includes: Display service orchestration interface; In response to the interface selection operation in the service orchestration interface, the selected public interface and the service interface selected from the generated service interfaces are determined. In response to an interface move operation for the selected service interface and the public interface, determine the execution order between the selected service interface and the public interface; The selected service interface, the public interface, and the execution order are processed to generate a new service interface; the new service interface is used to call the selected service interface and the public interface according to the execution order.

5. The method according to claim 1, characterized in that, The step of performing automated testing on the generated service interface to obtain the service interface to be registered includes: In response to configuration operations in the test interface, an automated test environment is built for the service interface; In response to the test orchestration operation in the test interface, determine the test scenario for the service interface; The service interface is automatedly tested using the test scenario in the automated testing environment to obtain the service interface to be registered.

6. The method according to claim 1, characterized in that, The step of publishing the registered service interface after registering it with the microservice center includes: After registering the service interface to be registered with the microservice center, the service interface to be published is published through the gateway unit so that the caller can call the published service interface. During the process of the caller invoking the published service interface, at least one of the following is performed through the gateway unit: access control, access routing control, and security control.

7. The method according to claim 1, characterized in that, After registering the service interface to be registered to its respective microservice center and publishing the registered service interface, the method further includes: The service monitoring unit monitors the running service interfaces to obtain at least one type of data, including running performance data, call count statistics, and call chain topology diagram.

8. The method according to claim 1, characterized in that, The service interfaces include at least one of the following: R&D processing interface, engineering and operation processing interface, collaborative design interface, supply chain collaboration interface, construction and manufacturing service interface, production operation service interface, and decommissioning service interface.

9. A service interface processing device, characterized in that, The device includes: The interface definition module is used to obtain the service definition data specified in the service interface generation interface; and generate the corresponding service interface based on the service definition data. The interface orchestration module is used to respond to orchestration operations in the service orchestration interface, process the selected public interface and the service interface selected from the generated service interfaces, and generate a new service interface; the new service interface is used to call the selected service interface and the public interface. The interface testing module is used to perform automated tests on the generated service interfaces to obtain the service interfaces to be registered. The interface publishing module is used to publish the registered service interface after it has been registered with the microservice center to which it belongs.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 8.

Images