CN114816591A - Service interface processing method and device, computer equipment and storage medium - Google Patents

Abstract

The present application relates to a service interface processing method, apparatus, computer equipment and storage medium. The method includes: acquiring service definition data specified in the service interface generating interface; generating a corresponding service interface based on the service definition data; The service interface selected in the service interface is processed to generate a new service interface; the new service interface is used to call the selected service interface and the public interface; perform automated testing on the generated service interface to obtain the pending registration. After registering the service interface to be registered in the microservice center to which it belongs, the registered service interface is published. Therefore, the service interface can be delivered agilely.

Description

Service interface processing method, apparatus, computer equipment and storage medium

technical field

The present application relates to the field of software technology, and in particular, to a service processing method, apparatus, computer equipment and storage medium.

Background technique

With the rapid development of digital transformation, the continuous expansion of the business of companies and organizations, the continuous increase in demand, and the continuous increase in the number of users, the traditional monolithic architecture has been unable to adapt to the rapid changes in applications in the cloud computing era, and the microservice architecture is considered to be the future construction. The direction of a new generation of distributed architecture applications makes it easy to upgrade and expand by decomposing applications into smaller service interfaces. Enterprises can assemble various products to provide personalized services externally and internally by calling a variety of different service interfaces.

However, due to the large number of service interfaces, the generation and release of service interfaces requires a lot of resources to complete, and cannot be delivered agilely. Therefore, efficiency needs to be improved to enable agile delivery.

SUMMARY OF THE INVENTION

Based on this, it is necessary to provide a service interface processing method, apparatus, computer equipment, storage medium and computer program product capable of agile delivery in response to the above technical problems.

In a first aspect, the present application provides a service interface processing method. The method includes:

Get the service definition data specified in the service interface generation interface;

Based on the service definition data, a corresponding service interface is generated;

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 invoke the selected service interface and the public interface;

Perform automated testing on the generated service interface to obtain the service interface to be registered;

After the service interface to be registered is registered in the microservice center to which it belongs, the registered service interface is published.

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 the corresponding service is generated based on the service definition data The interface includes at least one of the following processes:

Determine the data processing model and data model specified in the service interface generation interface, and generate a first service interface; wherein, the first service interface is used to perform data processing on the data obtained by the data model through the data processing model deal with;

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 use the structured query language data in the data source Structured query in .

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

Confirm the database stored process 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 process 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.

In one of the embodiments, the orchestration operation includes an interface selection operation and an interface move operation; and 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 performed. processing 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 an interface selection operation in the service orchestration interface, determining a selected public interface and a service interface selected from the generated service interfaces;

determining an order of operation between the selected service interface and the public interface in response to an interface move operation for the selected service interface and the public interface;

Processing 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 interface.

In one of the embodiments, performing automated testing on the generated service interface to obtain the service interface to be registered includes:

In response to the configuration operation in the test interface, constructing an automated test environment for the service interface;

determining a test scenario for the service interface in response to a test orchestration operation in the test interface;

The service interface is automatically tested by using the test scenario in the automated test environment to obtain the service interface to be registered.

In one embodiment, after the to-be-registered service interface is registered with the microservice center to which it belongs, publishing the registered service interface includes:

After the to-be-registered service interface is registered in the microservice center to which it belongs, the to-be-published service interface is published through the gateway unit, so that the caller invokes the published service interface;

During the process of invoking the published service interface by the caller, at least one of access authority control, access route control and security control is performed by the gateway unit.

In one of the embodiments, after the service interface to be registered is registered with the microservice center to which it belongs, and the registered service interface is published, the method further includes:

The running service interface is monitored by the service monitoring unit to obtain at least one type of data in the running performance data, the statistical data of the number of calls and the calling link topology map.

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 decommissioning service interface interface.

In a second aspect, the present application further provides a service interface processing apparatus. The device includes:

The interface definition module is used to obtain the service definition data specified in the service interface generation interface; based on the service definition data, the corresponding service interface is generated;

The interface orchestration module is used to process 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, and generate a new service interface; the new service interface is used to call all the selected service interface and the public interface;

an interface testing module, configured to perform automated testing on the generated service interface to obtain the service interface to be registered;

The interface publishing module is configured to publish the registered service interface after the service interface to be registered is registered in the microservice center to which it belongs.

In a third aspect, the present application also provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor executes the steps of the above-mentioned service interface processing method.

In a fourth aspect, the present application also provides a computer-readable storage medium. The computer-readable storage medium has a computer program stored thereon, and the computer program is executed by the processor to execute the steps of the above-mentioned service interface processing method.

In a fifth aspect, the present application also provides a computer program product. The computer program product includes a computer program, and the computer program is executed by a processor to execute the steps of the above-mentioned service interface processing method.

The above-mentioned service interface processing method, apparatus, computer equipment, storage medium and computer program product obtain the service definition data specified in the service interface generation interface; and generate the corresponding service interface based on the service definition data. In this way, the service interface can be generated through the operation of the interface, which improves the generation efficiency of the service interface. In the case where the service interface needs to be orchestrated, based on the orchestration operation in the service orchestration interface, determine at least one service interface and at least one public interface selected, and generate and run the at least one service interface and at least one public interface new service interface. In this way, multiple interfaces can be arranged through an interface arrangement operation to generate a new service interface, which improves the generation efficiency of the service interface. An automated test is performed on the service interface to obtain the service interface to be published, thereby improving the test efficiency of the service interface. The to-be-published service interface is published, so that the caller invokes the published service interface. In this way, users do not need to write relevant code for each function point of the service interface, but only need to operate the relevant interface, and can quickly define, arrange, test and publish the service interface, thus meeting the requirements for agile delivery of service interfaces. .

Description of drawings

1 is an application environment diagram of a service interface processing method in one embodiment;

2 is a schematic flowchart of a service interface processing method in one embodiment;

3 is a schematic diagram of the principle of a service interface processing method in one embodiment;

4 is a schematic diagram of the principle of a service interface processing method in one embodiment;

5 is a structural block diagram of an apparatus for processing a service interface in one embodiment;

FIG. 6 is a diagram of the internal structure of a computer device in one embodiment.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application more clearly understood, the present application will be described in further 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, but not to limit the present application.

The service interface processing method provided by this application can be applied to the application environment shown in FIG. 1 . The terminal 110 communicates with the server 120 through the network. The data storage system may store data that the server 120 needs to process. The data storage system can be integrated on the server 120, or it can be placed on the 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.

The terminal 110 may display service interface processing related interfaces such as a service interface generation interface and a service arrangement interface. The server 120 acquires the service definition data specified in the service interface generation interface, and generates a corresponding service interface based on the service definition data. In response to the orchestration operation in the service orchestration interface, the server 120 processes the selected public interface and the service interface selected from the generated service interfaces, and generates a new service interface; the new service interface is used to call the selected service interface and public interface. The server 120 performs automated testing on the generated service interface to obtain the service interface to be registered. After the server 120 registers the service interface to be registered in the microservice center to which it belongs, the server 120 publishes the registered service interface. The terminal 110 can access the published service interface.

