Cloud-based native password application service management method and system

Abstract

The invention relates to the field of password application service management, in particular to a cloud native password application service management method and system. The method comprises the following steps of: refining and dividing a password application service into a plurality of independent function modules of data extraction, format filling, initialization vector extraction, key preparation and password function calling according to functions; the function module forms an independent password micro-service; a cloud native technology is adopted to realize management scheduling of a password micro-service cluster and password micro-services; the password micro-services are combined and are automatically arranged, deployed and monitored in real time on the basis of containers, and automatic recovery of password micro-service faults, automatic performance expansion and contraction and automatic alarm of insufficient resources are achieved; and a cloud native container management technology is adopted to realize online smooth upgrade of the password micro-service. Through deep integration of a cloud native technology and a password technology, clustering, manageability, expandability, high stability and high efficiency of a password application service in a cloud environment are realized by a password service.

Description

Technical Field

[0001] The present invention is based on the field of cloud-native cryptographic application service management, and in particular relates to a cloud-native cryptographic application service management method and system. Background Art

[0002] At present, big data and cloud computing technologies are widely used, and cloud-native technologies such as containerization and microservices are developing rapidly, providing technical guarantees for the rapid delivery, efficient deployment and risk feedback of software applications. Cryptography technology is the core technology to ensure the security of network information systems. At present, the integration of cryptography technology and cloud-native technology is still in its early stages and cannot give full play to the advantages of integration. With the development of related technologies, microservice component technology has shown obvious advantages in improving system management efficiency and system reliability. How to use microservice technology to improve the level of information system management and make the cryptographic service system efficient, stable and easy to adjust has positive research and development significance. Summary of the invention

[0003] In order to solve the above technical problems, the present invention proposes a cloud-native-based cryptographic application service management method and system to solve at least one of the above technical problems.

[0004] A cryptographic application service management method based on cloud native comprises the following steps: step S1, dividing the cryptographic application service into independent functional modules according to functions, wherein the independent functional modules include original data extraction, format filling, initialization vector extraction, key preparation and cryptographic function calling; step S2, forming the independent functional modules into independent cryptographic microservices, each of which is responsible for completing a task; step S3, adopting cloud native microservice registration and service discovery, dynamic configuration, service health monitoring, load balancing and traffic management technology to realize the management and scheduling of cryptographic microservice clusters and cryptographic microservices; step S4, combining the cryptographic microservices and automatically arranging, deploying and real-time monitoring based on containers to realize automatic recovery of cryptographic microservice faults, automatic performance scaling and automatic alarm of insufficient resources; step S5, adopting cloud native container management technology to realize smooth online upgrade of cryptographic microservices.

[0005] Preferably, step S1 comprises:

[0006] Based on the single function principle or high cohesion principle, the cryptographic application service is subdivided into five independent functional modules: original data extraction, format filling, initialization vector extraction, key preparation and cryptographic function call.

[0007] Preferably, step S3 comprises:

[0008] The microservice registration and service discovery are carried out through a service registration center, using a service registration and discovery mechanism, so that each microservice can dynamically find and communicate with each other;

[0009] The dynamic configuration is used to dynamically adjust the configuration parameters of the microservice without restarting the microservice;

[0010] The service health monitoring continuously monitors the operating status of each microservice;

[0011] The load balancing reasonably distributes requests for different service instances through a hardware load balancer or a software load balancer;

[0012] The traffic management manages and controls the traffic by adopting traffic control, current limiting and fuse strategies; through the above technologies, the management and scheduling of the cryptographic microservice cluster is realized.

[0013] Preferably, step S4 comprises:

[0014] Based on real-time monitoring of containers, container failures are discovered and the types of failures are identified. Based on the types of failures, corresponding failure recovery strategies are selected and executed to achieve automatic recovery of cryptographic microservice failures.

