Application software-oriented information processing method based on cloud native

Abstract

The embodiment of the invention discloses a cloud-native-based application software-oriented information processing method, which comprises the following steps: receiving packaging information configured for a service package by a user in a visual configuration mode, and packaging a service based on the packaging information to obtain a service mirror image; one or more service mirror images associated with an application program of the application software are packed to construct a service composition mirror image. Compared with other one-stop cloud platforms, the rapid delivery and treatment technology based on application software has the demand status that user group types are concentrated and application scene types are similar, and unnecessary functions are rejected while the cloud native technology is fused in a one-stop mode, so that autonomous configuration operation of users is reduced, and exposure of underlying technical details is avoided. And while the degree of freedom of part of users is reduced, the usability of the product is greatly improved, the learning cost and threshold of developers and operation and maintenance personnel are reduced, and the service application is clouded at zero cost.

Description

Technical Field

[0001] The present disclosure relates to the technical field, and in particular to a cloud-native-based information processing method for application software. Background Art

[0002] Cloud native is a method of building and running applications, a set of technical systems and methodologies. Cloud native is a combination of Cloud + Native. Cloud means that the application is located in the cloud, not in a traditional data center; Native means that the application is designed with the cloud environment in mind from the beginning. Cloud native is designed for the cloud and runs in the cloud in the best posture, making full use of the elasticity and distribution advantages of the cloud platform. Among the related technologies, the ease of use of the product, the learning cost and threshold for developers and operation and maintenance personnel are relatively high. Summary of the invention

[0003] The main purpose of the present invention is to provide a cloud-native based information processing method for application software to solve the defects existing in the related technology.

[0004] In order to achieve the above-mentioned purpose, according to the first aspect of the present disclosure, a cloud-native information processing method for application software is provided, including receiving packaging information configured by a user for a service package in a visual configuration manner, packaging the service based on the packaging information to obtain a service image; and packaging one or more service images associated with an application program of the application software to construct a service composition image.

[0005] Optionally, receiving packaging information configured by a user for a service package in a visual configuration manner, and obtaining a service image after packaging based on the packaging information includes: determining a service packaging type from the configured packaging information, wherein the packaging type includes AI service packaging, microservice packaging, and image packaging; and executing different packaging methods for different packaging types.

[0006] Optionally, executing different encapsulation methods for different encapsulation types includes: for AI service encapsulation and microservice encapsulation, performing single instance configuration based on the configured encapsulation information; for image encapsulation, obtaining a general image selected by the user; after single instance configuration and selecting a general image, obtaining hardware platform information selected by the user, wherein the hardware platform information includes configuration file mounting information, data source information, startup command, environment variables, and persistent directory; obtaining user-configured publishing information; and publishing services based on the selected hardware platform information and publishing information.

[0007] Optionally, packaging one or more service images associated with an application of the application software to construct a service composition image includes: accepting a service image associated with the application selected by a user through a visual configuration method, and pulling version information corresponding to the application; obtaining content configured by the user for one or more associated service images through a visual configuration method; and encapsulating based on the configured content and version information.

[0008] Optionally, the method further includes: obtaining deployment information configured by the user in a visual configuration manner, so as to deploy the encapsulated service based on the deployment information.

[0009] Optionally, deploying the encapsulated service based on the deployment information includes: obtaining a target service and version selected by a user; obtaining deployment location information selected by a user; and performing automatic deployment based on the target service and version and deployment location information.

[0010] Optionally, during automated deployment, the method includes: environment verification; configuration writing; performing service deployment after configuration writing is completed, wherein the service deployment includes domain name registration, and performing gateway configuration after successful registration; performing service registration after gateway configuration is completed; and completing deployment after service registration is completed.

[0011] Optionally, after the configuration is written, a status check is started, and the service deployment is completed after the check passes.

[0012] According to a second aspect of the present disclosure, a computer-readable storage medium is provided, storing computer instructions, wherein the computer instructions are used to enable the computer to execute any one of the methods described.

[0013] According to a third aspect of the present disclosure, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor executes the method described in any one implementation of the first aspect.

[0014] This embodiment is based on a cloud-native information processing method for application software, including receiving packaging information configured by a user for a service package in a visual configuration manner, packaging the service based on the packaging information to obtain a service image; packaging one or more service images associated with the application of the application software to build a service component image. Based on the rapid delivery and governance technology of JS application software, compared with other one-stop cloud platforms, it is based on the JS field, with concentrated user groups and similar application scenarios. While integrating cloud-native technology in one stop, it discards unnecessary functions, reduces user self-configuration operations, and avoids exposing underlying technical details. While reducing the freedom of some users, it greatly improves the usability of the product, reduces the learning cost and threshold for developers and operation and maintenance personnel, and enables business applications to be put on the cloud at zero cost. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the specific embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the specific embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0016] Figure 1 is a flow chart of an information processing method for application software based on cloud native according to an embodiment of the present disclosure;