In one embodiment, as shown in FIG. 2 , a service interface processing method is provided. In this embodiment, the method is applied to a server for illustration. It can be understood that the method can also be applied to a terminal, and can also be applied to It is used in a system including a terminal and a server, and is realized through the interaction between the terminal and the server. In this embodiment, the method includes the following steps:

S202: Acquire the service definition data specified in the service interface generation interface; generate a corresponding service interface based on the service definition data.

Among them, the service definition data is data for defining a service interface.

Specifically, the user performs service definition related operations on the service interface generation interface displayed on the terminal to specify service definition data. The server obtains the service definition data specified in the service interface generation interface, and generates a corresponding service interface based on the service definition data.

In one embodiment, step S202 is performed by the 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, and the like. The service interface integration unit can also support service simulation, and provide at least one function such as role management, view templates, resource files, and application configuration.

Specifically, the service interface integration unit supports the creation of service interfaces through data processing models. The server creates the entity model of the table by selecting the created data source, and creates the service interface through the entity model. Among them, the entity model is a data processing model that can carry table data and perform data processing on the table data, rather than an abstract model. The service interface integration unit can also support creating a service interface through a business model, creating a business model of a table by selecting an already created data source, and creating a service interface through a structured query language statement. Among them, the business model is related to the business and is implemented through multiple data processing models. The service interface integration unit can also support the creation of service interfaces through scripts, and supports through SQL (Structured Query Language, structured query language), Java (an object-oriented programming language), JavaScript (a lightweight with function priority, Interpreted or just-in-time compiled programming language), Python (a programming language), Shell (a command language) and other script codes create service interfaces. The service interface integration unit can also support Java Bean (a reusable component written in JAVA language) to create service interface, and publish key-value pair parameter service interface, path parameter service interface, JSON (JavaScript Object Notation, JS) by using platform annotations Object notation) to pass parameters to the service interface to realize the creation of the service interface. The service interface integration unit can also support the creation of service interfaces through database stored procedures.

Specifically, the service interface integration unit may also support service simulation. Among them, service simulation mainly includes simulation data management, simulation data generator and data simulation rules. Simulated data is the unified management of all service interface data that needs to be simulated, and can be used in routing configuration and service interface registration. Through the simulation data generator and data simulation rules, the server can output the simulation data to the calling end, thereby realizing the service interface data simulation function.

Specifically, the service interface integration unit can also support role management, through which new roles can be added and users, roles and permissions can be associated. Through role management, users can manage service interfaces belonging to users.

Specifically, the service interface integration unit can also provide a view template function, and the service interface integration development platform provides a view template technology, and can develop a page service interface mixed with the front end. The service interface integration unit can view the resource file of the service interface. The service interface integration unit provides application configuration functions to make development more convenient, faster and easier to manage.

S204, in response to the orchestration operation in the service orchestration interface, process the selected public interface and the 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 public interface.

The public interface is a public interface that provides basic functions and can be called by multiple service interfaces. Common interfaces can be process basic components, script execution components, message queue components, process time components, process monitoring, publishing service interface, orchestration service interface, data conversion and data mapping configuration, rule management, application configuration, service interface orchestration application, public interface At least one public interface among component libraries and platform monitoring functions.

Specifically, in response to the orchestration operation in the service orchestration interface, the server processes the selected public interface and the service interface selected from the generated service interfaces to generate a new service interface. Among them, the new service interface is used to call the selected service interface and the public interface.

In one embodiment, the server performs step S204 through the service interface orchestration unit. The basic process components of the service interface orchestration unit are used for process management and support calling service interfaces provided by other systems, which mainly include Restful (a design style and development method of network applications, based on HTTP (Hypertext Transfer Protocol), Can use XML (Extensible Markup Language) format definition or JSON format definition) service interface, WebService (a platform-independent, low-coupling, self-contained, programmable web-based application, can use open XML (standard) A subset of the Common Markup Language) standard to describe, publish, discover, coordinate and configure these applications for developing distributed interoperable applications), Dubbo (an open source distributed services framework), TCP/IP ( At least one of Transmission Control Protocol/Internet Protocol) message, variable setting, manual approval, asynchronous callback, asynchronous queue, gateway node, sub-process, data merge, data split, file upload, file download, etc. kinds of components.

Among them, the Restful service interface is mainly used to call the service interface of the Rest (Representational State Transfer, presentation layer state transition) type, and the main input and output are JSON data format. The WebService node is mainly used to call the interface type that has been published as WebService in the business system. Data, the Dubbo interface is mainly used to call the RPC (Remote Procedure Call) interface published by Dubbo, so as to realize the shuffling and invocation with the Restful interface.

Manual approval supports manual approval data flow. Only the data flow that has passed manual approval can enter subsequent execution nodes. At the same time, it provides service interface approval interface to connect with various systems.

Sub-process, the existing and enabled service choreography in the system can be used as a sub-process choreography to be nested in other service choreography.

Asynchronous execution capability of services. Through distributed deployment, the orchestration server can respond to any large-traffic HTTP service interface requests. The orchestration server first persists the request traffic to MongoDB (a database based on distributed file storage) and then coordinates through distributed scheduling. The choreographer is used to schedule the process executor to schedule the orchestration process.

Gateway nodes implement multi-branch aggregation through aggregation-type gateway nodes. Subsequent nodes are executed only after all branches are executed and reach the aggregation gateway. Therefore, the gateway node must have an aggregation gateway node for branch aggregation.

The script execution component supports JavaBean.Java rules, SQL, WebService, Dubbo, MQ (message queue), Python, Shell and other types of services for mixing and can automatically convert data formats between multiple protocols. JSON data format can It can automatically convert the XML format data of the next service interface node, and at the same time, through the shuffling mode of Java code, it can support the reorganization and integration of any business logic and service interface, and can solve the arbitrarily complex business process orchestration logic of CGN.

The message queue components mainly include Kafka (a high-throughput distributed publish-subscribe messaging system) messages, RabbitMQ (open source message broker software that implements advanced message queuing protocols) messages, and Mqtt (a message queuing transmission protocol that uses subscription, Publishing mechanism, subscribers only receive data that they have subscribed to, and do not receive non-subscribed data) messages, at least one of JMS (Java Message Service, Java Message Service) messages.

The process event component mainly includes at least one of debug logs, self-increment settings, timers, WeChat messages, DingTalk messages, sending emails, description text, start nodes, end nodes, etc. The debug log supports viewing the debug log generated when the process is in the debug state.

The process monitoring content mainly includes at least one of the pending approval process, the pending compensation process, the compensation failure process, the node to be compensated, all compensation nodes, the asynchronous waiting queue, the unfinished process, and the completed process. Process running statistics You can view the total running times, success times, failure times, and compensation times of the process. Click Total Runs to open a process record for all runs. The node to be compensated can view the list of all processes that need to be compensated positively, and if the compensation has been successful, it will be automatically deleted from this list. An unfinished node supports a process that is running, see a running process in an unfinished process. If you want to force the end of the process, you can force the end of the process. Ended processes support querying all processes that have been run and ended.