[0015] Use Kubernetes for container deployment, obtain the status information of container automation orchestration and deployment and the performance requirements of cryptographic microservices, automatically adjust the number of microservice instances or resource configuration, and realize automatic scaling of cryptographic microservice performance;

[0016] When the number of instances or resources cannot meet the current cryptographic microservice performance requirements, an automatic resource shortage alarm is issued.

[0017] Preferably, step S5 comprises:

[0018] Build an image, package the cryptographic application service into a Docker image, and run it on a platform that supports the Docker image;

[0019] Add, delete, and restart the password microservice through Kubernetes. In Kubernetes, create a Deployment to define the image version of the password microservice.

[0020] Online smooth upgrade: when a new password microservice version is available, the image version of the password microservice defined in the Deployment is updated; during the update process, if a problem is found in the new password microservice version, it will automatically roll back to the old password microservice version.

[0021] According to another embodiment of the present invention, a cloud-native-based cryptographic service management system is also provided, including:

[0022] Functional module segmentation module, which divides the cryptographic application service into independent functional modules according to its functions, and the independent functional modules include original data extraction, format filling, initialization vector extraction, key preparation and cryptographic function call;

[0023] A cryptographic microservice module forms independent cryptographic microservices from the independent functional modules, each of which is responsible for completing a task;

[0024] The management and scheduling module of the cryptographic microservice cluster adopts cloud-native microservice registration and service discovery, dynamic configuration, service health monitoring, load balancing, and traffic management technologies to achieve the management and scheduling of the cryptographic microservice cluster;

[0025] The cryptographic microservice function implementation module combines the cryptographic microservices and automatically arranges, deploys, and monitors them in real time based on containers to achieve automatic recovery of cryptographic microservice failures, automatic performance scaling, and automatic warning of insufficient resources;

[0026] The online upgrade module uses cloud-native container management technology to achieve smooth online upgrades of cryptographic microservices.

[0027] Preferably, the functional module segmentation module includes: based on the single function principle or the high cohesion principle, the cryptographic application service is segmented into five independent functional modules: original data extraction, format filling, initialization vector extraction, key preparation and cryptographic function call.

[0028] Preferably, the management and scheduling module of the cryptographic microservice cluster includes:

[0029] The microservice registration and service discovery are carried out through a service registration center, using a service registration and discovery mechanism, so that each microservice can dynamically find and communicate with each other;

[0030] The dynamic configuration is used to dynamically adjust the configuration parameters of the microservice without restarting the microservice;

[0031] The service health monitoring continuously monitors the operating status of each microservice;

[0032] The load balancing reasonably distributes requests for different service instances through a hardware load balancer or a software load balancer;

[0033] The traffic management manages and controls the traffic by adopting traffic control, current limiting and fuse strategies; through the above technologies, the management and scheduling of the cryptographic microservice cluster is realized.

[0034] Preferably, the cryptographic microservice function implementation module includes:

[0035] Based on real-time monitoring of containers, container failures are discovered and the types of failures are identified. Based on the types of failures, corresponding failure recovery strategies are selected and executed to achieve automatic recovery of cryptographic microservice failures.

[0036] Use Kubernetes for container deployment, obtain the status information of container automation orchestration and deployment and the performance requirements of cryptographic microservices, automatically adjust the number of microservice instances or resource configuration, and realize automatic scaling of cryptographic microservice performance;

[0037] When the number of instances or resources cannot meet the current cryptographic microservice performance requirements, an automatic resource shortage alarm is issued.

[0038] Preferably, the online upgrade module includes:

[0039] Build an image, package the cryptographic application service into a Docker image, and run it on a platform that supports the Docker image;

[0040] Add, delete, and restart the password microservice through Kubernetes. In Kubernetes, create a Deployment to define the image version of the password microservice.

[0041] Online smooth upgrade: when a new password microservice version is available, the image version of the password microservice defined in the Deployment is updated; during the update process, if a problem is found in the new password microservice version, it will automatically roll back to the old password microservice version.