[0017] Figure 2 is a service packaging flow chart of an embodiment of the present disclosure;

[0018] Figure 3 is an application packaging flow chart of an embodiment of the present disclosure;

[0019] Figure 4 is a visual deployment flow chart of an embodiment of the present disclosure;

[0020] Figure 5 is a schematic diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0021] In order to enable those skilled in the art to better understand the scheme of the present disclosure, the technical scheme in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in the field without creative work should fall within the scope of protection of the present disclosure.

[0022] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so as to describe the embodiments of the present disclosure described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0023] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present disclosure may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0024] According to an embodiment of the present disclosure, a cloud-native-based information processing method for application software is provided. Figure 1 As shown, it includes the following steps 101 to 102:

[0025] Step 101: receiving packaging information configured by a user for a service package in a visual configuration manner, and packaging the service based on the packaging information to obtain a service image.

[0026] In this embodiment, the packaging process is divided into two steps: service packaging and application packaging. This embodiment provides users with a visual packaging capability to compile the source code of an application into an image. Users only need to configure the service runtime environment, startup configuration, data source and other service package related information to complete the service packaging and build an Mpks package image that meets the standard. The image is stored in the image warehouse for service deployment. Service packaging builds the service software package into an Mpks image.

[0027] As an optional implementation method of this embodiment, receiving packaging information configured by a user for a service package in a visual configuration manner, and obtaining a service image after packaging based on the packaging information includes: determining a service packaging type from the configured packaging information, wherein the packaging type includes AI service packaging, microservice packaging, and image packaging; and executing different packaging methods for different packaging types.

[0028] As an optional implementation method of this embodiment, executing different encapsulation methods for different encapsulation types includes: for AI service encapsulation and microservice encapsulation, performing single instance configuration based on the configured encapsulation information; for image encapsulation, obtaining a general image selected by the user; after single instance configuration and selecting a general image, obtaining hardware platform information selected by the user, wherein the hardware platform information includes configuration file mounting information, data source information, startup command, environment variables, and persistent directory; obtaining user-configured publishing information; and publishing services based on the selected hardware platform information and publishing information.

[0029] In this optional implementation, reference Figure 2 When encapsulating services, for example, the encapsulation type configured by the user is obtained, which includes AI service encapsulation, image encapsulation, and microservice encapsulation. Under the image encapsulation type, the user-configured general image is obtained, and the configured hardware platform data is obtained, including but not limited to configuration file mounting information, data source information, startup command information, environment variable information, persistent directory information, etc., as well as information on whether the configuration needs to provide services separately to the outside world, and is published based on the filled-in and constructed publishing information.

[0030] Under the microservice packaging type, obtain the uploaded JAR or WAR package, and then obtain the operating environment JDK and the selected application server selected by the user, and then perform single instance configuration, obtain the configured hardware platform data, and whether it is necessary to provide services to the outside world separately, and then publish based on the filled-in build release information.

[0031] Under the AI ​​service encapsulation type, a single instance is configured based on the intelligent framework selected by the user, and then the configured hardware platform data and information on whether a separate service needs to be provided to the outside world are obtained, and then the service is published based on the published information filled in.

[0032] This embodiment provides users with the ability to compile application source code into a visual packaging image. Users can package service description information such as the service runtime environment, startup configuration, data source, etc., build business services into standard images, and store the images in the image warehouse for service deployment.

[0033] Step 102: Package one or more service images associated with the application program of the application software to construct a service composition image.

[0034] In this embodiment, the application encapsulation packages one or more service Mpks images that the application depends on into a service group Mpks image.

[0035] As an optional implementation method of this embodiment, packaging one or more service images associated with an application program of the application software to construct a service composition image includes: accepting a service image associated with the application program selected by a user through a visual configuration method, and pulling version information corresponding to the application program; obtaining content configured by the user for one or more associated service images through a visual configuration method; and encapsulating based on the configured content and version information.

[0036] In this optional implementation, reference Figure 3 When packaging the application, obtain the associated services selected by the user in the visual configuration interface, and configure the version pulling rules; then obtain the setting information of the application access entry service and the setting information of the application's external access port; further, obtain the version number and version description, obtain the configured application type, and finally complete the application release.

[0037] The new packaging standard - MPKS standard. MPKS packaging is different from other existing packaging formats. It customizes a set of standards that conform to the entire J and meet GJB requirements. It is mainly aimed at JAVA services. Through a simple visual interface reminder, users only need to fill in the information related to their service package to complete the packaging.

