Nuclear power production service management system

Abstract

The invention belongs to the technical field of nuclear power, and particularly relates to a nuclear power production service management system. According to the system, a management framework is deployed and a nuclear power production service management function is provided based on Kubernetes and Docker containerization virtualization technologies, compared with a traditional mode, more stable, robust, simple, convenient, continuous and comprehensive service management is formed for software services, high availability and service expandability of application services are guaranteed, and the service management efficiency is improved. And non-research and non-development operations of developers are reduced, so that the developers can concentrate on the development of own businesses.

Description

Technical Field

[0001] This invention belongs to the field of nuclear power technology, and specifically relates to a nuclear power production service management system. Background Technology

[0002] Nuclear power, as a safe, clean, low-carbon, and reliable energy source, has been increasingly accepted and adopted by more and more countries, and its related industries are constantly expanding. The informatization and digitalization of the nuclear power industry are also gradually improving. This informatization and digitalization relies on software services. With the expansion of basic services in the nuclear power industry, the scale of related services is also constantly growing, and the complexity of nuclear power-related systems is increasing exponentially. The difficulty of system maintenance and readability also increase accordingly, which leads to a corresponding decrease in system stability, availability, and other performance characteristics, ultimately affecting the user experience. In response to the above situation, ordinary monolithic architectures cannot support the stable operation of large-scale services. Therefore, it is urgent to optimize the architecture of the nuclear power industry's information systems to improve system service performance. Summary of the Invention

[0003] To overcome the problems existing in related technologies, a nuclear power production service governance system based on cloud-native technology is provided.

[0004] According to one aspect of the present disclosure, a nuclear power production service governance system is provided, the system comprising: a Kubernetes platform, a service governance framework, and multiple application services; The Kubernetes platform provides container management capabilities, including service scaling, self-healing, service discovery, and load balancing. The service governance framework, deployed on the Kubernetes platform, includes a registry center, configuration center, circuit breaker protection module, and service call monitoring module. Multiple application services are deployed in the form of containers in the corresponding namespaces of the Kubernetes platform. Each application service instance runs as a Pod and is exposed through a Service, wherein the Service is bound to a group of Pods through Label and Selector rules. Each application service is configured to access the service governance framework, including: When the system starts up, it registers service information with the registry center, including the name, IP address, port and metadata of the application service, and groups the services according to the name of the application service. Instances of application services with the same name are registered under the same group, and the system pulls service registry data from the registry center and caches it locally. The configuration center is used for dynamic configuration management. A long polling mechanism on the client is used to monitor configuration changes. When a configuration change occurs, the client is asynchronously triggered to fetch configuration data and update the local cache. When making inter-service calls, the instance of the service being called is obtained from the local registry, and a request is sent to the target instance through a load balancing strategy. The circuit breaker protection module is integrated to trigger the circuit breaker strategy and perform circuit breaker degradation when a downstream service is detected to have timed out or become unavailable. The service call monitoring module is integrated to record service call chain data, including Span and Trace, and report it to the service call monitoring module for persistence to generate call topology and node details.

[0005] In one possible implementation, the service governance framework and the application service are deployed on the Kubernetes platform via image processing.

[0006] In one possible implementation, the registry center is used to maintain the service registry and receive heartbeat information periodically reported by the application service to monitor the instance status. The application service updates the local registry data by periodically pulling data.

[0007] In one possible implementation, the configuration center allows users to create and modify configuration files and trigger configuration change events via the server. The client has a long polling mechanism to obtain configuration updates in real time.

[0008] In one possible implementation, the circuit breaker protection module triggers circuit breaking and degradation during service calls due to network anomalies or downstream service failures to prevent system cascading failures.

[0009] In one possible implementation, the service call monitoring module persists the call chain data and then displays the service call topology in a graphical manner on the control page, including the request time, number of calls, number of failures, and call instance information of each call node.

[0010] In one possible implementation, the application service accesses the components of the service governance framework through service names and namespaces, ensuring the stability and scalability of the service governance framework.