[0042] According to yet another embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any one of the above method embodiments when run.

[0043] According to yet another embodiment of the present invention, there is provided an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0044] The purpose of the present invention is to provide a method for deeply integrating cloud native technology and cryptographic technology to solve the problems of clustering, manageability, scalability, high stability and high efficiency of cryptographic services in a cloud environment. Specifically, in a computing environment, the cryptographic service functions are refined and segmented to form the idea of ​​cryptographic microservices, and then cloud native technology is used to form a cloud native architecture for cryptographic services, so as to realize the integration, scheduling and management of cloud native cryptographic services, thereby improving the comprehensive capabilities of cryptographic services.

[0045] Compared with the prior art, the present invention has at least the following beneficial effects:

[0046] 1. The invented method of deep integration of cloud native technology and cryptographic technology is adopted to create a cloud native architecture for cryptographic application services, which enables each cryptographic functional module to have the characteristics of dynamic expansion, elastic scaling, stability and reliability, and realizes more efficient, stable, high-availability and higher resource utilization of multi-user and multi-business cryptographic services in the cloud environment.

[0047] 2. At the same time, through cloud-native container management technology and container service integration technology, the cryptographic microservices are encapsulated in lightweight and portable containers, making the development and operation and maintenance environments consistent, improving the portability and mutual isolation of cryptographic applications, and achieving a smooth transition of online upgrades of cryptographic service components.

[0048] 3. The cloud-native architecture of the cryptographic service can support multi-tenant and multi-region deployment of the cryptographic service, allowing applications to easily provide consistent cryptographic services in different ranges. The continuous integration and continuous delivery practices of the cryptographic service accelerate the delivery speed and quality of the cryptographic service software through the automated build, test and deployment process of the cryptographic service, and can quickly respond to business needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting implementations made with reference to the following drawings:

[0050] Figure 1 A flowchart of a method for managing cloud-native cryptographic application services is shown in accordance with an embodiment;

[0051] Figure 2 A specific process diagram of a cloud-native-based cryptographic application service management according to an embodiment is shown;

[0052] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0053] The following is a clear and complete description of the technical method of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by technicians in this field without creative work are within the scope of protection of the present invention.

[0054] In addition, the accompanying drawings are only schematic illustrations of the present invention and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. The functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor methods and / or microcontroller methods.

[0055] It should be understood that, although the terms "first", "second", etc. may be used herein to describe various units, these units should not be limited by these terms. These terms are used only to distinguish one unit from another unit. For example, without departing from the scope of the exemplary embodiments, the first unit may be referred to as the second unit, and similarly the second unit may be referred to as the first unit. The term "and / or" used herein includes any and all combinations of one or more of the listed associated items.

[0056] See also Figure 1 to Figure 2 , the present application provides a cloud-native-based cryptographic service management method, comprising the following steps:

[0057] Step S1, dividing the cryptographic application service into independent functional modules according to the functions, wherein the functional modules include original data extraction, format filling, initialization vector extraction, key preparation and cryptographic function calling;

[0058] Specifically, the segmentation of cryptographic application services into independent functional modules based on their functions is also commonly referred to as modular design, which is a common strategy in software development. It includes:

[0059] Raw data extraction: involves obtaining data that needs to be encrypted or decrypted from user input or other data sources. The main task of this module is to ensure the accuracy and integrity of the raw data.

[0060] Format filling: This module is mainly responsible for performing specific format processing on the original data, such as filling it to a specific byte length to meet the requirements of the encryption algorithm.

[0061] Initialization vector extraction: In some encryption modes (such as CBC mode), the initialization vector (IV) is used to increase the randomness of encryption to prevent the same data block from getting the same result after encryption. Extract the appropriate initialization vector through the initialization vector;

