Service orchestration method for cloud native architecture platform informatization

Abstract

The invention discloses a cloud native architecture platform informatization-oriented service orchestration method, which comprises the following steps of: S1) providing an orchestration component, defining and managing a working process between micro-services, so that data and a request are correctly transmitted between the micro-services and a new service is formed; s2) packaging the service arrangement component into a standardized container through a Docker technology; s3) realizing automatic deployment of micro-services in the cloud native architecture, and managing starting and updating of containerized services and automatic replacement when faults occur; s4) performing index collection and monitoring, automatically recording service deployment, removal, rollback and update operation logs, and providing detailed running log records; and S5) after service arrangement is completed, all services are registered to a management portal in a unified manner, and centralized control is realized. According to the service orchestration method, the purposes of reducing middle layer codes and reducing coding investment can be achieved, and more efficient application development and management are achieved.

Description

Technical Field

[0001] The present invention relates to a service orchestration method, and in particular to a service orchestration method oriented to the informatization of a cloud native architecture platform. Background Art

[0002] In an era of rapid digital transformation, enterprises are faced with the challenges of massive data processing and efficient operation. In order to improve work efficiency, reduce operating costs and enhance competitiveness, cloud native architecture has emerged and provided a new solution. It uses advanced security features such as automated updates and microservice isolation to not only enhance data security and system reliability, but also give enterprises more flexibility, automation and scalability.

[0003] By using cloud native technology, enterprises can decompose applications into microservices and manage them in a unified manner. This management model allows enterprises to efficiently reuse existing microservices and meet business needs through service orchestration capabilities, thereby reducing the writing of middle-layer code, reducing coding workload, and quickly meeting business needs.

[0004] The flexibility, automation, and scalability of cloud-native architecture ensure that enterprises can continue to progress in a dynamic market and technological context, bringing new opportunities and challenges to enterprises, but also enabling enterprises to respond to market changes more efficiently and achieve continuous innovation and development. Summary of the invention

[0005] The technical problem to be solved by the present invention is to provide a service orchestration method for the informatization of a cloud-native architecture platform, which can achieve the goal of reducing intermediate layer code, reducing coding investment, and realizing more efficient application development and management.

[0006] The technical solution adopted by the present invention to solve the above-mentioned technical problems is to provide a service orchestration method for the informatization of a cloud-native architecture platform, wherein the cloud-native architecture platform provides multiple microservices, and the service orchestration method comprises the following steps: S1) providing an orchestration component, defining and managing the workflow between microservices, so that data and requests are correctly transmitted between microservices and form new services; S2) encapsulating the service orchestration component into a standardized container through Docker technology; S3) realizing the automated deployment of microservices in the cloud-native architecture, managing the startup, update and automatic replacement of containerized services in the event of a failure; S4) collecting and monitoring indicators, automatically recording service deployment, removal, rollback and update operation logs, and providing detailed operation log records; S5) after the service orchestration is completed, all services are uniformly registered to the management portal to achieve centralized control.

[0007] Furthermore, in step S1, the orchestration component uses nodes as basic building blocks, and constructs a workflow by dragging and dropping nodes and connecting different nodes; the nodes are divided into input nodes, processing nodes and output nodes, and data is transmitted between nodes through message objects, and the message objects contain payload, subject and metadata.

[0008] Furthermore, the step S1 also includes providing a custom node for integrating new hardware devices, services or performing customized tasks.

[0009] Furthermore, the service orchestrated in step S1 is event-driven and provides an exception capture node for capturing exceptions occurring in its upstream node; when an error occurs in other nodes connected to the exception capture node, the exception capture node captures the exception and handles the error by recording the error and sending a notification, while supporting global exception handling.

[0010] Furthermore, step S3 automatically or on-demand increases instances for horizontal expansion according to load changes, and automatically or on-demand increases resources for vertical expansion according to load changes.

[0011] Furthermore, step S4 uses Prometheus to collect and monitor indicators, combines Grafana for data visualization, and combines Elasticsearch, Logstash, and Kibana to achieve log storage and in-depth analysis.