[0038] Unlike other cloud platforms, this solution proposes the Mpks packaging standard in order to allow users to focus only on their own business and not on the basic environment. This solution encapsulates the common dependencies required for software to be put on the cloud into a basic environment package, including the basic environment image of each hardware platform, the operating environment such as JDK, and application servers such as Tomcat\Kingdee. Users only need to upload the service software package through the visual interface and configure the environment information required for the software to run, including hardware platform, runtime environment, application server, database, external interface and other information. The platform will build these description information and software packages into an image in Mpks format. When the service is deployed, the platform pulls the basic environment package and starts the container. The business service Mpks image is deployed in the container. The container configures the basic environment that the service depends on according to the description information of the Mpks image and completes the startup of the service.

[0039] Developers do not need to understand containers, K8s and other related knowledge at all. They only need to focus on their own business services and achieve zero-threshold cloud migration.

[0040] As an optional implementation manner of this embodiment, the method further includes: obtaining deployment information configured by the user in a visual configuration manner, so as to deploy the encapsulated service based on the deployment information.

[0041] As an optional implementation of this embodiment, deploying the packaged service based on the deployment information includes: obtaining the target service and version selected by the user; obtaining the deployment location information selected by the user; and performing automatic deployment based on the target service and version and the deployment location information.

[0042] As an optional implementation method of this embodiment, the method for automated deployment includes: environment verification; configuration writing; performing service deployment after configuration writing is completed, wherein the service deployment includes domain name registration, and performing gateway configuration after successful registration; performing service registration after gateway configuration is completed; and completing deployment after service registration is completed.

[0043] In this optional implementation, users deploy services through a simple and easy-to-use visual interface, select the appropriate hardware platform, service characteristics, container parameters, cluster size, and application server type, and deploy the service using the Mpks package in the image repository. The service deployment process is fully visualized, including environment verification, domain partitioning, configuration writing, deployment submission, domain name registration, gateway configuration, service registration, and deployment, a total of 8 steps. Users can monitor the deployment progress and status in real time.

[0044] refer to Figure 4 , when deploying, obtain the target service and service version selected by the user, obtain the selected deployment location and enter the automated deployment process. The deployment location includes the deployment environment, deployment scale, database, and persistent directory. In automated deployment, the environment is verified and the configuration is written first, and then the service is deployed. Service deployment includes domain name registration, gateway configuration, and service registration. Domain name registration includes container creation, service creation, and route creation. Service deployment also includes startup status check, and deployment is completed after the check passes.

[0045] Furthermore, for elastic scaling: for services running normally on the cloud, users can set the service target CPU usage, target memory usage, minimum number of instances, and maximum number of instances through the visual interface prompts, complete the elastic scaling configuration strategy, and trigger the strategy when the threshold is exceeded. When faced with sudden service anomalies and surging data traffic, resources can be quickly allocated and adjusted according to business needs, and the number of service instances can be flexibly adjusted. The elastic speed is fast and the real-time performance is high, fully ensuring the efficient and stable operation of the business system.

[0046] For service governance and operation and maintenance: encapsulate the grayscale release of underlying technologies through a visual interface, configure non-essential information by default, and reduce user operations. Support continuous upgrades and iterations of business systems. When upgrading services, they can be upgraded in batches and rolled back in real time to reduce system upgrade risks. At the same time, the system data link can be monitored in real time to grasp the global status of the system and predict system stability risks.

[0047] Unified management of heterogeneous resources: In view of the current situation in which different units in the JS field use different equipment models, a high proportion of domestic equipment, and the gradual development of technologies in the intelligent and edge fields, it is adapted to multiple heterogeneous computing hardware platforms such as X86, Loongson, Feiteng, and Shenwei, and realizes the function of unified management of heterogeneous resources. It can automatically manage and schedule intelligent computing resources and edge computing resources in all aspects, shield the differences in underlying computing resources, and provide computing power support for complex information systems.

[0048] Based on the rapid delivery and governance technology of JS application software, compared with other one-stop cloud platforms, the present invention is based on the JS field, with concentrated user groups and similar application scenarios. While integrating cloud native technology in one stop, it discards unnecessary functions, reduces user self-configuration operations, and avoids exposing underlying technical details. While reducing the freedom of some users, it greatly improves the usability of the product, reduces the learning cost and threshold for developers and operation and maintenance personnel, and enables business applications to be put on the cloud at zero cost. At the same time, it conducts in-depth adaptation and optimization for the current mainstream domestic CPUs, operating systems, middleware, databases, etc., to provide users with a basic operating environment for business service hosting.