[0062] Key preparation: Responsible for generating, storing, managing and retrieving keys to ensure their security and effectiveness. The key is the core of the cryptographic algorithm and is used to encrypt and decrypt data. Responsible for generating, storing, managing and retrieving keys to ensure their security and effectiveness;

[0063] Cryptographic function call: This is the part that actually performs the encryption or decryption operation. Depending on the needs, this module may call various cryptographic algorithms, such as AES, RSA, etc., and combine the original data, format, initialization vector and key provided by the previous module to complete the task.

[0064] This modular design makes cryptographic application services easier to understand and maintain. Each module has clear responsibilities and can be independently tested and optimized. It also makes it easy to add new cryptographic algorithms or functions.

[0065] Step S2: The independent functional modules form independent cryptographic microservices, and each of the cryptographic microservices is responsible for completing a task;

[0066] Specifically, cloud native is a method of building and running applications, a set of technical systems and methodologies. Cloud Native is a combination of words, 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, is natively designed for the cloud, runs in the cloud in the best posture, and fully utilizes and gives play to the elasticity and distributed advantages of the cloud platform. Cloud native consists of four elements: DevOps, continuous delivery, microservices, and containers. Cloud native has the characteristics of starting from the beginning, integrating operation and maintenance, narrowing the developer's cognition, flexible development direction, stronger cohesion, more agility, and easier resource scheduling and microservices. In this design, each independent functional module is encapsulated as a separate "microservice", and each microservice has its specific responsibilities or tasks, such as managing user passwords, encrypting and decrypting data, etc. Such a design has the following advantages:

[0067] Scalability: Each microservice can be deployed and scaled independently without affecting other services.

[0068] Maintainability: Because each service is relatively small and focused on a single task, the code is easier to understand and maintain.

[0069] Fault isolation: If a microservice fails, it will not affect the entire system, but only the functionality of that service.

[0070] Technology diversity: Different microservices can choose the technology stack that best suits their tasks.

[0071] This design can make password management more secure and efficient.

[0072] Step S3: adopt cloud-native microservice registration and service discovery, dynamic configuration, service health monitoring, load balancing, and traffic management technologies to achieve management and scheduling of cryptographic microservice clusters and cryptographic microservices;

[0073] Specifically, the specific execution of step S3 can be divided into the following sub-steps:

[0074] Microservice registration and service discovery: In a cloud-native environment, each microservice needs to be registered in the registry so that other services can discover and communicate with it. For example, you can use tools such as Eureka, Consul, or Nacos as a registry. When a microservice instance starts, it reports its existence to the registry and sends heartbeats periodically to prove that it is still running. Other services can find and connect to the required services through the registry.

[0075] Dynamic configuration: Dynamic configuration of microservices is achieved through a configuration center (such as Spring Cloud Config or Apollo), allowing the configuration of services to be updated at runtime without restarting the service. This allows us to respond quickly to business changes and improve the flexibility of the system.

[0076] Service health monitoring: Use a health check mechanism (such as Spring Boot Actuator or Prometheus) to monitor the status of microservices. If a service instance has a problem, the registry will be able to detect it and stop sending new requests to it to ensure the stability of the system.

[0077] Load balancing: In a microservice architecture, there are usually multiple instances of the same service running to provide high availability. Load balancers (such as Netflix Zuul, Spring Cloud Gateway, or Kubernetes Ingress) distribute requests to these instances to avoid overloading a single instance and improve system performance.

[0078] Traffic management: Traffic management through API gateways (such as Zuul, Kong, or Envoy) can implement routing rules, circuit breakers, current limiting, degradation and other strategies to protect microservice systems from sudden traffic shocks and ensure service stability and availability.

[0079] The above steps are all aimed at building an efficient, stable, and scalable microservice architecture, so that the cryptographic microservice cluster can be dynamically expanded according to demand and can effectively manage and schedule each microservice.

[0080] Step S4, combining the cryptographic microservices and automatically arranging, deploying, and real-time monitoring based on containers to achieve automatic recovery of cryptographic microservice failures, automatic performance scaling, and automatic warning of insufficient resources;