Further, the orchestrated process can be republished as a new service interface service, so that each time the service interface service is called, the process will be executed and the execution result of the process will be output to the calling end. Service interface orchestration can implement operations to add, modify, delete, and run service interfaces. Data transformation and data mapping configuration supports configuration of three types of data mappings: fixed value, reference value and script. Through them, the service orchestration interface, the assembly of the input parameters of the request interface (request interface) and the processing of the returned results can be completed. Data conversion includes result data clipping, field name mapping, field value conversion, data cleaning rules, XML to JSON, format conversion templates, mapping configuration templates, etc. The fixed value is mainly used for scenarios that require hard coding, and the reference value is mainly used to reference data between steps or from input. Script supports configuring scripts for fields, and the return result of the field is used as the value of the field. The asterisk wildcard can accept a reference value of the return object type, and the fields in the return object will be merged into the target object.

The rule management supports the rule code executed in the event node in the process choreography for unified management and publication here, and the rules can be added, modified, deleted and other operations.

Application configuration mainly includes public variable configuration, which is used to configure some public parameters and reference them in nodes or codes.

Process classification implements classification of orchestration processes and classification of management rules. Manage the categories in the rules, and you can add, delete, and modify categories.

The public component library includes at least one of an authentication component, an authentication component, a traffic control component, a cache component, a service log component, and a log component. The authentication component includes at least one authentication among Basic authentication and standard Token authentication.

Further, the authentication components include Basic authentication (basic authentication) and standard Token (token) authentication.

Basic authentication, each time the client accesses the service interface, the ID is included in the HTTP request header. After receiving the request, the gateway obtains the corresponding application ID and password from the HTTP header and compares them with the values stored in the local database. If successful, continue to the next implement.

For standard token authentication, first access the authentication interface provided by the gateway to obtain the token, and then bring the token in the request header to access the service interface.

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

The traffic control component limits the calling frequency of the service interface to avoid the crash of the service interface service provider due to excessive concurrency.

Cache component This component is used to cache the data returned by the back-end service interface. If the cache gateway is enabled on the service interface, it will first try to obtain data from the cache. If the data expires or does not hit the cache, it will call the back-end service to query the data.

The service routing component forwards the request of the client application received by the gateway to the back-end service provider, and supports protocol conversion, load balancing, etc. Currently, the platform supports Restful and Webservice service registration and exposure, and other types of protocols can be implemented through custom routing components.

The log component is used to record the access log of the service interface, including the number of calls per minute, average response time, total traffic, correct rate, etc.; all reports displayed in the monitoring center are generated based on the data collected by this component. When the interface is created, the system will bind this component by default, and users can also choose not to collect monitoring data.

Service interface service orchestration monitoring mainly includes management platform logs, orchestrated service interfaces, process operation statistics, process scheduling statistics, cluster servers, registry service instances, memory thread monitoring, etc.

S206, perform automated testing on the generated service interface to obtain the service interface to be registered.

Specifically, the server performs an automated test on the generated service interface, outputs an automated test report, and further obtains the service interface to be registered.

In one embodiment, executing automated tests is implemented based on service test units. The service is used to build an automated test environment for service interfaces based on the web interface. At the same time, it can arrange service interfaces to realize complex test scenarios and output test reports, which greatly improves the efficiency of service interface testing.

Further, the service interface integration unit supports custom test cases, and can set service addresses and input parameters for service interfaces in related business fields, arrange them according to certain business logic, add test plans, and then perform automated testing. According to the test of the service interface, the result is asserted using the grammar, and different business logic is executed according to different assertion results, which can complete the complex service interface test scenario.

S208, after the service interface to be registered is registered in the microservice center to which it belongs, the registered service interface is published.

Specifically, the server registers the service interface to be registered with the microservice center to which it belongs, and publishes the registered service interface, so that the caller can call the published service interface.

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

Further, the service registry is a custom registry that provides a complete solution for the micro-service framework. The service interface gateway and configuration center maintain close communication with the service registry. The service interface gateway will look up all available server lists from the registry according to the instance name and use different load balancing algorithms for distribution. All microservices will report the status information and performance data of the application to the registry through heartbeats.

The service registry includes: cluster server management, online service instance management, and offline service instance management. Cluster service management supports multiple registration center servers for clustering. In the web interface, the cluster servers of all service registration and discovery centers can be managed uniformly and data consistency can be highly guaranteed. Online service instance management supports the management of currently valid servers, and supports manual adjustment of the performance parameter weights of each server, as well as manual direct registration of third-party server instances. Service instance management offline In a service instance, the service instance data will be persisted to the database and will not be lost due to server restarts.

The positioning of the service configuration center is a configuration center solution for enterprise distributed deployment architecture. It is fully Web-based configuration, easy to use, non-intrusive, and does not need to modify SpringBoot (an open source framework) annotations and any code. The platform automatically takes over Configuration, including configuration center home page, all configuration list, to-be-released configuration, public configuration, edit configuration, change log, configuration snapshot, environment management, application management, etc.

The service configuration center includes: configuration management, environment management, and application management. Configuration management supports operations such as modifying, publishing, and deleting configurations. After configuration values are modified, they are always in the unpublished state. They can only take effect after they are actively published. A historical version relationship will be formed, and you can roll back to any version of the configuration value at any time. Environment management has a custom environment management function, and users can define multiple configuration environments according to the actual development and online situation. Application management can be defined as a micro-application or a business system. When an application is upgraded from 1.0 to 2.0, it is only necessary to build a 2.0 application configuration 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 Use the latest configuration of 2.0.

In the above-mentioned service interface processing method, the corresponding service interface is generated based on the service definition data by acquiring the service definition data specified in the service interface generation interface. In this way, the service interface can be generated through the operation of the interface, which improves the generation efficiency of the service interface. In the case where the service interface needs to be orchestrated, based on the orchestration operation in the service orchestration interface, determine the selected at least one service interface and at least one public interface, and generate a new service running the at least one service interface and the at least one public interface interface. In this way, multiple interfaces can be arranged through an interface arrangement operation to generate a new service interface, which improves the generation efficiency of the service interface. The automated test is performed on the service interface to obtain the service interface to be published, thereby improving the test efficiency of the service interface. Publish the service interface to be published, so that the caller can call the published service interface. In this way, users do not need to write relevant code for each function point of the service interface, but only need to operate the relevant interface, and can quickly define, arrange, test and publish the service interface, thus meeting the requirements for agile delivery of service interfaces. .

In one embodiment, the service definition data includes at least one of structured query language data, data source information, data processing model identifiers, and data model identifiers; based on the service definition data, generating a corresponding service interface includes at least one of the following processes : determine the data processing model and data model specified in the service interface generation interface, and generate a first service interface; wherein, the first service interface is used to process the data obtained by the data model through the data processing model; The structured query language data and data source specified in the interface generate 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.

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

In one embodiment, the server can select the service interface type, name the data processing model name, refer to the unique identifier of the data model, read the database table by associating the database, specify the primary key identifier of the database table, and bind the data processing model to the database table to create a service interface through the data processing model.