[0049] This embodiment reduces the difficulty of cloud migration: In order to avoid the complexity of cloud migration, numerous configurations, and redundant functions, this embodiment aims to reduce some degrees of freedom and improve the ease of use of cloud migration. The one-stop cloud native technology of the network information system architecture abandons unnecessary function display, uses more default configurations, reduces the exposure of underlying technical details, and provides a simpler and easier-to-use interface, so that developers only need to focus on their own application development, and do not need to understand containers, K8S and other related knowledge. Through a simple interface, users only need to focus on some configurations related to the business itself to complete service packaging, one-click deployment of services to the cloud, and visualization of the entire cloud migration process, which supports users to view the progress and status of cloud migration at any time, reduces the difficulty of cloud migration, and realizes zero threshold for developers to migrate to the cloud.

[0050] Reduce service operation and maintenance costs: With the development of all-J technology, all-J joint ZZ has also gradually transformed from the traditional model to a service-oriented and autonomous system based on a virtualized cloud architecture. Operation and maintenance personnel face difficulties such as high operation and maintenance difficulties and high operation and maintenance costs. This embodiment of a one-stop cloud native technology for the network information architecture allows users to improve the operation and maintenance capabilities of the networked resource environment through functions such as automatic fault recovery, automatic elastic scaling, and traffic monitoring based on the hosting platform, thereby improving the overall survivability and rapid response capabilities of the all-JJS information system, reducing the burden and increasing the efficiency of operation and maintenance support work.

[0051] Improve the stability of cloud services: The scope of use of JS applications is constantly expanding, and the types of business are increasing. The software is usually in a highly integrated state. The installation and upgrade operations that need to be completed for JS application software are often very complicated. In order to achieve continuous online services for JS application software, there are high requirements for the stability and reliability of the online software warehouse system. Therefore, the present invention proposes a one-stop cloud native technology for network information architecture. Through technical means such as dynamic expansion of the number of service nodes, request load balancing, operation monitoring, and traffic adjustment, the operating status of cloud services can be monitored and managed in real time, realizing the full life cycle management of cloud services while improving the high security, high stability, and high reliability of cloud services.

[0052] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0053] According to an embodiment of the present disclosure, a cloud-native information processing system for application software is also provided, including a service packaging module, which is configured to receive packaging information configured by a user for a service package in a visual configuration manner, so as to obtain a service image after packaging the service based on the packaging information; an application packaging module, which is configured to package one or more service images associated with an application program of the application software to construct a service composition image.

[0054] As an optional implementation method of this embodiment, receiving packaging information configured by a user for a service package in a visual configuration manner, and obtaining a service image after packaging based on the packaging information includes: determining a service packaging type from the configured packaging information, wherein the packaging type includes AI service packaging, microservice packaging, and image packaging; and executing different packaging methods for different packaging types.

[0055] As an optional implementation method of this embodiment, executing different encapsulation methods for different encapsulation types includes: for AI service encapsulation and microservice encapsulation, performing single instance configuration based on the configured encapsulation information; for image encapsulation, obtaining a general image selected by the user; after single instance configuration and selecting a general image, obtaining hardware platform information selected by the user, wherein the hardware platform information includes configuration file mounting information, data source information, startup command, environment variables, and persistent directory; obtaining user-configured publishing information; and publishing services based on the selected hardware platform information and publishing information.

[0056] As an optional implementation method of this embodiment, packaging one or more service images associated with an application program of the application software to construct a service composition image includes: accepting a service image associated with the application program selected by a user through a visual configuration method, and pulling version information corresponding to the application program; obtaining content configured by the user for one or more associated service images through a visual configuration method; and encapsulating based on the configured content and version information.

[0057] As an optional implementation of this embodiment, the device further includes a visual deployment unit configured to obtain deployment information configured by a user in a visual configuration manner, so as to deploy the encapsulated service based on the deployment information.

[0058] As an optional implementation of this embodiment, deploying the packaged service based on the deployment information includes: obtaining the target service and version selected by the user; obtaining the deployment location information selected by the user; and performing automatic deployment based on the target service and version and the deployment location information.

[0059] As an optional implementation method of this embodiment, an environment check is performed during automated deployment; configuration is written; service deployment is performed after configuration writing is completed, wherein the service deployment includes domain name registration, and gateway configuration is performed after successful registration; service registration is performed after gateway configuration is completed; and deployment is completed after service registration is completed.

[0060] As an optional implementation of this embodiment, after the configuration is written, the status check is started, and the service deployment is completed after the check passes.