[0012] Furthermore, for the flood prevention monitoring application scenario, the step S4 accurately projects the flood prevention video monitoring points onto the spatiotemporal map, intuitively displays the monitoring coverage on the map, and uses the interactive map function to deeply view the detailed information of each monitoring point.

[0013] Furthermore, all microservices in the cloud-native architecture platform run on Kubernetes. The service orchestration method also includes building a process snapshot for release. Once the workflow is released, each workflow forms an independent service in the container and can be authorized to access through the management portal. After the service is launched, the operation log is sent to the log system, and the service will be registered with the monitoring and early warning system for log aggregation, real-time monitoring and data visualization.

[0014] Furthermore, it also includes providing version control functions. A snapshot is stored for each released version. By selecting the appropriate snapshot for deployment, detailed information of each version can be tracked and stored. Once the system encounters a failure, the snapshot can be used to quickly restore the service.

[0015] Compared with the prior art, the present invention has the following beneficial effects: the service orchestration method for cloud native architecture platform informatization provided by the present invention comprehensively practices data and application service orchestration under the cloud native architecture platform, and explores methods and key technical paths. Through experimental verification of key technologies such as service orchestration, containerization, dynamic management, DevOps, continuous delivery, security, version control, logging and monitoring, the results show that this combination can effectively improve the high availability, horizontal expansion capability and security of the service. In addition, the present invention can also reduce the middle-layer code and reduce the coding workload. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 This is an application architecture diagram of the service orchestration method for cloud native architecture platform informatization of the present invention;

[0017] Figure 2 It is a schematic diagram of the service arrangement process of the present invention;

[0018] Figure 3 It is a schematic diagram of the log collection process of the present invention;

[0019] Figure 4 It is a schematic diagram of the service monitoring process of the present invention. DETAILED DESCRIPTION

[0020] The present invention will be further described below in conjunction with the accompanying drawings and embodiments.

[0021] Under the informationization mode of cloud native architecture platform, this paper summarizes the method paths and key technologies of practical data and application service orchestration, including the following functions: service orchestration, containerization, dynamic management, DevOps and continuous delivery, security, version control, logging, and monitoring.

[0022] Service orchestration: There are hundreds or even thousands of microservices in the cloud native architecture. Service orchestration can define and manage the workflow between microservices, ensure that data and requests are correctly transmitted between services and form new services, and ensure that the correct services are triggered and executed in the correct order, especially when the business process spans multiple services. Service orchestration provides a rich orchestration component to reduce the middle-layer code, reduce coding investment, and quickly meet business needs.

[0023] Orchestration service orchestration is based on the idea of ​​process programming, where users build workflows by dragging and dropping nodes and connecting them. This workflow is called a "flow" and consists of a series of connected nodes that can perform various tasks, such as reading sensor data, sending HTTP requests, or processing data.

[0024] In service orchestration, nodes are the basic building blocks of processes and represent code blocks that perform specific tasks. Nodes are divided into input nodes, processing nodes, and output nodes. Users can drag and drop them to the workspace through a visual interface and connect them to define processes.

[0025] Data is passed between nodes via message objects. Message objects contain information about the data, such as payload, subject, metadata, etc. Nodes are able to process these message objects and pass them on to the next connected node.

[0026] Users can extend system functionality by allowing custom nodes to be installed. This enables users to integrate new hardware devices, services, or perform other customized tasks.

[0027] Service orchestration is event-driven. The system listens for events from users, nodes, and systems. Once an event occurs, the service orchestration component handles it accordingly, such as executing a node in the process or notifying the user. This event-driven architecture makes service orchestration flexible and highly customizable.

[0028] Service orchestration provides a "catch exception" node to catch exceptions that occur in its upstream nodes. When errors occur in other nodes connected to the catch exception node, the catch exception node will catch the exception, and users can define operations to handle the errors, such as logging errors, sending notifications, etc. At the same time, service orchestration supports global exception handling, and the global error handling mechanism can be configured in the settings. No matter which node the exception occurs in, it can be handled at the global level.

[0029] Containerization: By encapsulating service orchestration components into standardized containers through technologies such as Docker, the consistency and portability of applications in different environments are ensured. These containers can be started quickly and run reliably in various environments, reducing the dependencies between services and improving the overall flexibility and maintainability of the system. This meets the requirements of cloud-native architecture for rapid deployment and high reliability.