[0081] Specifically, step S4 can be divided into the following sub-steps:

[0082] Containerization: Cryptography microservices need to be containerized. This means packaging each microservice into a separate container, each of which contains all the dependencies required to run the service. This is usually done using tools such as Docker.

[0083] Automated orchestration: Use container orchestration tools such as Kubernetes or Docker Swarm to manage these containers. These tools can automatically handle the life cycle of containers, including starting, stopping, scaling, and updating services. In Kubernetes, you can create a Deployment to define the number of replicas of a microservice, as well as when and how to update the service.

[0084] Deployment: Deploy these containers into a production environment. This can be done by submitting a configuration file to an orchestration system, which automatically creates and runs the required containers in the cluster.

[0085] Real-time monitoring: Integrate monitoring tools (such as Prometheus, Grafana, ELK stack or Elastic APM) to monitor the performance and status of microservices in real time. This can help us understand the health of the service, including response time, error rate, resource usage, etc.

[0086] Automatic fault recovery: Set monitoring rules. When a microservice failure is detected, the orchestration system can automatically restart the failed container or instance to ensure high availability of the service.

[0087] Automatic performance scaling: Automatic scaling policies can be set based on business load. For example, if the CPU or memory usage reaches a preset threshold, the orchestration system can automatically increase the number of service instances; conversely, when the load decreases, instances can be reduced to save resources.

[0088] Automatic alerts for insufficient resources: If system resources (such as CPU, memory, or disk space) are insufficient, monitoring tools can send alert notifications so that timely actions can be taken, such as increasing resources or optimizing services.

[0089] The above is the specific implementation process of step S4, which ensures the stable operation of the cryptographic microservice and can automatically adjust according to demand and environmental changes.

[0090] Step S5: Use cloud-native container management technology to achieve smooth online upgrade of cryptographic microservices;

[0091] Specifically, cloud-native container management technologies, such as Kubernetes (K8s) or Docker Swarm, can easily implement smooth online upgrades of microservices. The following are the basic steps:

[0092] Build the image: First, you need to package your password microservice application code into a Docker image. Define your application environment and dependencies in the Dockerfile, and then use the docker build command to create the image.

[0093] Configure deployment: In Kubernetes, you can create a Deployment to manage your microservice instances. In the Deployment configuration file, you can define the number of service replicas, update strategy, etc.

[0094] Set up rolling updates: In the Deployment configuration, you can set up rolling updates. A rolling update will gradually replace old Pods after starting new Pods (container instances) and confirming their normal operation, thus ensuring service continuity and stability.

[0095] Trigger updates: When you have a new version of the cryptographic microservice, you only need to update the image version of the Deployment. Kubernetes will automatically pull the new image and perform rolling updates according to the strategy you set.

[0096] Monitor the upgrade process: During the upgrade process, you can monitor the upgrade status through the Kubernetes Dashboard or command-line tools (such as kubectl) to ensure that all instances have been successfully updated and that services are not interrupted.

[0097] Rollback: If there is a problem with the new version, Kubernetes also supports quick rollback to the previous stable version.

[0098] The object of the present invention is to provide a cloud-native based cryptographic service management system, the system comprising:

[0099] Functional module segmentation module, which divides the cryptographic application service into independent functional modules according to its functions, including original data extraction, format filling, initialization vector extraction, key preparation and cryptographic function call;

[0100] A cryptographic microservice module forms independent cryptographic microservices from the independent functional modules, each of which is responsible for completing a task;

[0101] The management and scheduling module of the cryptographic microservice cluster adopts cloud-native microservice registration and service discovery, dynamic configuration, service health monitoring, load balancing, and traffic management technologies to achieve the management and scheduling of the cryptographic microservice cluster;