[0011] The beneficial effects of this disclosure are as follows: The nuclear power production service governance system provided by this disclosure deploys a governance framework and provides nuclear power production service governance functions based on Kubernetes and Docker containerization and virtualization technologies. Compared with traditional methods, it provides more stable, robust, simple, and continuous comprehensive service governance for software services, ensuring high availability and scalability of application services, reducing non-R&D operations for developers, and allowing developers to focus more on their own business development. Attached Figure Description

[0012] Figure 1This is a schematic diagram of a nuclear power production service management system shown in an embodiment of this disclosure.

[0013] Figure 2 This is a schematic diagram illustrating the application and organization process of a nuclear power production service management system according to an embodiment of this disclosure. Detailed Implementation

[0014] The present disclosure will now be described in further detail with reference to the accompanying drawings and specific embodiments.

[0015] Unless otherwise defined, the technical and scientific terms used in this disclosure have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains; the terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of this disclosure; the term "comprising" and any variations thereof in this disclosure are intended to cover non-exclusive inclusion. Clearly, the embodiments described in this disclosure are only a part of the embodiments of this disclosure, and not all of them. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0016] In this disclosure, the reference to "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this disclosure. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0017] See Figure 1 The nuclear power production service governance system disclosed herein includes: a Kubernetes cluster, a service governance framework, and multiple application services.

[0018] The Kubernetes platform provides container management capabilities, including service scaling, self-healing, service discovery, and load balancing. A service governance framework, deployed on the Kubernetes platform, includes a registry, configuration center, circuit breaker protection module, and service call monitoring module. Multiple application services are deployed as containers in their respective namespaces on the Kubernetes platform. Each application service instance runs as a Pod and is exposed through a Service, where each Service is bound to a group of Pods via Label and Selector rules. The underlying Kubernetes platform provides container governance capabilities, ensuring the high stability, scalability, and continuous service capabilities of the service governance framework and the service application's running service containers.

[0019] After deploying the applications required for nuclear power production services on the Kubernetes platform using containers, Pods for each application are created under the corresponding namespaces on the Kubernetes platform. Each application Pod represents a service instance and contains information such as the application's IP address and port. These applications are exposed through Kubernetes Services, which bind to a group of application Pods using Labels and Selector rules. Each application configures the relevant components of the nuclear power production service governance framework using the `serviceName.namespace` method, ensuring the stability, scalability, and continuous service governance capabilities of the nuclear power production service governance framework.

[0020] After an application is launched, the Nuclear Power Production Service Governance System reports its service information to the system's service registry (which includes application name, IP address, port, and metadata). The service registry groupes applications based on this information, registering instances with the same service information under the same group. During each application's operation, it periodically reports its current instance status heartbeat to the service registry, forming the application's service registry data. After successful application registration, the Nuclear Power Production Service Governance System retrieves each application's service registry data from the service registry at a preset frequency and stores it locally on the application's machine to update the application's local registry data.

[0021] When applications make calls, the application making the call first looks up the service instance of the called application in its local registry. This avoids accessing the remote registry center for every call, reducing network overhead and improving system availability. Even if the registry center is temporarily unavailable, the local cache can still support service discovery. If the application making the call cannot find the service instance of the called application in the local registry, it looks up the service instance of the called application in the service registry center. The application making the call needs to select one of the multiple instances obtained to initiate a request.

[0022] After integrating dynamic configurations for multiple applications, the nuclear power production service governance system extracts the configuration information related to each application into a configuration file. The configuration is then read using the `@Value` method, and the configuration data is loaded locally into each application. After the client sends a poll to the server, the application periodically monitors whether the corresponding configuration content has changed. If a change is found, an asynchronous call is initiated via a long connection, the client retrieves the configuration data, and updates it locally.