[0030] Dynamic management: Service orchestration enables automated deployment of microservices in cloud-native architectures, managing the startup, update, and automatic replacement of containerized services in the event of failures. This architectural design supports automatic recovery and maintains service continuity even in the event of infrastructure failures. In addition, applications can automatically or on-demand scale horizontally (add instances) or vertically (add resources) based on load changes, thereby flexibly adapting to market demand.

[0031] DevOps and continuous delivery: Service orchestration provides fast, visual process changes and the entire process management from development to production environment deployment, accelerating software construction and thus speeding up delivery from development to production.

[0032] Version control: Service orchestration provides version control capabilities. Each released version stores a snapshot. In the version control system, developers can switch versions and compare differences. Databases use snapshots to protect data and ensure integrity. In deployment and testing, snapshots create a known state environment to improve test consistency. When errors occur, snapshots help understand the system state, facilitate diagnosis and repair. Performance tests are based on the same state and accurately compare performance. In disaster recovery, snapshots quickly restore the system. Snapshots are a key tool in software development, improving efficiency, reducing errors, and ensuring reliable testing.

[0033] Security: After service orchestration is completed, all services are uniformly registered to the management portal for centralized control. By implementing strict authentication and authorization mechanisms, only authorized users can access specific services and data, and the principle of least privilege is followed to enhance security. In addition, the HTTPS protocol is used to encrypt data transmission, thereby enhancing data transmission security.

[0034] Logs: Service orchestration automatically records service deployment, removal, rollback, and update operation logs, and provides detailed operation log records. Combined with the ELK stack (Elasticsearch, Logstash, Kibana), efficient storage and in-depth analysis of logs are achieved to optimize monitoring and troubleshooting.

[0035] Monitoring: Service orchestration uses Prometheus for metric collection and monitoring, combined with Grafana for data visualization, to achieve comprehensive monitoring of system status and performance. These tools together provide logging and alerting capabilities to help identify and respond to system problems in a timely manner.

[0036] The present invention is applied in the following practical scenarios:

[0037] Scenario 1: Data visualization of flood control video monitoring points in the spatiotemporal map

[0038] Through the service orchestration template component, the spatiotemporal map display of flood control video monitoring point data is realized to enhance the intuitive visualization of data. The service accurately projects the flood control video monitoring points on the spatiotemporal map, allowing users to intuitively understand the monitoring coverage on the map and view the detailed information of each monitoring point through the interactive map function. This optimized spatiotemporal map display capability not only improves the visualization of data, but also enhances users' understanding and utilization of flood control monitoring point data.

[0039] Scenario 2: Integrate flood prevention video surveillance services along the Huangpu River

[0040] Through service orchestration, the flood control video surveillance services in the four areas of Huangpu, Xuhui, Hongkou and Pudong were successfully integrated, and efficient and secure video surveillance services were provided for the "Digital Twin Huangpu River Project". While ensuring the security requirements for data use, this service displays the flood control monitoring points along the river in an intuitive way by optimizing the spatiotemporal map display capabilities. Such collaborative integration not only improves the value of the service, but also makes the information presented on the spatiotemporal map more intuitive and clear, further enhancing the practicality and visualization of the data, forming a synergistic effect of 1+1>2.

[0041] like Figure 1 As shown in the figure, in the system built under the cloud native architecture, all services run on Kubernetes. The service orchestration management terminal provides orchestrators with the function of demand design and test process, and allows the construction of process snapshots for release. Once the process is released, each process forms an independent service in the container, and developers can authorize access through the portal. After the service is launched, the operation log will be sent to the log system, and the service will be registered with the monitoring and early warning system for log aggregation, real-time monitoring and data visualization.

[0042] like Figure 2 As shown, in the service orchestration process of the present invention, service developers design the process through a visual interface to ensure that it meets business requirements and conduct tests. After the design is completed, the developer will create a snapshot of the process and select the appropriate snapshot for deployment in order to track and store detailed information of each version. Once the system encounters a failure, these snapshots can quickly restore the service. After the service is deployed and enters the running state, it can start to provide the required services to users. At the same time, the cloud native architecture supports the management of the startup, update and automatic replacement of containerized services in the event of a failure, and maintains service continuity even in the event of an infrastructure failure.