[0102] The cryptographic microservice function implementation module combines the cryptographic microservices and automatically arranges, deploys, and monitors them in real time based on containers to achieve automatic recovery of cryptographic microservice failures, automatic performance scaling, and automatic warning of insufficient resources;

[0103] The online upgrade module uses cloud-native container management technology to achieve smooth online upgrades of cryptographic microservices.

[0104] The present application also provides a system based on the deep integration of cloud native and cryptographic application services, the system comprising: Functional module segmentation: the system decomposes the cryptographic application service into multiple independent functional modules, such as original data extraction, format filling, initialization vector extraction, key preparation and cryptographic function call, etc. This modular design is conducive to improving the readability and maintainability of the code. Cryptographic microservice: each functional module is converted into an independent cryptographic microservice, and each microservice focuses on performing specific tasks, which can improve the flexibility and scalability of the service.

[0105] Management and Scheduling Module: Using cloud-native technologies, such as microservice registration and service discovery, dynamic configuration, health checks, load balancing, and traffic management, the cryptographic microservice cluster is efficiently managed to ensure the stability and reliability of the service. Microservice Function Implementation: Through automated container orchestration and deployment, the running status of the cryptographic microservice is monitored in real time to achieve automatic fault recovery, automatic performance scaling, and automatic alarms when resources are insufficient, thus improving the system's self-healing capabilities and resource utilization. Online Upgrade Module: With the help of cloud-native container management technology, the cryptographic microservice can be upgraded smoothly online without downtime, ensuring service continuity and reducing operation and maintenance costs.

[0106] Such a system design aims to provide an efficient, flexible, scalable and easy-to-maintain cryptographic service management platform that can adapt to the high concurrency and high availability requirements in cloud computing environments.

[0107] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0108] An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0109] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0110] An embodiment of the present invention further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0111] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0112] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.

[0113] Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0114] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A cloud-native cryptographic application service management method, characterized in that: The following steps are involved: Step S1, dividing the cryptographic application service into independent functional modules according to the functions, wherein the independent functional modules include original data extraction, format filling, initialization vector extraction, key preparation and cryptographic function calling; Step S2: The independent functional modules are formed into multiple independent cryptographic microservices, each of which is responsible for completing a task; Step S3: adopt cloud-native microservice registration and service discovery, dynamic configuration, service health monitoring, load balancing, and traffic management technologies to achieve management and scheduling of cryptographic microservice clusters and cryptographic microservices; Step S4, combining the cryptographic microservices and automatically arranging, deploying, and real-time monitoring based on containers to achieve automatic recovery of cryptographic microservice failures, automatic performance scaling, and automatic warning of insufficient resources; Step S5: Use cloud-native container management technology to achieve smooth online upgrade of cryptographic microservices.

2. The method according to claim 1, characterized in that Step S1 includes: based on the single function principle or the high cohesion principle, the cryptographic application service is subdivided into a plurality of independent functional modules including original data extraction, format filling, initialization vector extraction, key preparation and cryptographic function calling.

3. The method according to claim 1, characterized in that The step S3 comprises: The microservice registration and service discovery are carried out through a service registration center, using a service registration and service discovery mechanism, so that each microservice can dynamically find and communicate with each other; The dynamic configuration is used to dynamically adjust the configuration parameters of the microservice without restarting the microservice; The service health monitoring continuously monitors the operating status of each microservice; The load balancing reasonably distributes requests for different service instances through a hardware load balancer or a software load balancer; The traffic management manages and controls the traffic by adopting traffic control, current limiting and fuse strategies; through the above technologies, the management and scheduling of the cryptographic microservice cluster is realized.

4. The method according to claim 1, characterized in that Step S4 includes: Based on real-time monitoring of containers, container failures are discovered and the types of failures are identified. Based on the types of failures, corresponding failure recovery strategies are selected and executed to achieve automatic recovery of cryptographic microservice failures. Use Kubernetes for container deployment, obtain the status information of container automation orchestration and deployment and the performance requirements of cryptographic microservices, automatically adjust the number of microservice instances or resource configuration, and realize automatic scaling of cryptographic microservice performance; When the number of instances or resources cannot meet the current cryptographic microservice performance requirements, an automatic resource shortage alarm is issued.