[0023] The service integrates circuit breaker and link-related plugins. During inter-service calls, a span is recorded at the request entry point, and a trace is formed from the request to the response. This trace is used for service monitoring and analysis, and the service call relationship is displayed graphically to aid in troubleshooting. To ensure overall system availability and fault tolerance, in the event of network or downstream service anomalies during service calls, a circuit breaker strategy is triggered to perform circuit breaking and degradation, protecting the entire system from service downtime or a cascading failure due to excessive request blocking.

[0024] See Figure 2 The service governance framework and application services are deployed in a Kubernetes cluster via images. Leveraging Kubernetes' container governance capabilities, the framework ensures high availability, stability, and continuous governance, including dynamic scaling and fault recovery for application services.

[0025] The application service registers with the registry center and obtains the service registration list, caching the registration list data locally. The application can choose whether to use dynamic configuration. If dynamic configuration is selected, configuration files can be created and modified through the configuration center. When the configuration server triggers configuration changes, it calls a long polling request on the client, which then retrieves the configuration content and updates it to its local cache.

[0026] Calls between application services generate call chain data, which is reported to the service governance and monitoring module for data persistence. The service governance control page displays service chain information and call topology, showing detailed information for each call node, including request time, number of calls, number of failures, and call instance. During service calls, if a downstream service times out or becomes unavailable, a circuit breaker policy is triggered for degradation processing.

[0027] The service governance system is used in the nuclear power production service environment. It ensures the high availability, robustness and scalability of software services through containerization and virtualization technology, allowing developers to focus on business development.

[0028] The various embodiments of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or improvement of the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A nuclear power production service management system, characterized in that, The system includes: a Kubernetes cluster, a service governance framework, and multiple application services; Kubernetes clusters are used to provide container management capabilities, including service scaling, self-healing, service discovery, and load balancing. The service governance framework, deployed on the Kubernetes cluster, includes a registry center, a configuration center, a circuit breaker protection module, and a service call monitoring module. Multiple application services are deployed in the form of containers in the corresponding namespaces of the Kubernetes cluster. Each application service instance runs as a Pod and is exposed through a Service, wherein the Service is bound to a group of Pods through Label and Selector rules. Each application service is configured to access the service governance framework, including: When the system starts up, it registers service information with the registry center, including the name, IP address, port and metadata of the application service, and groups the services according to the name of the application service. Instances of application services with the same name are registered under the same group, and the system pulls service registry data from the registry center and caches it locally. The configuration center is used for dynamic configuration management. A long polling mechanism on the client is used to monitor configuration changes. When a configuration change occurs, the client is asynchronously triggered to fetch configuration data and update the local cache. When making inter-service calls, the instance of the service being called is obtained from the local registry, and a request is sent to the target instance through a load balancing strategy. The circuit breaker protection module is integrated to trigger the circuit breaker strategy and perform circuit breaker degradation when a downstream service is detected to have timed out or become unavailable. The service call monitoring module is integrated to record service call chain data, including Span and Trace, and report it to the service call monitoring module for persistence to generate call topology and node details.

2. The system according to claim 1, characterized in that, The service governance framework and the application service are deployed in the Kubernetes cluster via image processing.

3. The system according to claim 1, characterized in that, The registry center is used to maintain the service registry and receive heartbeat information reported by the application service at regular intervals to monitor the instance status. The application service updates the local registry data by periodically pulling data.

4. The system according to claim 1, characterized in that, The configuration center allows users to create and modify configuration files and trigger configuration change events through the server. The client has a long polling mechanism to obtain configuration updates in real time.

5. The system according to claim 1, characterized in that, The circuit breaker protection module triggers circuit breaking and degradation during service calls when there is a network anomaly or a downstream service failure, in order to prevent a system cascading failure.

6. The system according to claim 1, characterized in that, The service call monitoring module persists the call chain data and then displays the service call topology in a graphical manner on the control page, including the request time, number of calls, number of failures, and call instance information for each call node.

7. The system according to claim 1, characterized in that, The application service accesses the components of the service governance framework through service names and namespaces, ensuring the stability and scalability of the service governance framework.

Images