In one embodiment, the server can also select the service interface type, name the names of multiple data processing models, refer to the unique identifier of the data model, and determine the database table and database primary key identifier by connecting to the data source and using SQL statements, thereby realizing the business The model creates the service interface.

In one embodiment, the server can also connect to a database, select a data model (including a data model, an entity model, and a business model), write a script through code, and select an execution mode according to the data returned by the SQL statement to create a service interface.

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

In one embodiment, the service definition data includes at least one of cross-platform service code and database stored procedure information; based on the service definition data, generating a corresponding service interface includes at least one of the following processes: confirming that the service interface generation interface specifies The database stored procedure information is generated, and the third service interface is generated; 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 , generate a fourth service interface; the fourth service interface is used to run the cross-platform service code and return the running result.

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 the 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 the fourth service interface. Among them, the fourth service interface is used to run the cross-platform service code and return the running result.

In one embodiment, the cross-platform service code may be Java code. Specifically, the server can customize the name of the Bean (which describes Java's software component model), and register the Java Bean through the Rest service (a Web service architecture whose goal is to create a distributed system with good scalability), and then By writing Java code. Among them, there are three ways to write Java code, one is to write directly, the other is to read code from a local project or other paths, and the other is to write through template code, and finally create a service interface through Java Bean.

In one embodiment, the server may select a data source, then generate a stored procedure ID by loading the stored procedure information in the database, and automatically import parameters into and out of the stored procedure to implement a new data storage procedure, and finally expose the stored procedure ID. Go out URL (Uniform Resource Locator, Uniform Resource Locator), realize the creation of service interface through data storage process information.

In this implementation, the service supports the creation of service interfaces through data storage process information, and the creation of service interfaces through cross-platform service codes, thereby improving the diversity of service interface creation.

In one embodiment, the orchestration operation includes an interface selection operation and an interface move 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 interfaces are processed to generate a new Service interface; the new service interface is used for invoking the selected service interface and the public interface including: showing the service orchestration interface; in response to the interface selection operation in the service orchestration interface, determining the selected public interface and selecting from the generated service interface In response to the interface move 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, and generate a new Service interface; the new service interface is used to call the selected service interface and the public interface in the running order.

Specifically, the orchestration operation includes an interface selection operation and an interface move operation. The server can present the service orchestration interface. The server determines the selected public interface and the service interface selected from the generated service interfaces in response to the interface selection operation in the service orchestration interface. In response to the interface move 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, 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.

In this embodiment, by selecting and moving the service interface and the public interface, the relevant running order is obtained, so as to obtain a new service interface that runs the service interface and the public interface according to the running order, thereby simplifying the generation process of the service interface, It simplifies the operation visualization to provide the generation efficiency of the service interface.

In one embodiment, performing an automated test on the generated service interface to obtain the service interface to be registered includes: in response to a configuration operation in the test interface, constructing an automated test environment for the service interface; in response to a configuration operation in the test interface; Test the orchestration operation to determine the test scenario for the service interface; use the test scenario to perform automated testing on the service interface in the automated test environment to obtain the service interface to be registered.

Specifically, the server constructs an automated test environment for the service interface in response to the configuration operation in the test interface. The server determines a test scenario for the service interface in response to the test orchestration operation in the test interface. The server performs automated testing on the service interface using the test scenario in the automated testing environment, so as to obtain the service interface to be registered.

In this embodiment, by operating on the interface, an automated test environment and a test scenario are constructed to perform automated testing on the service interface, thereby reducing the testing cost of the service interface and improving the efficiency of generating the service interface.

In one embodiment, after registering the service interface to be registered in the affiliated microservice center, publishing the registered service interface includes: after registering the service interface to be registered in the affiliated microservice center, through the gateway The unit publishes the service interface to be published, so that the caller calls the published service interface; in the process of the caller calling the published service interface, at least one of access authority control, access routing control and security control is performed through the gateway unit. a treatment.

Specifically, the server may publish the service interface to be published through the gateway unit after registering the service interface to be registered in the microservice center to which it belongs, so that the caller can call the published service interface. During the process of invoking the published service interface by the caller, the server performs at least one of access authority control, access route control and security control through the gateway unit.

Specifically, the gateway unit, as the unified entrance and exit of all business system integration service interfaces, provides at least one core function for all business system service interfaces, such as centralized authentication, error warning, data encryption and decryption, protocol conversion, security protection, and log auditing. . The gateway unit is a distributed deployment architecture, and supports the expansion of custom components and multi-tenant capabilities. It can realize service interface registration, plug-in configuration, service interface auditing and monitoring of service interface gateways by different teams and developers at the same time.

Further, the gateway unit supports service interface registration, which mainly registers and forwards the service interfaces of the back-end service individually, and can configure information such as mapping parameters and addresses, and at the same time, it can convert Rest into a webservice service interface.

The gateway unit supports service interface routing configuration. By configuring certain forwarding rules, it mainly calculates an address matching the back-end server according to the url path, and then forwards all http requests requesting this URL to the back-end server in batches.

The gateway unit supports gateway configuration management, including three aspects: back-end service management, routing classification management, and global variable configuration:

Back-end service management, customer developers can develop different routing conversion components according to the type of back-end service interface, and type them into Jar (Java Archive, English: Java Archive, is a software package file) format package according to the agreed format. The center is ready to use, and the gateway provides Rest-style service routing by default;

Route classification management, create a new route classification, or create a route under an existing route classification. It is recommended to create a corresponding route classification according to the needs of the business system;

Global variable configuration, modify the host address of the backend service interface by referencing the gateway variable in the backend service interface path.

The gateway unit supports data management, including three aspects: analog data management, data conversion rules, and data caching rules:

Simulation data is the unified management of all service interface data that needs to be simulated, which can be used in routing configuration and service interface registration;

Add a new conversion rule, add a header to the registered service interface through the script, modify the body parameter of the request, or trim the returned body data of the registered service interface through the script to add or reduce fields;

For service interfaces with query types and infrequent data changes, appropriate cache settings can effectively reduce the pressure on back-end services; administrators can configure whether to cache updated policies based on the characteristics of the service interface services.

Through client authentication, call permission configuration, data encryption configuration, IP whitelist, blacklist mechanism, secondary development, expandable customized security functions, and current limiting rule configuration, the security of the service interface is protected.

The gateway unit can realize timeout warning, error code warning, rate warning, business warning, etc. through warning settings.

The gateway unit supports gateway monitoring, including management platform logs, gateway topology map, server link monitoring, gateway cluster server, real-time request service interface monitoring, Hystrix (a fault-tolerant component that implements a timeout mechanism and circuit breaker mode) fuse monitoring, and registry services. examples, etc.

The gateway unit is a distributed deployment architecture and supports custom component expansion.

The gateway unit supports viewing the service interface release history (such as version, release description, release time, and release environment), and supports rollback to any historical version of the service interface, so as to meet the requirements of business grayscale release, version upgrade, and rollback.

The gateway unit supports calling different backend services in different environments by creating environment variables to implement the same service interface.

The gateway unit supports the use of the unified identity authentication service to manage the authority of the gateway service of the service interface it owns.

The gateway unit supports the creation of a VPC (a cloud computing service) channel to access resources in the VPC environment, and exposes service interfaces to backend services deployed in the VPC. At the same time, the VPC channel has the function of load balancing, so as to realize the load balancing of back-end services.

The gateway unit supports a signature key, which is used by the back-end service to verify the identity of the service interface gateway, and ensures the security of the back-end service when the gateway unit requests the back-end service.

The gateway unit supports intelligent identification of service interfaces, including automatic identification of Restful WebService, automatic registration and one-click publishing, and intelligent identification of service interface parameters.

In this implementation, at least one of access authority control, access routing control and security control is performed by the gateway unit, thereby improving the standardization, security and effectiveness of the access to the service interface.

In one embodiment, after the service interface to be registered is registered in the microservice center to which it belongs, and after the registered service interface is published, the method further includes: monitoring the running service interface through a service monitoring unit, At least one kind of data in the running performance data, the statistical data of the number of calls and the call link topology map is obtained.

Specifically, after the service interface to be registered is registered in the microservice center to which it belongs, and the registered service interface is published, the server monitors the running service interface through the service monitoring unit, and obtains running performance data, calls At least one kind of data in the number of times statistical data and the invocation link topology map.

Specifically, the service monitoring unit is a real-time monitoring center for microservices. Through the monitoring center, the operating status and performance data of service interfaces can be understood and analyzed in real time, and at the same time, the unified monitoring center of microservices can collect the running performance data of all microservice instances in real time. , all microservice instances aggregate monitoring data through heartbeats or logs, and the monitoring center conducts analysis and statistics through a unified monitoring chart or panel. 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 operation log.

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 operation log.

Through the Rest service, you can open the operation status list of all service interface services, including service interface real-time request monitoring, service interface real-time operation data, service interface execution exception monitoring, non-HTTP 200 status code requests, etc.

Through the statistical analysis of service interface calls, you can view the number of daily calls of service interfaces, the number of calls and performance of service interfaces, the average performance distribution of service interfaces, the top statistics of application calls, the top statistics of user calls, the distribution statistics of service interface status codes, and each cluster server. Information such as the number of calls, the list of invalid or duplicated service interfaces, etc.

Through application server monitoring, cluster server monitoring, local service instance cache, memory and thread monitoring, network connectivity monitoring, etc.

Through cache and container monitoring, monitor JavaBean objects like containers, incorrectly instantiated beans, SpringBean (an object instantiated, assembled and managed by the Spring Inversion of Control container) monitoring, list of loaded Jar packages, all caches of the platform, and Bean instances Cache, Bean configuration cache, service interface configuration cache, etc.

Through the service monitoring unit, the invocation of all service interfaces is automatically collected and a topology diagram of the invocation link is formed, so as to track service instances by user, track service interfaces by user, view service interface dependencies, track by service instances, and global service dependencies. Figure, trace by trace mark.

Call the inventory application service interface through the service interface asynchronous queue to send the notification message, put the operation into the message queue and gradually consume it. After the previous logic is completed, the service interface of another application is called back to notify the result.

Through the system operation log, you can manage the platform log, service interface call log, system operation log, search service interface log, user login log, log library management, system recycle bin, etc. The log storage method supports sub-database and sub-table for storage and can regularly clean up unnecessary log data. It can record detailed data of all requests and responders to facilitate auditing of the invocation. Various charts are supported to analyze logs and obtain problem solutions.

In this embodiment, the service interface is monitored by the service monitoring unit to obtain at least one type of data in the operation performance data, the statistical data of the number of calls and the call link topology diagram, so that the service interface can be further optimized.

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 decommissioning service interface.

Specifically, the R&D processing interface, the engineering and operation processing interface, the collaborative design interface, the supply chain collaboration interface, the construction and installation and manufacturing service interface, the production operation service interface and the decommissioning service interface are the R&D processing unit, the engineering and operation management unit, the collaborative design Interfaces provided by units, supply chain collaboration units, construction and manufacturing service units, production operation service units, and decommissioning service units. These units are used for the integration and unified management of various microservice components of the nuclear power business. Formed a total of 7 categories and 62 industrial micro-service components including R&D processing, engineering and operation management, collaborative design, supply chain collaboration, construction and manufacturing services, production and operation services, and decommissioning services, and unified externally in a standard form Provide services.

R&D processing unit, including R&D project management component, R&D expenditure management component, R&D achievement management component, collaborative R&D management component, R&D review management component, R&D knowledge management component, R&D performance management component, achievement transformation management component, system and standard management components, R&D decision analysis components.

Among them, the R&D project management component realizes the full life cycle management of model R&D projects, which can effectively control the application and approval, progress, funding, quality, documents, etc. of model R&D projects. R&D expenditure management component, accurate budget, expenditure management and control, and quantified cost, realize the pre-planning, in-process control, and post-event statistical management mode of the use of model R&D funds. The R&D result management component realizes the management functions of reporting, confirming, and tracking the model R&D results. The collaborative R&D management component provides model R&D management tools for project leaders, partners and model R&D teams through real-time project planning and project task execution tracking management to achieve clear management of project tasks. The R&D evaluation management component can be applied to the evaluation of innovative ideas solicitation, project approval, project acceptance evaluation, and project stage evaluation. It is a special evaluation system for model R&D business. The R&D knowledge management component realizes the knowledge sharing of model R&D units, solidifies the knowledge achievements of model R&D personnel, improves the reuse rate of knowledge, and helps model R&D units to form an automated knowledge base construction system. The R&D performance management component realizes the performance evaluation management of model R&D departments, projects, and personnel, and can dynamically set assessment indicators and rules. The achievement transformation management component realizes the management functions of model R&D achievement declaration, confirmation and tracking. System and Standard Management Components System and standards mainly include enterprise standard system management, standard implementation and supervision management, enterprise standard formulation management, and external standard formulation management. The research and development decision analysis component provides model research and development information retrieval statistics for enterprise leaders, expert teams, and leaders of various model research and development departments, so that users can grasp the model research and development capabilities of model research and development units at any time.

Project operation management unit, including design management component, project document management component, engineering project management component, decision support component, comprehensive operation management component, and comprehensive management component of safety, quality and environment.

Among them, the design management component is built on the basis of the design development and control system, and consists of the project management system, the process management system and the technical status management system. The Engineering Document Management component provides document management, file distribution, meeting minutes management and search services across the company. The engineering project management component covers the whole-cycle stage activities of nuclear power engineering projects from market development, project contracting to design, procurement, construction, commissioning, and handover. The KPI setting of decision support component engineering project management starts from the three dimensions of progress, cost and quality, and covers the business operation of EPCSO throughout the entire nuclear power project cycle. The comprehensive operation management component includes several systems/platforms for operation management such as online bidding and procurement, supplier collaboration, PBA management, cost and quotation management, contract management, assessment management, and model R&D management. The comprehensive management component of safety, quality and environment includes the whole process of safety, quality and environment inspection standards, inspection plans, supervision and inspection, assessment scores, personnel qualifications, and information reports within the scope of nuclear safety, occupational health and safety, quality, environment, security, anti-terrorism and emergency response. management and improvement.

Collaborative design unit, including collaborative design components, overall design components, system design components, layout design components, civil engineering design components, equipment design components, electrical design components, instrument control design components, technical design components, radiation screen design components, stacking engineering components Design Component, High Performance Computing Component, Design Data Component.

Among them, the collaborative design component provides advanced digital collaborative design tools, methods and computing services for all professional design work. The overall design component realizes the informationization of design input, the centralized control, online sharing and distribution of design data, and the online collaborative editing of documents, improving the level of collaboration within the overall institute and with other majors. The system design component takes the system design management system as the core, and is combined with Flowmaster (thermal fluid system simulation analysis software), pipenet (pipenet (pipe network fluid analysis software), apros and CAD (computer-aided design) and other software, through the data and process analysis software. It realizes the coordination of design data within the system major and other upstream and downstream majors to form a complete process system design tool. The layout design component takes the factory design management system as the core, integrates tools such as mechanical calculation, material management and drawing, and establishes a set of information design based on the unified 3D design basic component library, 3D design specification and design process. The civil engineering design component integrates professional design data and necessary software such as plant site, general drawing, building and structure, and provides digital collaborative design for civil engineering design related majors through an information-based design system based on a unified basic component library and standardized design process. Tools, methods and computing services. The equipment design component takes the simulation data and 3D equipment model management functions as the core, and is driven by the design task. Digital design integrating process specification, data specification management and equipment design and simulation of knowledge accumulation. Based on AutoCAD software, the electrical design components integrate digital design tools such as main wiring design, system design, schematic design and termination design. Through a unified basic database of electrical equipment, electrical design engineering database, electrical design specifications and design processes Based on a set of electrical information design system, it provides advanced digital collaborative design tools, methods and computing services for electrical primary, secondary and other professional design work. The I&C design components are developed on the basis of AutoCAD software. Now, in collaboration with process, electrical and layout design, advanced digital collaborative design tools, methods and calculation services are provided for the design work of the I&C first-level and second-level parts. The technical and economic design component effectively manages and controls various types of technical and economic data, meets the measurement and pricing requirements of each design stage of the technology and economics, and has business functions such as the connection of technical and economic data at each design stage and each link, and the arrangement and analysis of the database. The spoke screen design component provides an integrated design platform for the spoke screen design work, realizes the rapid transfer of design data and process preservation based on the smallest design unit, and finally provides designers with functions such as set design tools, knowledge push, and design collaboration. The reactor design component is based on the general integrated tool for calculation and simulation, and integrates the core calculation software and design process of core design and fuel design. By establishing a unified working environment, it can centrally manage business processes, data, knowledge, etc. The design data of components is quickly transmitted and the process is saved, and finally provides designers with an integrated design platform integrating design tools, knowledge push, design collaboration and other functions. The computing service capability of high-performance computing components reaches one trillion times per second. It adopts task scheduling and visual monitoring mode, and integrates large-scale commercial computing software to effectively improve design and simulation efficiency. Design data components Design results data sharing, integration, and publishing centers to ensure data consistency across platforms and achieve effective data exchange between platforms.

Supply chain collaboration unit, including material management component, supplier management component, procurement management component, inquiry management component, material receiving management component, warehouse management component, material distribution component, contract execution component, equipment construction management component, equipment supply chain information components.

Among them, the material management component system is connected with the design data center, and the material list is automatically generated, which is used for purchasing, signing contracts, placing orders, and supplying. The supplier management component system manages the management of all suppliers participating in the bidding business of CGNPC. The procurement management component system includes the procurement of equipment and materials within the scope of the general contract. The inquiry management component system realizes that the procurement of equipment and materials is determined and the procurement is started, and the bidding method is specified to complete the whole process of contract bidding. The material receiving management component system realizes the receiving management of raw materials, equipment, and prefabricated products supplied by A. The warehouse management component system mainly includes three kinds of business, one is the maintenance of materials during warehouse management, the other is inventory inventory, and the third is to record the status of inventory materials truthfully. The material distribution component system mainly includes five kinds of business, one is the prefabrication/installation contractor technical department to make material requirements in combination with design information and engineering plans, the second is the rationality of the requirements reviewed by the installation professionals of the engineering company, and the third is the prefabrication/installation contractor technology The department prepares the material requisition list based on the material demand and inventory information after review. Fourth, the prefabrication/installation contractor splits the material requisition list and collects materials from the warehouse. Fifth, the warehouse administrator issues the materials. The contract execution component system realizes the whole process management of contract execution including contract, payment, change, claim, confirmation, customs declaration, letter of guarantee and filing. The equipment construction management component covers all important aspects of quality supervision, and provides a platform for the standardization of quality supervision. The equipment supply chain information component includes equipment supplier evaluation, supplier qualification assessment, supplier credit management, and decision support modules.

Construction, installation and manufacturing service units, including construction production management components, construction quality process control components, construction technology management components, construction plan planning components, on-site personnel management components, construction measurement and payment management components, construction virtual simulation components, commissioning management components, joint commissioning Commissioning test components, commissioning test reports and intelligent computing components, and handover and production integration components.

Among them, the construction production management component, the system establishes the construction work package of the work list of different majors and different areas. When the work package is designed and issued, the construction resources such as the human-machine material law ring and other construction resources are automatically loaded into the work package to interact with the progress plan. On-site progress and plans are dynamically adjusted. The construction quality process control component system realizes the quality control and tracking management of the whole construction process. The construction technology management component system includes design information management, drawing document management, technical change management, and completion document management. The construction plan planning component prepares the crane station layout and site demand report, and provides input information for the corridor design, schedule preparation, etc. as an interface document. The on-site personnel management component integrates various contractor construction personnel and construction management personnel to accurately grasp the specific personnel conditions of the construction site, so as to control the labor input cost of the nuclear power construction site. The construction metering payment management component realizes that the contractor carries out on-site work according to the construction and installation contract and construction drawings; the contractor fills in the completed work quantity on site and applies for the progress payment; the engineering company reviews the project quantity and the progress payment according to the actual progress; Progress payment. The construction virtual simulation component utilizes virtual simulation technology and combines nuclear power requirements to develop a virtual tour of key workshops, providing users with an immersive experience, while simulating construction progress and steps to improve construction efficiency. The commissioning management components include commissioning safety management, commissioning quality management, commissioning environment management, commissioning progress management, commissioning cost management, commissioning experience feedback management; equipment dismantling and maintenance, system transformation, special maintenance, and final processing. The joint debugging and debugging test components include the main control room operation and special test work. Commissioning test report and intelligent calculation components include preparation and publication, handover document preparation, ticket preparation, tool spare parts, equipment status inspection, prerequisite confirmation, test implementation and data recording, unexpected events and changes, commissioning report preparation, test result analysis and evaluation, Resume on-site handover and final item processing. The integrated component of handover and handover builds an integrated handover and handover management intermediate database on the basis of existing system applications by planning the standard process of handover and handover business, the standard data format of legacy items, and the interface scheme and other functional modules to provide unified query , interface, interface provides and other services.

Production and operation service units, including equipment management components, nuclear emergency decision command and management components, nuclear power plant physical protection components, DCS (distributed control system) system components, multi-base technical support components, production plan management components, nuclear power plant overhaul management system components, Group factory production and operation management components.

Among them, the equipment management component provides a unified management method for all kinds of problems found in the operation of the more important equipment of the nuclear power plant. Centering on equipment problems, it realizes the addition, tracking, upgrading and progress of equipment problems and their derived problems. Evaluation, closure, query, statistics, export and outlook reminders as well as hierarchical, integrated, electronic management. The nuclear emergency decision-making command and management component integrates and utilizes various emergency data resources of nuclear power plants to realize data collection and monitoring, emergency level auxiliary judgment, accident status judgment and decision-making, and emergency action procedures. The nuclear power plant physical protection component is a comprehensive security management software specially applied to the operation and management of the nuclear power plant physical protection system. DCS system components realize basic functions including nuclear power unit operation data collection, calculation, data transmission, and monitoring through sensor network and central control system. The multi-base technical support component is a system dedicated to the management and settlement of technical support work for nuclear power plant contractors. It realizes the demand application for multi-base technical support services, task assignment, system authorization, task execution, working hours calculation, material borrowing, and financial settlement. and other functions. The production plan management component realizes the functions of three-day rolling plan preparation, seven-day plan preparation, daily production milestone plan, work order management, work order statistics, and high-risk statistics for nuclear power plant production. The components of the nuclear power plant overhaul management system include NPP overhaul index management, overhaul task preparation, overhaul plan management, overhaul technical issues, overhaul safety management, overhaul quality management, overhaul contractor management, overhaul document management, and overhaul change management modules. The production and operation management components of the group factory include system procedures, information and reports, trap management, routine and overhaul, hidden danger investigation, major meetings and holidays, summer peaks and other special work, as well as the group factory weekly meeting TEF daily meeting, TEF weekly meeting, special There are five special modules for conferences such as reports, exchanges and seminars.

Decommissioning service unit, including decommissioning project management component, decommissioning collaborative design component, decommissioning impact analysis component, and decommissioning process management component.

Among them, the decommissioning project management component is suitable for the decommissioning of radioactive facilities, decommissioning engineering and the demolition of conventional facilities. The decommissioning collaborative design component includes several modules of radiation protection design, ventilation system design, process design and comprehensive report, and realizes the optimal dose analysis of radiation protection in the decommissioning construction stage. The decommissioning impact analysis component includes safety assessment, three-dimensional radiation assessment and visual decommissioning treatment impact analysis functions, which are used for decommissioning feasibility studies, safety analysis and environmental impact assessment, and guide decommissioning design and construction. The decommissioning process management component includes the management of many different technical methods and treatment processes in the decontamination, cutting and dismantling process to ensure the improved quality of the decommissioning process.

In this embodiment, the micro-service center supports quick access to various services, realizes integration and unified management with existing nuclear power business components, and provides services to the outside world in a standard form. The microservice center transforms various components into different open cloud services, provides unified support and scheduling management, improves the efficiency of the group in deployment, debugging and operation, and realizes the agile business delivery in the industrial Internet edge-cloud collaborative system of the nuclear power industry. .

In one embodiment, as shown in FIG. 3 , a schematic diagram of the principle of the microservice management platform is shown. Specifically, the microservice management platform includes a service interface management platform and an industrial microservice center. Among them, the service interface management platform includes many links such as design, development, management, testing, release, monitoring and opening. The modules are divided to obtain the service interface integration unit, service testing unit, gateway unit, service monitoring unit, service registration and configuration unit, and service orchestration unit indicated in the above implementations. The service interface management platform also includes a service interface management portal unit. The portal unit through the service interface management is mainly a unified entry for service interface developers, third-party developers, and partners of the enterprise. The service interface management platform pools computing, storage, network and other resources through virtualization technology, provides users with measurable and flexible resource services, and builds service interfaces on this basis, and realizes the integration of various complex service interface services. Efficient management, sorting out the mutual invocation and dependencies between service interfaces, integrating, creating, testing, gateway configuration management, portal management, monitoring unit, service registration and configuration, and service orchestration management of service interfaces to achieve agile microservice business Delivered, providing a comprehensive and convenient service environment for the industrial Internet edge-cloud collaboration system. The Industrial Microservice Center includes R&D processing unit, engineering and operation management unit, collaborative design unit, supply chain collaboration unit, construction and manufacturing service unit, production operation service unit and decommissioning service unit. The Industrial Microservice Center supports quick access to various services, integrates and manages with existing nuclear power business components, and provides services in a standard form.

In one embodiment, as shown in FIG. 4 , a schematic diagram of the principle of a service interface processing method is shown. Specifically, the service interface developer invokes each function provided by the service interface integration unit, the service orchestration unit, the service testing unit, and the service registration and configuration unit through the service interface management portal unit. The server can publish the service interface through the gateway unit, and the user can manage the portal unit through the service interface to call the published service interface. The service interface may include at least one interface among 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. These interfaces belong to Microservice Center. The service monitoring unit can monitor each service in the microservice center and collect heartbeat and log information.

It should be understood that although the steps in the flowcharts in some embodiments of the present application are displayed in sequence according to the arrows, these steps are not necessarily executed sequentially in the order indicated by the arrows. Unless explicitly stated herein, the execution of these steps is not strictly limited to the order, and the steps may be executed in other orders. Moreover, at least a part of the steps in the flowchart may include multiple steps or multiple stages, these steps or stages are not necessarily executed at the same time, but may be executed at different times, and the execution order of these steps or stages is not It is necessarily performed sequentially, but may be performed alternately or alternately with other steps or at least a portion of a step or phase within the other steps.

In one embodiment, as shown in FIG. 5, a service interface processing apparatus 500 is provided, including: an interface definition module 502, an interface orchestration module 504, an interface testing module 506 and an interface publishing module 508, wherein:

The interface definition module 502 is configured to acquire 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 504 is configured to, in response to the orchestration operation 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 for calling Selected service interface and public interface.

The interface testing module 506 is configured to perform automated testing on the generated service interface to obtain the service interface to be registered.

The interface publishing module 508 is configured to publish the registered service interface after registering the service interface to be registered in the affiliated microservice center.

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; the interface definition module 502 is further configured to determine the specified in the service interface generation interface The data processing model and the data model generate a first service interface; 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 specified in the service interface generation interface and The data source generates a second service interface; wherein, the second service interface is used to perform structured query in the data source through structured query language data.

In one embodiment, the service definition data includes at least one of cross-platform service code and database stored procedure information; the interface definition module 502 is further configured to confirm the database stored procedure information specified on the service interface generation interface, and generate the 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 the fourth service interface; the fourth service The interface is used to run cross-platform service code and return the running result.

In one embodiment, the orchestration operation includes an interface selection operation and an interface move operation; the interface orchestration module is further configured to present the service orchestration interface; in response to the interface selection operation in the service orchestration interface, the selected public interface and the generated interface are determined. The service interface selected in the service interface; in response to the interface move 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 used to call the selected service interface and public interface according to the running order.

In one embodiment, the interface testing module is further configured to construct an automated test environment for the service interface in response to a configuration operation in the test interface; and determine a test scenario for the service interface in response to a test orchestration operation in the test interface; The service interface is automatically tested by using the test scenario in the automated test environment to obtain the service interface to be registered.

In one embodiment, the interface publishing module is further configured to publish the service interface to be published through the gateway unit after registering the service interface to be registered in the microservice center to which it belongs, so that the caller invokes the published service interface; During the process of invoking the published service interface by the caller, at least one of access authority control, access route control and security control is performed by the gateway unit.

In one embodiment, after the service interface to be registered is registered with the microservice center to which it 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 Monitoring is performed to obtain at least one type of data in the operation performance data, the statistical data of the number of calls and the call link topology map.

For the specific limitation of the foregoing service interface processing apparatus, reference may be made to the foregoing limitation of the foregoing service interface processing method, which will not be repeated here. Each module in the above-mentioned service interface processing apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

In one embodiment, a computer device is provided, the computer device may be a server, and its internal structure diagram may be as shown in FIG. 6 . The computer device includes a processor, memory, and a network interface connected by a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium, an internal memory. The nonvolatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the execution of the operating system and computer programs in the non-volatile storage medium. The database of the computer device is used to store service interface processing data. The network interface of the computer device is used to communicate with an external terminal through a network connection. The computer program implements a service interface processing method when executed by the processor.

Those skilled in the art can understand that the structure shown in FIG. 6 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied. Include more or fewer components than shown in the figures, or combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is also provided, including a memory and a processor, where a computer program is stored in the memory, and the processor implements the steps in the foregoing method embodiments when the processor executes the computer program.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, implements the steps in the foregoing method embodiments.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing relevant hardware through a computer program, and the computer program can be stored in any non-volatile computer-readable storage medium, When the computer program is executed, it may include the processes of the above-mentioned method embodiments. Wherein, any reference to memory, storage, database or other media used in the various embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (Read-Only Memory, ROM), magnetic tape, floppy disk, flash memory, or optical memory, and the like. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, the RAM may be in various forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM).

The technical features of the above embodiments can be combined arbitrarily. In order to make the description simple, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features It is considered to be the range described in this specification.

The above examples only represent several embodiments of the present application, and the descriptions thereof are relatively specific and detailed, but should not be construed as a limitation on the scope of the invention patent. It should be pointed out that for those skilled in the art, without departing from the concept of the present application, several modifications and improvements can be made, which all belong to the protection scope of the present application. Therefore, the scope of protection of the patent of the present application shall be subject to the appended claims.

Claims (10)

1. A method for service interface processing, the method comprising:

acquiring service definition data designated in a service interface generation interface;

generating a corresponding service interface based on the service definition data;

responding to the arrangement operation in the service arrangement interface, processing the selected public interface and the service interface selected from the generated service interfaces, and generating a new service interface; the new service interface is used for calling the selected service interface and the public interface;

performing automatic test on the generated service interface to obtain a service interface to be registered;

and after the service interface to be registered is registered to the affiliated micro service center, issuing the registered service interface.

2. The method of claim 1, wherein the service definition data comprises at least one of structured query language data, data source information, a data processing model identification, and a data model identification; the generating of the corresponding service interface based on the service definition data comprises at least one of the following processes:

determining a data processing model and a data model which are specified in the service interface generation interface, and generating a first service interface; the first service interface is used for processing the data acquired by the data model through the data processing model;

determining structured query language data and a data source specified in the service interface generation interface, and generating a second service interface; wherein the second service interface is configured to perform a structured query in the data source through the structured query language data.

3. The method of claim 1, wherein the service definition data comprises at least one of cross-platform service code and database stored procedure information; the generating of the corresponding service interface based on the service definition data comprises at least one of the following processes:

confirming the database storage process information appointed on the service interface generating interface, and generating a third service interface; the third service interface is used for operating the database storage process information based on the access parameters transmitted by the calling party and acquiring a database return result;

confirming a cross-platform service code appointed on the service interface generating interface, and generating a fourth service interface; the fourth service interface is used for running the cross-platform service code and returning a running result.

4. The method of claim 1, wherein the orchestration operation comprises an interface selection operation and an interface movement operation; the method comprises the steps of responding to arrangement operation in a service arrangement interface, processing a selected public interface and a service interface selected from generated service interfaces, and generating a new service interface; the new service interface is used for calling the selected service interface and the public interface comprises:

displaying a service arrangement interface;

in response to an interface selection operation in the service orchestration interface, determining a selected common interface and a service interface selected from the generated service interfaces;

determining a running order between a selected service interface and the common interface in response to an interface move operation for the selected service interface and the common interface;

processing the selected service interface, the public interface and the running sequence to generate a new service interface; and the new service interface is used for calling the selected service interface and the public interface according to the running sequence.

5. The method of claim 1, wherein performing automated testing on the generated service interface to obtain a service interface to be registered comprises:

building an automated test environment for the service interface in response to a configuration operation in a test interface;

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

and automatically testing the service interface by using the test scene in the automatic test environment to obtain the service interface to be registered.

6. The method according to claim 1, wherein the publishing the registered service interface after registering the service interface to be registered with the affiliated micro service center comprises:

after the service interface to be registered is registered to the affiliated micro service center, the service interface to be issued is issued through the gateway unit, so that a calling party calls the issued service interface;

and in the process of calling the issued service interface by the calling party, performing at least one of access authority control, access routing control and security control through the gateway unit.

7. The method according to claim 1, wherein after the publishing the registered service interface after registering the service interface to be registered with the affiliated micro service center, the method further comprises:

and monitoring the service interface in operation through the service monitoring unit to obtain at least one of operation performance data, calling frequency statistical data and calling link topological graph data.

8. The method of claim 1, wherein the service interface comprises at least one of a development processing interface, an engineering and operations processing interface, a co-design interface, a supply chain co-design interface, a build and manufacturing service interface, a production run service interface, and a decommissioning service interface.

9. A service interface processing apparatus, characterized in that the apparatus comprises:

the interface definition module is used for acquiring service definition data appointed in the service interface generation interface; generating a corresponding service interface based on the service definition data;

the interface arrangement module is used for responding to arrangement operation in the service arrangement interface, processing the selected public interface and the service interface selected from the generated service interfaces and generating a new service interface; the new service interface is used for calling the selected service interface and the public interface;

the interface testing module is used for executing automatic testing on the generated service interface to obtain a service interface to be registered;

and the interface publishing module is used for publishing the registered service interface after registering the service interface to be registered to the affiliated micro service center.

10. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 8.

Images