5. The method according to claim 1, characterized in that Step S5 includes: Build an image, package the cryptographic application service into a Docker image, and run it on a platform that supports the Docker image; Add, delete, and restart the password microservice through Kubernetes. In Kubernetes, create a Deployment to define the image version of the password microservice; Online smooth upgrade: when a new password microservice version is available, the image version of the password microservice defined in the Deployment is updated; during the update process, if a problem is found in the new password microservice version, it will automatically roll back to the old password microservice version.

6. A cloud-native cryptographic application service management system, characterized in that: include: Functional module segmentation module, which divides the cryptographic application service into independent functional modules according to its functions, and the independent functional modules include original data extraction, format filling, initialization vector extraction, key preparation and cryptographic function call; A cryptographic microservice module forms independent cryptographic microservices from the independent functional modules, each of which is responsible for completing a task; The management and scheduling module of the cryptographic microservice cluster adopts cloud-native microservice registration and service discovery, dynamic configuration, service health monitoring, load balancing, and traffic management technologies to achieve the management and scheduling of the cryptographic microservice cluster; The cryptographic microservice function implementation module combines the cryptographic microservices and automatically arranges, deploys, and monitors them in real time based on containers to achieve automatic recovery of cryptographic microservice failures, automatic performance scaling, and automatic warning of insufficient resources; The online upgrade module uses cloud-native container management technology to achieve smooth online upgrades of cryptographic microservices.

7. The system according to claim 6, characterized in that The functional module segmentation module includes: based on the single function principle or the high cohesion principle, the cryptographic application service is segmented into multiple independent functional modules including original data extraction, format filling, initialization vector extraction, key preparation and cryptographic function calling.

8. The system according to claim 6, characterized in that The management and scheduling module of the cryptographic microservice cluster includes: The microservice registration and service discovery are carried out through a service registration center, using a service registration and discovery mechanism, so that each microservice can dynamically find and communicate with each other; The dynamic configuration is used to dynamically adjust the configuration parameters of the microservice without restarting the microservice; The service health monitoring continuously monitors the operating status of each microservice; The load balancing reasonably distributes requests for different service instances through a hardware load balancer or a software load balancer; The traffic management manages and controls the traffic by adopting traffic control, current limiting and fuse strategies; through the above technologies, the management and scheduling of the cryptographic microservice cluster is realized.

9. The system according to claim 6, characterized in that The cryptographic microservice function implementation module includes: Based on real-time monitoring of containers, container failures are discovered and the types of failures are identified. Based on the types of failures, corresponding failure recovery strategies are selected and executed to achieve automatic recovery of cryptographic microservice failures. Use Kubernetes for container deployment, obtain the status information of container automation orchestration and deployment and the performance requirements of cryptographic microservices, automatically adjust the number of microservice instances or resource configuration, and realize automatic scaling of cryptographic microservice performance; When the number of instances or resources cannot meet the current cryptographic microservice performance requirements, an automatic resource shortage alarm is issued.

10. The system according to claim 6, characterized in that The online upgrade module includes: Build an image, package the cryptographic application service into a Docker image, and run it on a platform that supports the Docker image; Add, delete, and restart the password microservice through Kubernetes. In Kubernetes, create a Deployment to define the image version of the password microservice; Online smooth upgrade: when a new password microservice version is available, the image version of the password microservice defined in the Deployment is updated; during the update process, if a problem is found in the new password microservice version, it will automatically roll back to the old password microservice version.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program is configured to execute the method according to any one of claims 1 to 5 when executed.

12. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to run the computer program to perform the method according to any one of claims 1 to 5.

Images