[0043] like Figure 3 As shown in Figure 1, the service orchestration tool automatically tracks and records the deployment, removal, rollback, and update operations of all services, while collecting detailed operation logs. These logs are efficiently stored and can be used for in-depth analysis, thereby improving monitoring efficiency and accelerating the fault diagnosis process.

[0044] like Figure 4 As shown in the figure, the monitoring system collects key performance indicators and monitors the entire system to ensure a comprehensive understanding of the system status and performance. These tools integrate logging and alarm mechanisms, so that system problems can be quickly discovered and responded to, improving the reliability and response speed of the system.

[0045] Although the present invention has been disclosed as above with preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art may make some modifications and improvements without departing from the spirit and scope of the present invention. Therefore, the scope of protection of the present invention shall be based on the definition of the claims.

Claims

1. A service orchestration method for cloud native architecture platform informatization, wherein the cloud native architecture platform provides multiple microservices, characterized in that: The service arrangement method comprises the following steps: S1) Provides orchestration components to define and manage workflows between microservices, so that data and requests are correctly transmitted between microservices and form new services; S2) Encapsulate the service orchestration components into standardized containers through Docker technology; S3) Automated deployment of microservices in cloud-native architectures, managing the startup, update, and automatic replacement of containerized services in the event of failures; S4) collects and monitors indicators, automatically records service deployment, removal, rollback and update operation logs, and provides detailed operation log records; S5) After the service orchestration is completed, all services are uniformly registered to the management portal for centralized control.

2. The service orchestration method for cloud native architecture platform informatization according to claim 1, characterized in that: In step S1, the orchestration component uses nodes as basic building blocks, and builds a workflow by dragging and dropping nodes and connecting different nodes; the nodes are divided into input nodes, processing nodes and output nodes, and data is transmitted between nodes through message objects, and the message objects contain payload, subject and metadata.

3. The service orchestration method for cloud native architecture platform informatization according to claim 2, characterized in that: The step S1 also includes providing a custom node for integrating new hardware devices, services or performing customized tasks.

4. The service orchestration method for cloud native architecture platform informatization according to claim 1, characterized in that: The service choreographed in step S1 is event-driven and provides an exception capture node for capturing exceptions occurring in its upstream node; When an error occurs in other nodes connected to the exception-catching node, the exception-catching node will catch the exception and handle the error by recording the error and sending notifications, while supporting global exception handling.

5. The service orchestration method for cloud native architecture platform informatization according to claim 1, characterized in that: The step S3 automatically or on demand increases instances according to load changes for horizontal expansion, and automatically or on demand increases resources according to load changes for vertical expansion.

6. The service orchestration method for cloud native architecture platform informatization according to claim 1, characterized in that: The step S4 uses Prometheus to collect and monitor indicators, combines Grafana for data visualization, and combines Elasticsearch, Logstash, and Kibana to achieve log storage and in-depth analysis.

7. The service orchestration method for cloud native architecture platform informatization according to claim 1, characterized in that: For the flood prevention monitoring application scenario, step S4 accurately projects the flood prevention video monitoring points onto the spatiotemporal map, intuitively displays the monitoring coverage on the map, and uses the interactive map function to view the detailed information of each monitoring point.

8. The service orchestration method for cloud native architecture platform informatization according to claim 1, characterized in that: All microservices in the cloud-native architecture platform run on Kubernetes, and the service orchestration method further includes building a process snapshot for release. Once the workflow is released, each workflow forms an independent service in the container and can be authorized to access through the management portal; After the service goes online, the operation log is sent to the log system, and the service is registered to the monitoring and early warning system for log aggregation, real-time monitoring and data visualization.

9. The service orchestration method for cloud native architecture platform informatization according to claim 8, characterized in that: It also provides version control functions. A snapshot is stored for each released version. By selecting the appropriate snapshot for deployment, detailed information of each version can be tracked and stored. Once the system encounters a failure, the snapshot can be used to quickly restore the service.

Images