[0061] The present disclosure provides an electronic device, such as Figure 5 As shown, the electronic device includes one or more processors 31 and a memory 32. Figure 5 A processor 31 is taken as an example.

[0062] The controller may further include: an input device 33 and an output device 34 .

[0063] The processor 31, the memory 32, the input device 33 and the output device 34 may be connected via a bus or other means. Figure 3 The example of connecting through bus is taken in the following.

[0064] The processor 31 may be a central processing unit (CPU). The processor 31 may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination of the above chips. A general-purpose processor may be a microprocessor or the processor may be any conventional processor.

[0065] The memory 32 is a non-transitory computer-readable storage medium that can be used to store non-transitory software programs, non-transitory computer executable programs and modules, such as program instructions / modules corresponding to the control method in the embodiment of the present disclosure. The processor 31 executes various functional applications and data processing of the server by running the non-transitory software programs, instructions and modules stored in the memory 32, that is, the enterprise data exchange method based on email in the above method embodiment is implemented.

[0066] The memory 32 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of a processing device operated by the server, etc. In addition, the memory 32 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 32 may optionally include a memory remotely arranged relative to the processor 31, and these remote memories may be connected to a network connection device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0067] The input device 33 can receive input digital or character information, and generate key signal input related to user settings and function control of the processing device of the server. The output device 34 can include display devices such as a display screen.

[0068] One or more modules are stored in the memory 32, and when executed by one or more processors 31, the execution is as follows: Figure 1 The method shown.

[0069] Those skilled in the art can understand that the implementation of all or part of the processes in the above-mentioned embodiment method is a program that can be completed by instructing related hardware through a computer program, which can be stored in a computer-readable storage medium. When the program is executed, it can include the process of the embodiment of the above-mentioned method. Among them, the storage medium can be a disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), a flash memory (Flash Memory), a hard disk (Hard Disk Drive, abbreviated: HDD) or a solid-state drive (SSD), etc.; the storage medium can also include a combination of the above-mentioned types of memory.

[0070] Although the embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A cloud-native information processing method for application software, characterized in that: include: Receiving packaging information configured by a user for a service package in a visual configuration manner, and packaging the service based on the packaging information to obtain a service image; One or more service images associated with the application program of the application software are packaged to build a service composition image.

2. The cloud-native application-oriented information processing method according to claim 1, characterized in that: Receiving encapsulation information configured by a user for a service package in a visual configuration manner, and encapsulating based on the encapsulation information to obtain a service image includes: Determine a service encapsulation type from the configured encapsulation information, wherein the encapsulation type includes AI service encapsulation, microservice encapsulation, and mirror encapsulation; Different packaging methods are implemented for different packaging types.

3. The cloud-native application-oriented information processing method according to claim 2, characterized in that: Different packaging methods are implemented for different packaging types, including: For AI service encapsulation and microservice encapsulation, single instance configuration is performed based on the configured encapsulation information; For image packaging, obtain the universal image selected by the user; After configuring a single instance and selecting a general image, obtaining the hardware platform information selected by the user, wherein the hardware platform information includes configuration file mounting information, data source information, startup commands, environment variables, and a persistent directory; Get the publishing information configured by the user; Service publishing is performed based on the selected hardware platform information and publishing information.

4. The cloud-native application-oriented information processing method according to claim 1, characterized in that: Packaging one or more service images associated with the application software to build a service component image includes: Accept the service image associated with the application selected by the user through visual configuration, and pull the version information corresponding to the application; Obtain the content of one or more associated service images configured by the user through visual configuration; Packaging is performed based on the configuration content and version information.

5. The cloud-native application-oriented information processing method according to claim 1, characterized in that: The method also includes: obtaining deployment information configured by the user in a visual configuration manner, so as to deploy the encapsulated service based on the deployment information.

6. The cloud-native application-oriented information processing method according to claim 5, characterized in that: Deploying the packaged service based on the deployment information includes: Get the target service and version selected by the user; Get the deployment location information selected by the user; Automatic deployment is performed based on the target service, version, and deployment location information.

7. The cloud-native application-oriented information processing method according to claim 5, characterized in that: When automating deployment, methods include: Environmental calibration; Configuration write; After the configuration is written, the service is deployed, wherein the service deployment includes domain name registration, and after successful registration, gateway configuration is performed; after the gateway configuration is completed, service registration is performed; after the service registration is completed, deployment is completed.

8. The cloud-native application-oriented information processing method according to claim 7, characterized in that: After the configuration is written, start the status check, and complete the service deployment after the check passes.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the method according to any one of claims 1 to 8.

10. An electronic device, characterized in that: include: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor executes the method described in any one of claims 1-8.

Images