Quality evaluation method and apparatus for cloud service architecture

Abstract

Disclosed in the embodiments of the present application are a quality evaluation method for a cloud service architecture, which method is used for improving the design quality of a cloud service architecture. The method in the embodiments of the present application comprises: presenting a cloud architecture diagram, which represents a cloud service architecture and includes a first cloud primitive and a second cloud primitive, wherein the first cloud primitive corresponds to a first cloud service, the second cloud primitive corresponds to a second cloud service, and the first cloud service and second cloud service in the cloud service architecture have an integration relationship; evaluating the integration relationship between the first cloud service and the second cloud service on the basis of at least one of the following information: types of the first cloud service and the second cloud service, communication modes of the first cloud service and the second cloud service, and communication content of the first cloud service and the second cloud service; and presenting to a user an evaluation result of the integration relationship between the first cloud service and the second cloud service.

Description

A quality assessment method and device for cloud service architecture

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 21, 2023, with application number 202311225944.4, and invention name “A method, system and device for cloud architecture evaluation”, and the Chinese patent application filed with the State Intellectual Property Office of China on January 22, 2024, with application number 202410088954.6, and invention name “A method and device for quality assessment of cloud service architecture”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present invention relates to the field of computers, and more particularly to a method and apparatus for evaluating the quality of a cloud service architecture. Background Art

[0003] With the rapid development of cloud computing, more and more enterprises are choosing to use cloud computing technology to solve their business problems. Cloud vendors offer a wide variety of cloud services, including hundreds of basic cloud services. When enterprises use cloud computing to solve their business problems, they don't necessarily need to use all of these cloud services. Typically, solution architects select a subset of these basic cloud services for integration, design a cloud service architecture, and ultimately develop a solution to solve their business problems.

[0004] However, designing a cloud service architecture for a solution is a highly experience-based task, often requiring highly experienced architects to craft a high-quality solution architecture. Architects must have a comprehensive understanding of all cloud service features, applicable scenarios, specifications, performance, and differences and limitations compared to similar cloud services. Furthermore, the integration relationships between cloud services are complex, and updates are frequent. Designers must maintain a real-time understanding of cloud services and their integration relationships to deliver a high-quality architecture design.

[0005] Currently, after solution architects complete solution design, they need to conduct quality assessment and solution verification on the cloud service architecture to ensure that the final delivered solution meets the requirements. The current cloud service architecture quality assessment process relies on experienced architects to conduct the assessment, which takes a long time and is often incomplete, resulting in poor solution design results for the cloud service architecture.

[0006] Summary of the Invention

[0007] Embodiments of the present application provide a cloud service architecture quality assessment method, in which a computing device can perform a quality assessment on a cloud service architecture designed by an architect based on an integration relationship knowledge graph and provide recommended integration relationships for the cloud service architecture, thereby improving the design quality and efficiency of the cloud service architecture. Embodiments of the present application also provide a cloud service architecture quality assessment apparatus, computing device, computing device cluster, computer-readable storage medium, and computer program product corresponding to the cloud service architecture quality assessment method.

[0008] In a first aspect, embodiments of the present application provide a method for assessing the quality of a cloud service architecture. The method can be executed by a computing device of a cloud service platform, or by a component of the computing device, such as a processor, chip, or chip system of the computing device, or by a logic module or software capable of implementing all or part of the computing device's functionality. The method provided in the first aspect includes: the computing device displays a cloud architecture editing interface, the cloud architecture editing interface including at least one element selection area, the element selection area including at least one cloud element, each cloud element corresponding to at least one cloud service. The computing device obtains an element selection instruction from a user for a first cloud element, the first cloud element corresponding to a first cloud service. The computing device obtains an element selection instruction from a user for a second cloud element, the second cloud element corresponding to a second cloud service. The computing device displays a cloud architecture diagram, the cloud architecture diagram representing the cloud service architecture, the cloud architecture diagram including a first cloud element and a second cloud element, the first cloud service and the second cloud service in the cloud service architecture having an integrated relationship, the integrated relationship being expressed by at least one of the following: a connection between the first cloud element and the second cloud element in the cloud architecture diagram, or an inclusion relationship between the first cloud element and the second cloud element in the cloud architecture diagram. The computing device evaluates the integration relationship between the first cloud service and the second cloud service based on at least one of the following information: types of the first cloud service and the second cloud service, communication methods of the first cloud service and the second cloud service, and communication content between the first cloud service and the second cloud service, where the communication content between the first cloud service and the second cloud service includes at least one of the following: data content communicated between the first cloud service and the second cloud service, and a data format communicated between the first cloud service and the second cloud service; and the communication methods between the first cloud service and the second cloud service include at least one of the following: a communication protocol between the first cloud service and the second cloud service, and a communication path between the first cloud service and the second cloud service. The computing device displays the evaluation result of the integration relationship between the first cloud service and the second cloud service to a user.

[0009] In the embodiment of the present application, the computing device can provide a cloud architecture editing interface for designing a cloud service architecture, perform a quality assessment on the cloud service architecture designed by the user based on relevant information of the cloud service architecture, and display the integration relationship assessment results of the cloud service architecture, so that the user can update the cloud service architecture based on the integration relationship assessment results, thereby improving the design quality of the cloud service architecture.

[0010] In one possible implementation, a computing device provides a dependency evaluation result between a first cloud service and a third cloud service based on dependency information. The third cloud service may be a cloud service that a user is designing. The dependency information includes at least one of the following: a strong dependency and a recommended dependency. A strong dependency means that the first cloud service and at least one of the first cloud services exist as a bundled copy of another cloud service. A recommended dependency means that at least one of the first cloud service and the second cloud service is recommended to coexist with the other cloud service. The computing device displays the dependency evaluation result between the first cloud service and the third cloud service to the user. The dependency evaluation result includes at least one of the following: a lack of at least one cloud service and a recommendation to add at least one cloud service.

[0011] In the embodiment of the present application, the computing device can perform dependency evaluation on the cloud service architecture designed by the user based on the dependency information of the cloud service architecture, and display the dependency evaluation results of the cloud service architecture, so that the user can update the cloud service architecture based on the content of the dependency evaluation results, thereby improving the design quality of the cloud service architecture.

[0012] In one possible implementation, while evaluating the integration relationship between a first cloud service and a second cloud service, the computing device parses the cloud service architecture to obtain the integration relationships of the cloud services included in the cloud service architecture. Based on the integration relationships of the cloud services, the computing device searches the integration relationship knowledge graph to determine associated integration relationships. The associated integration relationships are used to determine the evaluation results of the cloud service integration relationships. The integration relationship knowledge graph is used to store the integration relationships between different cloud services.

[0013] In the embodiment of the present application, the computing device is capable of parsing the integration relationship of cloud services in the cloud service architecture, and comparing the associated integration relationship in the relationship knowledge graph with the integration relationship of the cloud services obtained by parsing, thereby obtaining a quality assessment result of the integration relationship of multiple cloud services in the cloud service architecture, thereby improving the design quality of the cloud service architecture.

[0014] In one possible implementation, a computing device constructs an integrated relationship knowledge graph based on integrated relationship data. The integrated relationship knowledge graph includes nodes and edges. Nodes are used to represent cloud services, and edges are used to represent integrated relationships between cloud services. The cloud service integrated relationship data includes historical integrated relationship data of different cloud services.

[0015] In the embodiment of the present application, the computing device can construct a knowledge graph of the integration relationship based on the historical integration relationship data of the cloud service, and perform a quality assessment of the cloud service architecture based on the knowledge graph, thereby improving the accuracy of the integration relationship knowledge graph and the feasibility of the computing device in performing the cloud service architecture assessment.

[0016] In a possible implementation, the integration relationship evaluation result includes one or more of the following: unknown integration relationship, prohibited integration relationship, not recommended integration relationship, optional integration relationship, and preferred integration relationship.

[0017] The integration relationship evaluation results generated by the computing device in the embodiment of the present application include multiple different types of integration relationship evaluation results, thereby improving the accuracy of the quality evaluation results of the cloud service architecture.

[0018] In one possible implementation, when the integration relationship evaluation result is that the integration relationship is prohibited or the integration relationship is not recommended, the computing device displays the reasons why the integration relationship is prohibited or not recommended to the user. The computing device can also display modification suggestions corresponding to the prohibition of the integration relationship or the non-recommendation of the integration relationship to the user.

[0019] In the embodiment of the present application, the computing device can also display the evaluation reasons and modification suggestions corresponding to the integrated relationship evaluation results, thereby improving the integrity of the quality evaluation results.

[0020] In a possible implementation, there is a mapping relationship between the integration relationship evaluation result and the integration relationship quality score, and the recommendation degree in the integration relationship evaluation result is associated with the integration relationship quality score.

[0021] In the embodiment of the present application, the computing device generates a cloud service architecture corresponding to each cloud service integration relationship included in the quality score, thereby improving the accuracy of the quality assessment results of the cloud service architecture.

[0022] In one possible implementation, a computing device provides a quality assessment call interface for evaluating integration relationships across different cloud service architectures. The computing device receives an integration relationship evaluation request through the quality assessment call interface and sends an integration relationship evaluation result corresponding to the integration relationship evaluation request through the quality assessment call interface.

[0023] In the embodiment of the present application, the computing device provides a quality assessment calling interface on the display interface, so that the user can call the quality assessment calling interface in real time during the design process of the cloud service architecture to generate the quality assessment results of the cloud service architecture, thereby improving the real-time and evaluation efficiency of the quality assessment of the cloud service architecture.

[0024] In one possible implementation, if the integration relationship quality score corresponding to the integration relationship evaluation result is greater than a score threshold, the cloud service architecture is revised. If the integration relationship quality score corresponding to the integration relationship evaluation result is less than or equal to the score threshold, the cloud service architecture is submitted for cloud service architecture review and cloud service architecture verification.

[0025] In the embodiment of the present application, after the quality assessment result of the cloud service architecture is qualified, the computing device can perform cloud service architecture review and cloud service architecture verification on the cloud service architecture, thereby further improving the design quality of the cloud service architecture.

[0026] In one possible implementation, the computing device displays a recommended integration relationship, the recommended integration relationship includes at least two cloud services, and an evaluation result of the recommended integration relationship is better than an evaluation result of the integration relationship of the first cloud service and the second cloud service.

[0027] In the embodiment of the present application, the computing device can provide recommended integration relationships, and the evaluation results of the recommended integration relationships are better than the evaluation results of the currently designed integration relationships, thereby improving the design quality of the cloud service integration relationships.

[0028] In one possible implementation, a computing device displays a recommended integration relationship set, which includes a first recommended integration relationship and a second recommended integration relationship. In the recommended integration relationship set, the first recommended integration relationship is displayed better than the second recommended integration relationship, and the evaluation result of the first recommended integration relationship is better than the evaluation result of the second recommended integration relationship, that is, the recommended integration relationships in the recommended integration relationship set can be displayed in order of recommendation procedures.

[0029] In the embodiment of the present application, the computing device can provide multiple groups of recommended integration relationships to form a recommended integration relationship set, and recommend and sort the recommended integration relationships in the recommended integration relationship set according to the integration relationship evaluation results, thereby improving the design quality of the cloud service integration relationship.

[0030] In the second aspect, an embodiment of the present application also provides a quality assessment method for a cloud service architecture, which can be executed by a computing device of a cloud service platform, or by a component of a computing device, such as a processor, chip or chip system of a computing device, or by a logic module or software that can implement all or part of the functions of the computing device. The method provided in the second aspect includes: obtaining a cloud service architecture, where the cloud service architecture is a cloud service architecture created by a user on a cloud service platform. A quality assessment is performed on the cloud service architecture based on an integration relationship knowledge graph to generate a quality assessment result. The integration relationship knowledge graph is used to indicate the integration rules between different cloud services, and the integration rules include one or more of the following: integration relationship type and integration priority. The quality assessment result is displayed on the display interface of the cloud service platform, and the quality assessment result is used to indicate the score of one or more integration relationships in the cloud service architecture.

[0031] In the embodiment of the present application, the computing device can perform quality assessment on the cloud service architecture designed by the user based on the integrated relational knowledge graph, and display the quality assessment results of the cloud service architecture through a display interface. The user can update the designed cloud service architecture based on the quality assessment results of the cloud service architecture, thereby improving the design quality and design efficiency of the cloud service architecture.

[0032] In one possible implementation, during a quality assessment of a cloud service architecture based on an integration relationship knowledge graph, a computing device parses the cloud service architecture's integration relationships to obtain the integration relationships of cloud services within the cloud service architecture. Based on the cloud service integration relationships, the integration relationship knowledge graph is searched to determine associated integration relationships within the integration relationship knowledge graph. The associated integration relationships are used to assess the design quality of the cloud service integration relationships. A quality assessment result is generated based on the associated integration relationships and the cloud service integration relationships.

[0033] In the embodiment of the present application, the computing device is capable of parsing the integration relationship of cloud services in the cloud service architecture, and comparing the associated integration relationship in the relationship knowledge graph with the integration relationship of the cloud services obtained by parsing, thereby obtaining a quality assessment result of the integration relationship of multiple cloud services in the cloud service architecture, thereby improving the design quality of the cloud service architecture.

[0034] In one possible implementation, a computing device constructs an integrated relationship knowledge graph based on integrated relationship data. The integrated relationship knowledge graph includes nodes and edges. The nodes are used to represent cloud services, and the edges are used to represent the integrated relationships between cloud services. The cloud service integrated relationship data includes historical data of the cloud service integrated relationships.

[0035] In the embodiment of the present application, the computing device can construct a knowledge graph of the integration relationship based on the historical data of the cloud service integration relationship, and perform a quality assessment of the cloud service architecture based on the knowledge graph, thereby improving the accuracy of the integration relationship knowledge graph and the feasibility of the computing device in performing the cloud service architecture assessment.

[0036] In one possible implementation, cloud services include multiple different types of cloud services, including computing cloud services, container cloud services, storage cloud services, and network cloud services. Computing cloud services include Elastic Cloud Servers (ECS), Bare Metal Servers (BMS), and Image Service (IMS); container cloud services include Cloud Container Engine (CCE) and Container Image Service (SWR); storage cloud services include EVS, Elastic File Service (SFS), and Object Storage Service (OBS); and network cloud services include Virtual Private Cloud (VPC), Elastic Internet Protocol (EIP), Elastic Load Balancer (ELB), and Network Address Translation (NAT).

[0037] The cloud services in the embodiments of the present application include a variety of different types of cloud services, and the computing device can perform quality assessment on the cloud service architectures of different types of cloud services, thereby improving the applicability of the cloud service architecture quality assessment method.

[0038] In one possible implementation, a computing device may define integration relationship types in a knowledge graph. The cloud service integration relationship types in the knowledge graph include main types and subtypes. The main types include network protocol integration, data storage integration, middleware integration, dependency integration, and other integrations. Subtypes of the network protocol integration main type include TCP / UDP protocol integration and HTTP protocol integration, and subtypes of the data storage integration main type include object storage integration, file storage integration, and block storage integration.

[0039] In the embodiment of the present application, the computing device can define the integration relationship type in the knowledge graph, and further generate the knowledge spectrum of the integration relationship based on the integration relationship type, thereby improving the accuracy of the integration relationship knowledge graph.

[0040] In one possible implementation, the quality assessment results include one or more of the following: unknown integration relationship, prohibited integration relationship, not recommended integration relationship, optional integration relationship, and preferred integration relationship. Different quality assessment results correspond to different quality scores. The cloud service architecture assessment result and the quality score may be positively or negatively correlated, without limitation.

[0041] The quality assessment results generated by the computing device in the embodiment of the present application include multiple different types of quality assessment results, thereby improving the accuracy of the quality assessment results of the cloud service architecture.

[0042] In one possible implementation, a quality assessment result of each integration relationship in the cloud service architecture may correspond to a quality score, and the computing device may calculate the total quality score of the cloud service architecture based on the integration relationships included in the cloud service architecture.

[0043] In the embodiment of the present application, the computing device generates a cloud service architecture corresponding to each cloud service integration relationship included in the quality score, thereby improving the accuracy of the quality assessment results of the cloud service architecture.

[0044] In one possible implementation, a computing device provides a quality assessment call interface on a display interface. The quality assessment call interface is used to provide real-time quality assessment results of integration relationships within the cloud service architecture during the design process. During the design process, the computing device can call this quality assessment call interface in real time to perform a quality assessment on the cloud service architecture being designed and generate quality assessment results.

[0045] In the embodiment of the present application, the computing device provides a quality assessment calling interface on the display interface, so that the user can call the quality assessment calling interface in real time during the design process of the cloud service architecture to generate the quality assessment results of the cloud service architecture, thereby improving the real-time and evaluation efficiency of the quality assessment of the cloud service architecture.

[0046] In one possible implementation, the computing device provides a recommended integration relationship of the cloud service architecture on a display interface based on a quality assessment calling interface, and the recommended integration relationship is determined based on an integration relationship knowledge graph.

[0047] In the embodiment of the present application, in addition to performing a quality assessment on the cloud service architecture, the computing device can also provide a recommended integration relationship of the cloud service architecture on the display interface. Users can design the cloud service architecture based on the recommended integration relationship, thereby improving the design quality and efficiency of the cloud service architecture.

[0048] In one possible implementation, the computing device provides cloud primitives corresponding to recommended integration relationships on a display interface based on a quality assessment call interface. Users can design cloud service architectures based on the cloud primitives provided in the user interface. When users select cloud primitives to create a cloud service architecture, the computing device can display the quality assessment results of the integration relationship between the created cloud service and the cloud primitive on the display interface.

[0049] In an embodiment of the present application, the computing device provides cloud graphics corresponding to the recommended integration relationship of the cloud service architecture on the display interface, allowing users to quickly create a cloud service architecture based on the cloud graphics, thereby improving the design quality and design efficiency of the cloud service architecture.

[0050] In one possible implementation, when the score corresponding to the quality assessment result is less than or equal to a score threshold, the cloud service architecture is submitted for cloud service architecture review and cloud service architecture verification. Specifically, after the computing device passes the cloud service architecture quality assessment, the user can perform a cloud service architecture review on the cloud service architecture. This cloud service architecture review can be a manual review. After the manual review passes, the cloud service architecture can be further verified. After passing the verification, the cloud service architecture can be delivered.

[0051] In the embodiment of the present application, after the quality assessment result of the cloud service architecture is qualified, the computing device can perform cloud service architecture review and cloud service architecture verification on the cloud service architecture, thereby further improving the design quality of the cloud service architecture.

[0052] In a third aspect, embodiments of the present application provide a quality assessment device for a cloud service architecture, which is applied to a cloud service platform for managing a cloud service architecture, wherein the cloud service architecture includes at least two cloud services. The device includes an acquisition unit, a processing unit, and a display unit. The display unit is configured to display a cloud architecture editing interface, wherein the cloud architecture editing interface includes at least one element selection area, wherein the element selection area includes at least one cloud element, and wherein the cloud element corresponds to at least one cloud service. The acquisition unit is configured to acquire an element selection instruction from a user for a first cloud element, wherein the first cloud element corresponds to a first cloud service. The acquisition unit is further configured to acquire an element selection instruction from a user for a second cloud element, wherein the second cloud element corresponds to a second cloud service. The display unit is further configured to display a cloud architecture diagram, wherein the cloud architecture diagram represents the cloud service architecture, wherein the cloud architecture diagram includes a first cloud element and a second cloud element, wherein the first cloud service and the second cloud service in the cloud service architecture have an integrated relationship, wherein the integrated relationship is expressed by at least one of the following means: a connection between the first cloud element and the second cloud element in the cloud architecture diagram, or an inclusion relationship between the first cloud element and the second cloud element in the cloud architecture diagram. The processing unit is configured to evaluate the integration relationship between the first cloud service and the second cloud service based on at least one of the following information: the types of the first cloud service and the second cloud service, the communication method between the first cloud service and the second cloud service, and the communication content between the first cloud service and the second cloud service, wherein the communication content between the first cloud service and the second cloud service includes at least one of the following: the data content of the communication between the first cloud service and the second cloud service and the data format of the communication between the first cloud service and the second cloud service, and the communication method between the first cloud service and the second cloud service includes at least one of the following: the communication protocol between the first cloud service and the second cloud service and the communication path between the first cloud service and the second cloud service. The display unit is further configured to display the evaluation result of the integration relationship between the first cloud service and the second cloud service to a user.

[0053] In one possible implementation, the processing unit is further configured to provide a dependency evaluation result between the first cloud service and the third cloud service based on the dependency information. The dependency information includes at least one of the following: a strong dependency and a recommended dependency. A strong dependency means that at least one of the first and third cloud services exists as a bundled dependency with another cloud service. A recommended dependency means that at least one of the first and third cloud services is recommended to coexist with the other cloud service. The display unit is further configured to display the dependency evaluation result between the first and third cloud services to a user. The dependency evaluation result includes at least one of the following: a lack of at least one cloud service and a recommendation to add at least one cloud service.

[0054] In one possible implementation, the processing unit is also used to parse the cloud service architecture to obtain the integration relationship of the cloud services included in the cloud service architecture; based on the integration relationship of the cloud services, integration relationship retrieval is performed in the integration relationship knowledge graph to determine the associated integration relationship, and the associated integration relationship is used to determine the evaluation result of the integration relationship of the cloud service. The integration relationship knowledge graph is used to store the integration relationship between different cloud services.

[0055] In one possible implementation, the processing unit is also used to construct an integrated relationship knowledge graph based on the integrated relationship data. The integrated relationship knowledge graph includes nodes and edges. The nodes are used to represent cloud services, and the edges are used to represent the integration relationship between cloud services. The cloud service integrated relationship data includes historical integrated relationship data of different cloud services.

[0056] In a possible implementation, the integration relationship evaluation result includes one or more of the following: unknown integration relationship, prohibited integration relationship, not recommended integration relationship, optional integration relationship, and preferred integration relationship.

[0057] In a possible implementation, the display unit is further configured to display to the user the reasons why the integration relationship is prohibited or not recommended when the integration relationship evaluation result is that the integration relationship is prohibited or not recommended.

[0058] In a possible implementation, there is a mapping relationship between the integration relationship evaluation result and the integration relationship quality score, and the recommendation degree in the integration relationship evaluation result is associated with the integration relationship quality score.

[0059] In one possible implementation, the processing unit is further configured to provide a quality assessment call interface for performing integration relationship assessments across different cloud service architectures. The quality assessment call interface receives an integration relationship assessment request and sends an integration relationship assessment result corresponding to the integration relationship assessment request.

[0060] In one possible embodiment, the processing unit is further configured to modify the cloud service architecture when the integration relationship quality score corresponding to the integration relationship evaluation result is greater than a score threshold, and submit the cloud service architecture for cloud service architecture review and cloud service architecture verification when the integration relationship quality score corresponding to the integration relationship evaluation result is less than or equal to the score threshold.

[0061] In a possible implementation, the display unit is further configured to display a recommended integration relationship, where the recommended integration relationship includes at least two cloud services, and an evaluation result of the recommended integration relationship is better than an evaluation result of the integration relationship between the first cloud service and the second cloud service.

[0062] In one possible implementation, the display unit is also used to display a recommended integration relationship set, which includes a first recommended integration relationship and a second recommended integration relationship. In the recommended integration relationship set, the first recommended integration relationship is displayed better than the second recommended integration relationship, and the evaluation result of the first recommended integration relationship is better than the evaluation result of the second recommended integration relationship.

[0063] In a fourth aspect, an embodiment of the present application provides a computing device, comprising a processor coupled to a memory, the processor being used to store instructions. When the instructions are executed by the processor, the computing device executes the method described in the first aspect or any possible implementation of the first aspect.

[0064] In a fifth aspect, an embodiment of the present application provides a computing device cluster, which includes one or more computing devices, each of which includes a processor coupled to a memory, and the processor is used to store instructions. When the instructions are executed by the processor, the computing device cluster executes the method described in the first aspect or any possible implementation method of the first aspect.

[0065] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium having instructions stored thereon. When the instructions are executed, the computer executes the method described in the first aspect or any possible implementation method of the first aspect.

[0066] In a seventh aspect, an embodiment of the present application provides a computer program product, which includes instructions. When the instructions are executed, the computer implements the method described in the first aspect or any possible implementation method of the first aspect.

[0067] It can be understood that the beneficial effects that can be achieved by the quality assessment device, computing device, computing device cluster, computer-readable medium or computer program product of any of the cloud service architectures provided above can be referred to the beneficial effects in the corresponding method and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] FIG1 is a schematic diagram of the system architecture of a quantity evaluation system for a cloud service architecture provided in an embodiment of the present application;

[0069] FIG2 is a flow chart of a method for evaluating the quantity of a cloud service architecture provided in an embodiment of the present application;

[0070] FIG3a is a schematic diagram of a display interface of a cloud service architecture provided in an embodiment of the present application;

[0071] FIG3 b is a flow chart of another method for evaluating the quantity of a cloud service architecture provided in an embodiment of the present application;

[0072] FIG4a is a schematic diagram of a knowledge graph for creating an integrated relationship provided in an embodiment of the present application;

[0073] FIG4b is a data schematic diagram corresponding to a cloud service architecture provided in an embodiment of the present application;

[0074] FIG5 is a schematic diagram of a display interface of another cloud service architecture provided in an embodiment of the present application;

[0075] FIG6 a is a schematic diagram of a display interface of another cloud service architecture provided in an embodiment of the present application;

[0076] FIG6 b is a schematic diagram of a display interface of another cloud service architecture provided in an embodiment of the present application;

[0077] FIG7 is a schematic diagram of a quality assessment device for a cloud service architecture provided by an embodiment of the present application;

[0078] FIG8 is a schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0079] FIG9 is a schematic diagram of the structure of another computing device provided in an embodiment of the present application;

[0080] FIG10 is a schematic diagram of the structure of another computing device cluster provided in an embodiment of the present application. DETAILED DESCRIPTION

[0081] The embodiments of the present application provide a method and apparatus for evaluating the quality of a cloud service architecture, for improving the design quality of the cloud service architecture.

[0082] The terms "first," "second," "third," "fourth," and the like (if any) in the specification and claims of this application and in the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or sequential sequence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions, e.g., a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0083] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0084] First, some terms involved in the embodiments of the present application are introduced to facilitate those skilled in the art to understand the technical solutions.

[0085] Elastic Cloud Server (ECS) is an elastically scalable cloud server instance that allows users to quickly create, configure, and manage virtual servers according to their needs.

[0086] Bare metal server (BMS) refers to a physical server rental service on the cloud. Bare metal servers can provide users with physical servers that do not go through multiple layers of virtualization, and users can control the server hardware and operating system environment.

[0087] Elastic Volume Service (EVS) is a storage space that provides persistent block storage for computing services such as ECS and BMS. Users can format EVS, create file systems, and store data persistently.

[0088] Object Storage Service (OBS) is an object-based storage service that provides customers with massive, secure, highly reliable, and low-cost data storage capabilities. There are no capacity limitations when using OBS, and OBS offers a variety of storage types to meet the needs of customers in various business scenarios.

[0089] A virtual private cloud (VPC) is an isolated, private virtual network environment that users apply for on the cloud.

[0090] An Elastic IP (Elastic IP) is a public IP address that can be dynamically bound and unbound. It is used to provide reliable public network access to cloud resources such as cloud servers and load balancers.

[0091] Elastic Load Balance (ELB) automatically distributes access traffic to multiple cloud servers, expanding the application system's external service capabilities and reducing the load and complexity of cloud servers.

[0092] In order to make the technical solution of the present application clearer and easier to understand, the system architecture of the present application is introduced below with reference to the accompanying drawings.

[0093] Please refer to Figure 1, which is a schematic diagram of the system architecture of a cloud service architecture quality assessment system provided in an embodiment of the present application. In the example shown in Figure 1, the cloud service architecture quality assessment system 10 includes an integrated relationship knowledge graph maintenance subsystem 101, a cloud service architecture design subsystem 102, a cloud service architecture assessment subsystem 103, and a cloud service architecture verification subsystem 104. The specific functions of each subsystem of the cloud service architecture quality assessment system 10 are described below.

[0094] The integration relationship knowledge graph maintenance subsystem 101 is used to generate a knowledge graph of cloud service integration relationships. This knowledge graph describes the optional integration relationships between cloud services, as well as the priority and integration type of the integration relationships. The integration relationship knowledge graph maintenance subsystem 101 includes an integration relationship maintenance module 1011 and a knowledge graph construction module 1012.

[0095] Among them, the integration relationship maintenance module 1011 is used to define the integration rules between different cloud services based on the historical integration relationships between cloud services and the experience of integration architects, and enter point data and edge data in the integration relationship knowledge graph maintenance subsystem 101 according to the defined integration rules. Point data refers to cloud services, and edge data refers to the integration relationships between cloud services and the integration relationship priorities.

[0096] The knowledge graph construction module 1012 is used to standardize the point data and edge data entered by the integration relationship maintenance module 1011. The knowledge graph construction module 1012 saves the cloud services and the integration relationships and integration priorities between cloud services to the graph system, thereby obtaining a knowledge graph of cloud service integration relationships. The knowledge graph of cloud service integration relationships serves as a reference standard for the cloud service architecture evaluation subsystem 103 to perform cloud service architecture quality evaluation.

[0097] The cloud service architecture design subsystem 102 is used to design the cloud service architecture. The cloud service architecture design subsystem 102 provides an architecture editing interface for cloud service architecture design. Users can use the architecture editing interface to design the cloud service architecture and create a design diagram of the cloud service architecture.

[0098] The cloud service architecture design subsystem 102 includes a requirements analysis module 1021, a cloud service preparation module 1022, and a cloud service architecture design module 1023. The requirements analysis module 1021 is used to analyze the business scenarios and design requirements for the cloud service architecture design. The cloud service preparation module 1022 is used to collect relevant cloud services that constitute the cloud service architecture based on the design requirements and provide information on the relevant cloud services. The cloud service architecture design module 1023 is used to design and generate the cloud service architecture for the cloud service. The cloud service architecture design module 1023 is also used to call the quality assessment interface provided by the cloud service architecture assessment subsystem 103 during the cloud service architecture design process to generate real-time quality assessment results for the cloud service architecture.

[0099] The cloud service architecture assessment subsystem 103 is used to perform a quality assessment on the cloud service architecture of the cloud service based on the knowledge graph. The knowledge graph is the integrated relationship knowledge graph generated by the integrated relationship knowledge graph maintenance subsystem 101, and the cloud service architecture of the cloud service is the cloud service architecture designed by the cloud service architecture design subsystem 102. The cloud service architecture assessment subsystem 103 provides a quality assessment interface for the cloud service architecture. The cloud service architecture design module 1023 can call this quality assessment interface to generate a quality assessment result for the cloud service architecture.

[0100] It is understandable that the cloud service architecture evaluation subsystem 103 can perform quality evaluation on the cloud service architecture that is being designed by the cloud service architecture design subsystem 102, or it can perform quality evaluation on the cloud service architecture that has been designed by the cloud service architecture design subsystem 102, without any specific limitation.

[0101] The cloud service architecture assessment subsystem 103 includes a parsing module 1031, a quality assessment module 1032, and a result presentation module 1033. The parsing module 1031 is used to parse the cloud service architecture being designed or completed, obtaining the cloud services included in the cloud service architecture and the integration relationships between cloud services. The quality assessment module 1032 is used to compare the parsed integration relationships with the integration rules maintained in the knowledge graph and generate quality assessment results for each integration relationship based on preset assessment rules. The result presentation module 1033 is used to present the quality assessment results of the cloud service architecture on a display interface.

[0102] The cloud service architecture verification subsystem 104 is responsible for final verification and testing of the cloud service architecture. Specifically, the cloud service architecture verification subsystem 104 creates the corresponding cloud service architecture on the cloud service platform according to the designed cloud service architecture diagram and its configuration list, completing the actual deployment of the cloud service architecture. Based on the actual scenarios of the cloud service architecture, the cloud service architecture verification subsystem 104 designs various test cases, such as functional testing, performance testing, reliability testing, and security testing. The cloud service architecture is tested based on these test cases and, upon passing the tests, the cloud service architecture is delivered.

[0103] The cloud service architecture verification subsystem 104 includes a deployment and verification module 1041 and a delivery module 1042. The deployment and verification module 1041 is used to actually deploy the cloud service architecture based on the designed cloud service architecture and test the cloud service architecture according to test cases. The delivery module 1042 is used to deliver the tested cloud service architecture.

[0104] It should be noted that each subsystem in the quality assessment system 10 of the cloud service architecture can be implemented by software or hardware, without specific limitation.

[0105] When the quality assessment system 10 for a cloud service architecture is implemented via software, it can be an application running on a computing device, with each subsystem running as an application on the computing device and provided to a browser or third-party application through an interface. The computing device can be, for example, a server on a public or private cloud. When the quality assessment system 10 for a cloud service architecture is implemented via hardware, each subsystem in the quality assessment system 10 can be a computing device or processing circuit, etc.

[0106] Based on the quality assessment system 10 of the cloud service architecture shown in Figure 1, the present application further provides a quality assessment method for the cloud service architecture. The quality assessment method for the cloud service architecture provided by the present application is described below in conjunction with an embodiment.

[0107] Please refer to Figure 2, which is a flow chart of a quality assessment method for a cloud service architecture provided by an embodiment of the present application. In the example shown in Figure 2, the method includes the following steps:

[0108] 201. Display the cloud service architecture through the cloud architecture editing interface, where the cloud service architecture includes a first cloud graphic element corresponding to the first cloud service and a second cloud graphic element corresponding to the second cloud service.

[0109] The cloud service architecture quality assessment system 10 first obtains a cloud service architecture, which is the cloud service architecture created by the user device in the cloud architecture editing interface. Specifically, the user device performs cloud service architecture design based on the cloud service architecture design subsystem 102, including design requirements analysis, cloud service selection, and cloud service architecture creation. For example, during the cloud service architecture design process, the user device can select different cloud services provided by the cloud service platform in the cloud architecture editing interface to create and configure the cloud service architecture for the cloud service.

[0110] The quality assessment system 10 of the cloud service architecture provides a cloud architecture editing interface, which includes at least one graphic element selection area. The graphic element selection area includes at least one cloud graphic element. The quality assessment system 10 of the cloud service architecture corresponds to at least one cloud service in at least one cloud graphic element.

[0111] The user can edit the first cloud primitive and the second cloud primitive in the cloud architecture editing interface. The cloud service architecture quality assessment system 10 obtains the user's primitive selection instruction for the first cloud primitive, where the first cloud primitive corresponds to the first cloud service. The user's primitive selection instruction for the second cloud primitive is obtained, where the second cloud primitive corresponds to the second cloud service. The cloud service architecture quality assessment system 10 displays a cloud architecture diagram in the cloud architecture editing interface. The cloud architecture diagram represents the cloud service architecture. The first cloud service and the second cloud service in the cloud service architecture have an integration relationship. The integration relationship is expressed in at least one of the following ways: a connection between the first cloud primitive and the second cloud primitive in the cloud architecture diagram, or an inclusion relationship between the first cloud primitive and the second cloud primitive in the cloud architecture diagram.

[0112] Please refer to Figure 3a, which is a schematic diagram of a cloud architecture editing interface provided in an embodiment of the present application. In the example shown in Figure 3a, the left side is an element selection area, and the right side is a custom canvas. The element selection area includes cloud elements that can be selected for cloud architecture design. The custom canvas is the editing area for cloud architecture design, and the user can display the selected cloud elements on the custom canvas.

[0113] In the embodiment of the present application, a cloud primitive refers to a graphic identifier of the smallest unit, also called a primitive. For example, in the management of a cloud service resource, two or more cloud services can be integrated together to form a server cluster; each cloud primitive can identify the type, basic specifications and other information of a cloud service. In one possible implementation, a cloud primitive can also represent a collection of more than two cloud services. The number and type of specific cloud services represented by the cloud primitive are not limited here. In the embodiment of the present application, a cloud primitive can be an element of relatively fixed size, or a table, wireframe or connection element, which is not limited in the present application.

[0114] Please refer to Figure 3b, which is a flow chart of a quality assessment method for a cloud service architecture provided by an embodiment of the present application. In the example shown in Figure 3b, from step a to step b, the user device designs the cloud service architecture of the cloud service based on the cloud service architecture design subsystem 102, and the user device inputs the business scenario and design requirements into the cloud service architecture design subsystem 102, and creates the cloud service architecture based on the design requirements to obtain the cloud service architecture of the cloud service. For example, the user device creates a virtual private cloud VPC on the display interface of the cloud service platform, and creates an elastic cloud server ECS, an object storage service OBS, and a cloud hard disk EVS in the virtual private cloud VPC. At the same time, the user device establishes a strong dependency relationship between the virtual private cloud VPC and the elastic cloud server ECS on the display interface of the cloud service platform.

[0115] The cloud services in the embodiments of the present application include various types of cloud services, such as computing cloud services, container cloud services, storage cloud services, and network cloud services. Among them, computing cloud services include Elastic Cloud Servers (ECS), Bare Metal Servers (BMS), and Image Services (IMS), container cloud services include Cloud Container Engines (CCE) and Container Image Services (SWR), storage cloud services include EVS, Elastic File Services (SFS), and Object Storage Services (OBS), and network cloud services include Virtual Private Clouds (VPC), Elastic Internet Protocol (EIP), Elastic Load Balancing (ELB), and Network Address Translation (NAT).

[0116] In the embodiment of the present application, after the user device designs the cloud service architecture of the cloud service based on the cloud service architecture design subsystem 102, it calls the cloud service architecture evaluation subsystem 103 to perform a quality evaluation on the cloud service architecture. At this time, the cloud service architecture evaluation subsystem 103 obtains the cloud service architecture. Before the cloud service architecture evaluation subsystem 103 performs the quality evaluation on the cloud service architecture, it first needs to build an integrated relationship knowledge graph, which is described below:

[0117] In one possible implementation, the cloud service architecture assessment subsystem 103 constructs an integrated relationship knowledge graph based on the integrated relationship data. The integrated relationship knowledge graph includes nodes and edges. Nodes represent cloud services, and edges represent integrated relationships between cloud services. The cloud service integrated relationship data includes historical data on cloud service integrated relationships. The following describes in detail the process by which the cloud service architecture assessment subsystem 103 constructs the integrated relationship knowledge graph based on the integrated relationship data:

[0118] First, the cloud service architecture assessment subsystem 103 needs to define the types of cloud service integration relationships and maintain integration relationship data between cloud services based on the defined integration relationship types and historical data of cloud service integration relationships. The types of cloud service integration relationships are described in detail below.

[0119] Please refer to Table 1, which is a schematic table of integration relationship type definitions provided in an embodiment of the present application. As can be seen from the example shown in Table 1, cloud service integration relationship types include main types and subtypes. The main types include network protocol integration, data storage integration, middleware integration, dependency integration, and other integration. Each main integration type also includes subtypes. For example, the subtypes of the data storage integration type include object storage integration, file storage integration, and block storage integration.

[0120] Table 1

[0121] Next, the cloud service architecture assessment subsystem 103 maintains the integration relationships between cloud services based on the defined integration relationship types and generates a knowledge graph of the integration relationships. The integration relationship knowledge graph includes nodes and edges, where nodes represent cloud services and edges represent integration relationships between cloud services. The following describes the nodes and edges in the integration relationship knowledge graph:

[0122] In one possible implementation, the nodes in the integrated relational knowledge graph include node identifiers and node labels, wherein the node identifiers are used to identify cloud services, and the node labels are used to describe various features of the cloud services, such as name and type.

[0123] See Table 2 for a schematic diagram of node identifiers and node labels provided in an embodiment of the present application. In the example shown in Table 2, the node identifier includes the abbreviation of the cloud service name, and the node label includes the name and type. For example, the node identifier of an Elastic Cloud Server is ECS, the name is Elastic Cloud Server, and the type is a Compute Node.

[0124] Table 2

[0125] In one possible implementation, the edges in the integration relationship knowledge graph include edge labels and two node identifiers corresponding to the edges, wherein the node identifiers are used to identify cloud services, and the edge labels are used to describe various features between cloud services, such as integration type, integration type description, and integration priority.

[0126] Please refer to Table 3, which is a schematic table of node identifiers and edge labels provided in an embodiment of the present application. In the example shown in Table 3, node identifier 1 and node identifier 2 are respectively cloud services connected by edges in the integration relationship knowledge graph, and the edge labels include integration type, integration type description, and integration relationship priority. For example, the integration type between the Elastic Cloud Server ECS and the Cloud Hard Drive EVS is block storage, the integration type description is that the Elastic Cloud Server ECS can be mounted on the Cloud Hard Drive EVS, and the integration priority is 4.

[0127] Table 3

[0128] Please refer to Table 4, which is a schematic table of integration relationship priorities provided in an embodiment of the present application. In the example shown in Table 4, the priorities of the integration relationships between cloud services include five priorities, namely levels 1 to 4 and the max level, where level 1 indicates that the integration relationship is prohibited, level 2 indicates that the integration relationship is not recommended, level 3 indicates that the integration relationship is optional, level 4 indicates that the integration relationship is preferred, and the max level indicates that the integration relationship is required.

[0129] Table 4

[0130] Please refer to Figure 4a, which is a schematic diagram of generating an integration relationship knowledge graph provided in an embodiment of the present application. In step a of the example shown in Figure 4a, the integration relationship knowledge graph maintenance subsystem 101 first defines the type of cloud service integration relationship and enters the integration relationship between cloud services based on the historical data of cloud service integration.

[0131] In the example steps b to c shown in FIG4a , after the integration relationship between cloud services is entered by the integration relationship knowledge graph maintenance subsystem 101 , the entered integration relationship between cloud services is standardized based on the structure of the knowledge graph to generate a knowledge graph of the integration relationship between cloud services.

[0132] Specifically, the integrated relationship knowledge graph maintenance subsystem 101 maintains nodes and edges in the knowledge graph based on the integrated relationship between cloud services, thereby obtaining a knowledge graph of the integrated relationship. The integrated relationship knowledge graph maintenance subsystem 101 creates nodes of the knowledge graph based on the cloud services and edges of the knowledge graph based on the integrated relationship between cloud services. A node includes a node identifier and a node label, and an edge includes both end node identifiers and an edge label. The integrated relationship knowledge graph maintenance subsystem 101 then saves the integrated relationship knowledge graph.

[0133] 202. Perform an integration relationship evaluation on the cloud service architecture based on the integration relationship information, where the integration relationship information includes: the first cloud service and the type, communication method, and communication content of the first cloud service.

[0134] In the process of evaluating the integration relationship of the cloud service architecture based on the integration relationship information, the quality assessment system 10 of the cloud service architecture evaluates the integration relationship of the first cloud service and the second cloud service according to at least one of the following integration relationship information: the types of the first cloud service and the second cloud service, the communication methods of the first cloud service and the second cloud service, and the communication content of the first cloud service and the second cloud service. The communication content of the first cloud service and the second cloud service includes at least one of the following: the data content of the communication between the first cloud service and the second cloud service, and the data format of the communication between the first cloud service and the second cloud service. The communication method of the first cloud service and the second cloud service includes at least one of the following: the communication protocol of the first cloud service and the second cloud service, and the communication path of the first cloud service and the second cloud service.

[0135] Here, "category" refers to the type of cloud service, and "communication method" and "communication content" refer to characteristics related to cloud services and cloud service integration relationships. "Communication content" includes the communication data content and format, and is used to indicate the node label of the cloud service. "Communication method" includes the communication protocol and communication path, and is used to indicate the integration type of the cloud service integration relationship. Communication protocols include the network protocol integration listed in Table 1, and communication paths include the middleware integration listed in Table 1. It should be noted that this integration relationship information can also be referred to as information in the integration relationship knowledge graph, and the integration relationship indication graph is used to store this integration relationship information.

[0136] During the cloud service architecture design process, the cloud service architecture design subsystem 102 can call the cloud service architecture assessment subsystem 103 to perform a quality assessment on the cloud service architecture. Specifically, the cloud service architecture assessment subsystem 103 performs a quality assessment on the cloud service architecture based on an integration relationship knowledge graph, generating a quality assessment result. The integration relationship knowledge graph is used to indicate the integration rules between different cloud services. The integration rules include one or more of the following: integration relationship type and integration priority.

[0137] In one possible implementation, during the quality assessment of the cloud service architecture, the cloud service architecture assessment subsystem 103 parses the cloud service architecture's integration relationships to obtain the integration relationships between cloud services in the cloud service architecture. Based on the integration relationships of the cloud services, the subsystem searches the integration relationship knowledge graph to determine associated integration relationships in the integration relationship knowledge graph. The associated integration relationships are used to assess the design quality of the cloud service integration relationships in the cloud service architecture. The cloud service architecture assessment subsystem 103 generates a quality assessment result based on the associated integration relationships and the cloud service integration relationships.

[0138] Specifically, in the process of the cloud service architecture evaluation subsystem 103 generating a quality evaluation result based on the associated integration relationship and the integration relationship of the cloud service, the cloud service architecture evaluation subsystem 103 searches and compares the associated integration relationship based on the integration relationship of the cloud service. After retrieving an associated integration relationship whose similarity with the integration relationship is less than a threshold, the cloud service architecture evaluation subsystem 103 further determines the integration relationship priority corresponding to the associated integration relationship. The cloud service architecture evaluation subsystem 103 determines the integration relationship quality evaluation result of the cloud service based on the integration relationship priority.

[0139] It can be understood that the cloud service architecture includes one or more integrated relationships of cloud services, and the cloud service architecture evaluation subsystem 103 can generate a quality evaluation result based on each integration relationship. The cloud service architecture evaluation subsystem 103 can also generate an overall quality evaluation result of the cloud service architecture based on the quality evaluation result of each integration relationship in the cloud service architecture.

[0140] In one possible implementation, the quality assessment result includes one or more of the following: unknown integration relationship, prohibited integration relationship, not recommended integration relationship, optional integration relationship, preferred integration relationship, and required integration relationship. An unknown integration relationship means that the integration relationship is not found in the knowledge graph.

[0141] In one possible implementation, when the integration relationship evaluation result indicates that the integration relationship is prohibited or not recommended, the computing device displays the reason for prohibiting or not recommending the integration relationship to the user. Specifically, the computing device may display an evaluation result description corresponding to the integration relationship evaluation result, while displaying the integration relationship evaluation result. The evaluation result description may explain the evaluation basis for the integration relationship evaluation result. The computing device may also display modification suggestions corresponding to the prohibition or not recommending the integration relationship to the user.

[0142] It is understandable that the quality assessment result of each integration relationship in the cloud service architecture will correspond to a quality score, and the cloud service architecture assessment subsystem 103 can calculate the total quality score of the cloud service architecture based on the integration relationships included in the cloud service architecture.

[0143] Please refer to Table 5, which shows the correspondence between a quality assessment result and a quality score provided in an embodiment of the present application. From the example shown in Table 5, it can be seen that the higher the cloud service architecture score, the lower the quality of the cloud service architecture. For example, the quality score corresponding to unknown integration relationship and prohibited integration relationship is 10 points, the quality score corresponding to not recommended integration relationship is 3 points, the quality score corresponding to optional integration relationship is 0.1 points, and the quality scores corresponding to preferred integration relationship and required integration relationship are both 0 points.

[0144] Table 5

[0145] Continuing with FIG3b , in the example steps c through h shown in FIG3b , during the cloud service architecture design process, the user device can invoke a quality assessment interface provided by cloud service architecture assessment subsystem 103 to perform a quality assessment on the currently designed cloud service architecture. Cloud service architecture assessment subsystem 103 analyzes the cloud service architecture and obtains the integration relationships between cloud services within the cloud service architecture.

[0146] In the example shown in Figure 3b, after the cloud service architecture evaluation subsystem 103 parses the integration relationship between cloud services in the cloud service architecture, it can call the integration relationship knowledge graph stored in the integration relationship knowledge graph maintenance subsystem 101, and search for associated integration relationships related to the cloud service architecture in the knowledge graph, and compare them. According to the integration relationship type and integration relationship priority corresponding to the associated integration relationship, the integration relationship quality evaluation result of the cloud service in the cloud service architecture is determined, and the quality evaluation result is returned to the user device.

[0147] In one possible implementation, the cloud service architecture diagram designed on the display interface of the user device in the embodiment of the present application can be stored as standard structured data. In this way, the cloud service architecture evaluation subsystem 103 can parse the structured data corresponding to the cloud service architecture during the process of parsing the cloud service architecture, thereby obtaining all the integration relationships in the cloud service architecture.

[0148] Please refer to Figure 4b, which is a schematic diagram of a cloud service architecture and structured data provided in an embodiment of the present application. In the example shown in Figure 4b, Figure (a) shows a user designing a cloud service architecture on a display interface, wherein the cloud service architecture includes an integrated relationship between an elastic cloud server and a cloud database, and Figure (b) shows the structured data corresponding to the cloud service architecture.

[0149] In the structured data in Figure (b), the type field "standard.Link" indicates the integration relationship between the elastic cloud server and the cloud database. When parsing the cloud service architecture, the cloud service architecture assessment subsystem 103 reads the element with the type field "standard.Link" to obtain the integration relationship in the cloud service architecture.

[0150] 203. Present the integration relationship evaluation results of cloud service architecture.

[0151] After the cloud service architecture evaluation subsystem 103 generates the integration relationship evaluation results of the cloud service architecture, the integration relationship evaluation results can be displayed on the display interface of the cloud service platform. The integration relationship evaluation results are also called quality evaluation results. The quality evaluation results are used to indicate the quality scores of one or more integration relationships in the cloud service architecture.

[0152] In one possible implementation, cloud service architecture assessment subsystem 103 may display a quality assessment call interface on a display interface. This quality assessment call interface is used to provide real-time quality assessment results of integration relationships within the cloud service architecture during the cloud service architecture design process. During the cloud service architecture design process, cloud service architecture design subsystem 102 may call cloud service architecture assessment subsystem 103 in real time to perform a quality assessment on the cloud service architecture being designed and generate quality assessment results.

[0153] Please refer to Figure 5, which is a schematic diagram of a cloud service architecture design provided by an embodiment of the present application. In the example shown in Figure 5, while the user is designing the cloud service architecture, he can call the cloud service architecture evaluation subsystem 103 in real time to generate a cloud service architecture quality evaluation result. For example, the user creates a virtual private cloud VPC, and further creates an elastic cloud server ECS, a cloud hard disk EVS, and an object storage service OBS in the virtual private cloud. At the same time, the virtual private cloud and the elastic cloud server in the cloud service architecture are set to a strong dependency relationship, the elastic cloud server and the cloud hard disk are set to a strong dependency relationship, and the elastic cloud server and the object storage service are set to an object storage integration relationship.

[0154] In the example shown in Figure 5, the user can call the quality assessment interface of the architecture assessment subsystem 103 to perform a quality assessment on the designed cloud service architecture and generate a quality assessment result corresponding to the cloud service architecture. The architecture assessment subsystem 103 can generate a total quality score for the cloud service architecture and a quality score for each integration relationship in the cloud service architecture. For example, the total quality score of the cloud service architecture shown in Figure 5 is 13.1 points, among which the integration relationship between the virtual private cloud VPC and the elastic cloud server ECS is a preferred integration relationship with a quality score of 0.1 points, the integration relationship between the elastic cloud server ECS and the cloud hard disk EVS is a non-recommended integration relationship with a quality score of 3 points, and the integration relationship between the elastic cloud server ECS and the object storage service OBS is a prohibited integration relationship with a quality score of 10 points.

[0155] In the example shown in FIG5 , the architecture assessment subsystem 103 can annotate the integration relationships displayed on the interface with the quality assessment results of the cloud service architecture. For example, the architecture assessment subsystem 103 can annotate the current integration relationship between the virtual private cloud and the elastic cloud server as the preferred integration relationship, the integration relationship between the elastic cloud server and the cloud hard disk as the not-recommended integration relationship, and the integration relationship between the elastic cloud server and the object storage service as the prohibited integration relationship on the interface displaying the cloud service architecture design.

[0156] In one possible implementation, the architecture assessment subsystem 103 can provide recommended integration relationships for the cloud service architecture on a display interface based on a quality assessment interface. The recommended integration relationships are determined based on an integration relationship knowledge graph. Furthermore, the architecture assessment subsystem 103 can also recommend cloud primitives associated with the integration relationships on a display interface based on a quality assessment call interface.

[0157] It can be understood that the architecture evaluation subsystem 103 can provide recommended integration relationships for the integration relationships in the already designed cloud service architecture. The recommended integration relationships are modification suggestions for the already designed integration relationships. The architecture evaluation subsystem 103 can also provide recommended integration relationships for the cloud service architecture being designed. The recommended integration relationships can guide the design of the cloud service architecture.

[0158] For example, in one possible implementation, a computing device provides a dependency evaluation result between a first cloud service and a third cloud service based on dependency information. The third cloud service may be a cloud service that a user wants to design or recommend. The dependency information includes at least one of the following: a strong dependency and a recommended dependency. A strong dependency means that the first cloud service and at least one of the first cloud services exist as a bundled copy of another cloud service. A recommended dependency means that at least one of the first cloud service and the second cloud service is recommended to coexist with the other cloud service. The computing device displays the dependency evaluation result between the first cloud service and the third cloud service to the user. The dependency evaluation result includes at least one of the following: the lack of at least one cloud service and a recommendation to add at least one cloud service. For example, if a user only selects a cloud element corresponding to the first cloud service in the cloud architecture editing interface and does not select a cloud element corresponding to the third cloud service, the computing device may provide a dependency evaluation result for the cloud architecture, which is "the first cloud service of the cloud architecture lacks the third cloud service."

[0159] That is, the dependency relationship evaluation result can indicate the modification suggestion of the integration relationship. The above dependency relationship information can also be called information in the integration relationship knowledge graph, and the integration relationship indication graph is used to store the above dependency relationship information.

[0160] In one possible implementation, the computing device displays a recommended integration relationship, the recommended integration relationship includes at least two cloud services, and an evaluation result of the recommended integration relationship is better than an evaluation result of the integration relationship of the first cloud service and the second cloud service.

[0161] For example, a user designs a cloud architecture that includes a first cloud service and a second cloud service in the cloud architecture editing interface. The computing device displays recommended integration relationships of other cloud services based on the cloud architecture. The evaluation result of the recommended integration relationship in the cloud architecture is better than the evaluation result of the integration relationship of the first cloud service and the second cloud service. Therefore, the user can select the recommended integration relationship to replace the integration relationship of the first cloud service and the second cloud service.

[0162] In one possible implementation, a computing device displays a recommended integration relationship set, which includes a first recommended integration relationship and a second recommended integration relationship. In the recommended integration relationship set, the first recommended integration relationship is displayed better than the second recommended integration relationship, and the evaluation result of the first recommended integration relationship is better than the evaluation result of the second recommended integration relationship, that is, the recommended integration relationships in the recommended integration relationship set can be displayed in order of recommendation procedures.

[0163] For example, a user designs a cloud architecture that includes a first cloud service and a second cloud service in the cloud architecture editing interface. The computing device displays a recommended integration relationship set based on the cloud architecture. The recommended integration relationship set includes multiple recommended integration relationships. The multiple recommended integration relationships will be sorted and displayed according to the evaluation results of the integration relationships. The recommended integration relationships with high recommendation degrees in the evaluation results will be displayed first.

[0164] Please refer to Figure 6a, which is a schematic diagram of a display interface providing recommended integration relationships according to an embodiment of the present application. In the example shown in Figure 6a, after designing a cloud service architecture, the user calls the cloud service architecture assessment subsystem 103 to perform a quality assessment of the cloud service architecture. The cloud service architecture assessment subsystem 103 provides recommended integration relationships for the integration relationships in the cloud service architecture.

[0165] For example, in the example shown in Figure 6a, the user-designed cloud service architecture includes an elastic process cloud server and a cloud database. The integration relationship between the cloud server and the cloud database is set to object storage. The cloud service architecture assessment subsystem 103 evaluates the quality of this integration relationship and determines that the integration relationship is not recommended. The cloud service architecture assessment subsystem 103 also provides multiple recommended integration relationships for this integration relationship, ranked by recommendation level. The recommended integration relationships include TCP / UDP integration, application integration, and HTTP / HTTPS integration.

[0166] Please refer to Figure 6b, which is a schematic diagram of another display interface providing recommended integration relationships according to an embodiment of the present application. In the example shown in Figure 6b, during the process of designing a cloud service architecture, the user calls the cloud service architecture evaluation subsystem 103 to provide recommended integration relationships. The user can further design the cloud service architecture based on the recommended integration relationships provided by the cloud service architecture evaluation subsystem 103.

[0167] For example, in the example shown in Figure 6b, when the user is designing the cloud service architecture in the display interface, after the user creates an elastic cloud server, the cloud service architecture evaluation subsystem 103 can be called to provide recommended integration relationships. The cloud service architecture evaluation subsystem 103 provides all cloud elements that may have integration relationships with the elastic cloud server, such as elastic cloud server ECS and elastic load balancing ELB service, etc. The user can select the corresponding cloud element from them to proceed to the next step of creation.

[0168] In one possible implementation, when the score corresponding to the quality assessment result is less than or equal to the score threshold, the cloud service architecture is submitted for cloud service architecture review and cloud service architecture verification. Specifically, after the cloud service architecture assessment subsystem 103 passes the quality assessment of the cloud service architecture, the user can perform a cloud service architecture review on the cloud service architecture. This cloud service architecture review is a manual review. After the manual review passes, the cloud service architecture can be further verified. After passing the verification, the cloud service architecture can be delivered.

[0169] It can be seen from the above embodiments that the computing device in the embodiments of the present application can perform quality assessment on the cloud service architecture designed by the user based on the integrated relational knowledge graph, and display the quality assessment results of the cloud service architecture through a display interface, thereby improving the design quality and design efficiency of the cloud service architecture.

[0170] Based on the above method embodiment, the embodiment of the present application also provides a quality assessment device for a cloud service architecture. The quality assessment device for a cloud service architecture provided by the embodiment of the present application is described in detail below.

[0171] Please refer to Figure 7, which is a schematic diagram of the structure of a quality assessment device for a cloud service architecture provided in an embodiment of the present application. In the example shown in Figure 7, the quality assessment device 700 for a cloud service architecture is used to implement the various steps performed by the computing device in the above embodiments. The quality assessment device 700 for a cloud service architecture includes an acquisition unit 701, a processing unit 702, and a display unit 703.

[0172] Among them, the display unit 703 is used to display the cloud architecture editing interface, the cloud architecture editing interface includes at least one element selection area, the element selection area includes at least one cloud element, and the cloud element corresponds to at least one cloud service. The acquisition unit 701 is used to obtain the user's element selection instruction for the first cloud element, and the first cloud element corresponds to the first cloud service. The acquisition unit 701 is also used to obtain the user's element selection instruction for the second cloud element, and the second cloud element corresponds to the second cloud service. The display unit 703 is also used to display the cloud architecture diagram, which represents the cloud service architecture. The cloud architecture diagram includes the first cloud element and the second cloud element. The first cloud service and the second cloud service in the cloud service architecture have an integration relationship, and the integration relationship is expressed by at least one of the following methods: the connection between the first cloud element and the second cloud element in the cloud architecture diagram, and the inclusion relationship between the first cloud element and the second cloud element in the cloud architecture diagram. The processing unit 702 is configured to evaluate the integration relationship between the first cloud service and the second cloud service based on at least one of the following information: the types of the first cloud service and the second cloud service, the communication method between the first cloud service and the second cloud service, and the communication content between the first cloud service and the second cloud service, where the communication content between the first cloud service and the second cloud service includes at least one of the following: the data content of the communication between the first cloud service and the second cloud service and the data format of the communication between the first cloud service and the second cloud service. The communication method between the first cloud service and the second cloud service includes at least one of the following: the communication protocol between the first cloud service and the second cloud service and the communication path between the first cloud service and the second cloud service. The display unit 703 is further configured to display the evaluation result of the integration relationship between the first cloud service and the second cloud service to a user.

[0173] In one possible implementation, the processing unit 702 is further configured to provide a dependency evaluation result between the first cloud service and the third cloud service based on the dependency information. The dependency information includes at least one of the following: a strong dependency and a recommended dependency. A strong dependency means that at least one of the first cloud service and the third cloud service exists as a bundled copy of another cloud service. A recommended dependency means that at least one of the first cloud service and the third cloud service is recommended to coexist with the other cloud service. The display unit 703 is further configured to display the dependency evaluation result between the first cloud service and the third cloud service to the user. The dependency evaluation result includes at least one of the following: a lack of at least one cloud service and a recommendation to add at least one cloud service.

[0174] In one possible implementation, the processing unit 702 is also used to parse the cloud service architecture to obtain the integration relationship of the cloud services included in the cloud service architecture; based on the integration relationship of the cloud services, an integration relationship search is performed in the integration relationship knowledge graph to determine the associated integration relationship, and the associated integration relationship is used to determine the evaluation result of the integration relationship of the cloud service. The integration relationship knowledge graph is used to store the integration relationship between different cloud services.

[0175] In one possible implementation, the processing unit 702 is further used to construct an integrated relationship knowledge graph based on the integrated relationship data. The integrated relationship knowledge graph includes nodes and edges. The nodes are used to represent cloud services, and the edges are used to represent the integration relationships between cloud services. The cloud service integrated relationship data includes historical integrated relationship data of different cloud services.

[0176] In a possible implementation, the integration relationship evaluation result includes one or more of the following: unknown integration relationship, prohibited integration relationship, not recommended integration relationship, optional integration relationship, and preferred integration relationship.

[0177] In a possible implementation, the display unit 703 is further configured to display the reasons why the integration relationship is prohibited or not recommended to the user when the integration relationship evaluation result is that the integration relationship is prohibited or not recommended.

[0178] In a possible implementation, there is a mapping relationship between the integration relationship evaluation result and the integration relationship quality score, and the recommendation degree in the integration relationship evaluation result is associated with the integration relationship quality score.

[0179] In one possible implementation, processing unit 702 is further configured to provide a quality assessment call interface for performing integration relationship assessments across different cloud service architectures. The quality assessment call interface receives an integration relationship assessment request and sends an integration relationship assessment result corresponding to the integration relationship assessment request.

[0180] In one possible embodiment, the processing unit 702 is further configured to modify the cloud service architecture when the integration relationship quality score corresponding to the integration relationship evaluation result is greater than a score threshold, and submit the cloud service architecture for cloud service architecture review and cloud service architecture verification when the integration relationship quality score corresponding to the integration relationship evaluation result is less than or equal to the score threshold.

[0181] In a possible implementation, the display unit 703 is further configured to display a recommended integration relationship, where the recommended integration relationship includes at least two cloud services, and an evaluation result of the recommended integration relationship is better than an evaluation result of the integration relationship between the first cloud service and the second cloud service.

[0182] In one possible implementation, the display unit 703 is also used to display a recommended integration relationship set, which includes a first recommended integration relationship and a second recommended integration relationship. In the recommended integration relationship set, the first recommended integration relationship is displayed better than the second recommended integration relationship, and the evaluation result of the first recommended integration relationship is better than the evaluation result of the second recommended integration relationship.

[0183] It can be understood that the acquisition unit 701, processing unit 702 and display unit 703 in the quality assessment device 700 of the cloud service architecture can be mapped as functional modules to the various subsystems in the quality assessment system 10 of the cloud service architecture in Figure 1, thereby realizing the functions of each module in the quality assessment system 10 of the cloud service architecture.

[0184] It should be understood that the division of units in the above device is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. Moreover, the units in the device can all be implemented in the form of software called through processing elements; or they can all be implemented in the form of hardware; or some units can be implemented in the form of software called through processing elements, and some units can be implemented in the form of hardware. For example, each unit can be a separately established processing element, or it can be integrated into a certain chip of the device. In addition, it can also be stored in the memory in the form of a program, called by a certain processing element of the device and perform the function of the unit. In addition, all or part of these units can be integrated together, or they can be implemented independently. The processing element described here can also be a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each unit above can be implemented by the integrated logic circuit of the hardware in the processor element or in the form of software called through the processing element.

[0185] It is worth noting that, for the sake of simplicity of description, the above method embodiments are all expressed as a series of action combinations. However, those skilled in the art should know that this application is not limited to the order of the actions described. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required for this application.

[0186] Other reasonable step combinations that can be thought of by those skilled in the art based on the above description also fall within the scope of protection of this application. Secondly, those skilled in the art should also be familiar with that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by this application.

[0187] Please refer to Figure 8, which is a schematic diagram of the structure of a computing device provided in an embodiment of the present application. As shown in Figure 8, the computing device 800 includes: a processor 801, a memory 802, a communication interface 803, and a bus 804. The processor 801, the memory 802, and the communication interface 803 are coupled via a bus (not labeled in the figure). The memory 802 stores instructions. When the execution instructions in the memory 802 are executed, the computing device 800 performs the method performed by the computing device in the above method embodiment.

[0188] The computing device 800 may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For example, when a unit in the device can be implemented in the form of a processing element scheduler, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call a program. For example, these units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0189] The processor 801 may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0190] Memory 802 may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0191] The memory 802 stores executable program code, and the processor 801 executes the executable program code to implement the functions of the aforementioned units or modules, thereby implementing the quality assessment method for the cloud service architecture. In other words, the memory 802 stores instructions for executing the quality assessment method for the cloud service architecture.

[0192] The communication interface 803 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 800 and other devices or a communication network.

[0193] In addition to the data bus, bus 804 may also include a power bus, a control bus, and a status signal bus. The bus may be a Peripheral Component Interconnect Express (PCIe) bus, an Extended Industry Standard Architecture (EISA) bus, a unified bus (Ubus or UB), a Compute Express Link (CXL), or a Cache Coherent Interconnect for Accelerators (CCIX). Buses can be categorized as address buses, data buses, and control buses.

[0194] Please refer to FIG9 , which is a schematic diagram of a computing device cluster provided in an embodiment of the present application. As shown in FIG9 , the computing device cluster 900 includes at least one computing device 800 .

[0195] 9 , the computing device cluster 900 includes at least one computing device 800. The memory 802 in one or more computing devices 800 in the computing device cluster 900 may store the same instructions for executing the quality assessment method for the cloud service architecture.

[0196] In some possible implementations, the memory 802 of one or more computing devices 800 in the computing device cluster 900 may also store partial instructions for executing the aforementioned cloud service architecture quality assessment method. In other words, the combination of one or more computing devices 800 can collectively execute instructions for executing the aforementioned cloud service architecture quality assessment method.

[0197] It should be noted that the memory 802 in different computing devices 800 in the computing device cluster 900 can store different instructions, each for executing a portion of the functions of the task processing apparatus described above. In other words, the instructions stored in the memory 802 in different computing devices 800 can implement the functions of one or more modules among the acquisition unit, processing unit, and display unit.

[0198] In some possible implementations, one or more computing devices 800 in the computing device cluster 900 may be connected via a network, which may be a wide area network or a local area network.

[0199] Please refer to Figure 10, which is a schematic diagram of computer devices in a computer cluster provided by an embodiment of the present application connected via a network. As shown in Figure 10, two computing devices 800A and 800B are connected via a network. Specifically, the connection to the network is through a communication interface in each computing device.

[0200] In one possible implementation, the memory of the computing device 800A stores instructions for executing the functions of the acquisition unit, while the memory of the computing device 800B stores instructions for executing the functions of the processing unit and the display unit.

[0201] It should be understood that the functions of the computing device 800A shown in Figure 10 may also be completed by multiple computing devices. Similarly, the functions of the computing device 800B may also be completed by multiple computing devices.

[0202] In another embodiment of the present application, a computer-readable storage medium is provided, in which computer-executable instructions are stored. When the processor of the device executes the computer-executable instructions, the device executes the method executed by the computing device in the above method embodiment.

[0203] In another embodiment of the present application, a computer program product is provided, the computer program product including computer-executable instructions stored in a computer-readable storage medium. When a processor of a device executes the computer-executable instructions, the device performs the method performed by the computing device in the above method embodiment.

[0204] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0205] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0206] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0207] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0208] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

Claims

1. A quality assessment method for a cloud service architecture, characterized in that: The method is applied to a cloud service platform, the cloud service platform is used to manage a cloud service architecture, the cloud service architecture includes at least two cloud services, and the method includes: Displaying a cloud architecture editing interface, wherein the cloud architecture editing interface includes at least one graphic element selection area, wherein the graphic element selection area includes at least one cloud graphic element, and the cloud graphic element corresponds to at least one cloud service; Acquire a user's graphic element selection instruction for a first cloud graphic element, where the first cloud graphic element corresponds to a first cloud service; Acquire a user's graphic element selection instruction for a second cloud graphic element, where the second cloud graphic element corresponds to a second cloud service; A cloud architecture diagram is displayed, wherein the cloud architecture diagram represents the cloud service architecture, the cloud architecture diagram includes the first cloud element and the second cloud element, the first cloud service and the second cloud service in the cloud service architecture have an integration relationship, and the integration relationship is expressed in at least one of the following ways: a connection line between the first cloud element and the second cloud element in the cloud architecture diagram, and an inclusion relationship between the first cloud element and the second cloud element in the cloud architecture diagram; The integration relationship between the first cloud service and the second cloud service is evaluated according to at least one of the following information: types of the first cloud service and the second cloud service, communication methods of the first cloud service and the second cloud service, and communication content of the first cloud service and the second cloud service, wherein the communication content of the first cloud service and the second cloud service includes at least one of the following: data content of communication between the first cloud service and the second cloud service, and data format of communication between the first cloud service and the second cloud service, and the communication method of the first cloud service and the second cloud service includes at least one of the following: communication protocol of the first cloud service and the second cloud service, and communication path of the first cloud service and the second cloud service; The integration relationship evaluation result between the first cloud service and the second cloud service is displayed to the user.

2. The method according to claim 1, characterized in that The method further comprises: According to the dependency information, a dependency evaluation result between the first cloud service and the third cloud service is given, wherein the dependency information includes at least one of the following: a strong dependency and a recommended dependency, wherein the strong dependency is that at least one of the first cloud service and the third cloud service exists in a binding relationship with another cloud service, and the recommended dependency is that at least one of the first cloud service and the third cloud service is recommended to exist together with another cloud service; The dependency evaluation result between the first cloud service and the third cloud service is displayed to the user, where the dependency evaluation result includes at least one of the following: lack of at least one cloud service and recommendation to add at least one cloud service.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: Parsing the cloud service architecture to obtain an integration relationship of cloud services included in the cloud service architecture; Based on the integration relationship of the cloud service, an integration relationship search is performed in the integration relationship knowledge graph to determine the associated integration relationship, and the associated integration relationship is used to determine the evaluation result of the integration relationship of the cloud service. The integration relationship knowledge graph is used to store the integration relationship between different cloud services.

4. The method according to claim 3, characterized in that The method further comprises: The integrated relationship knowledge graph is constructed based on the integrated relationship data. The integrated relationship knowledge graph includes nodes and edges. The nodes are used to represent cloud services, and the edges are used to represent the integrated relationship between cloud services. The cloud service integrated relationship data includes historical integrated relationship data of different cloud services.

5. The method according to any one of claims 1 to 4, characterized in that The integration relationship evaluation result includes one or more of the following: unknown integration relationship, prohibited integration relationship, not recommended integration relationship, optional integration relationship, and preferred integration relationship.

6. The method according to claim 5, characterized in that The method further comprises: When the integration relationship evaluation result is that the integration relationship is prohibited from selection or the integration relationship is not recommended, the reasons why the integration relationship is prohibited from selection or the integration relationship is not recommended are displayed to the user.

7. The method according to claim 5, characterized in that There is a mapping relationship between the integration relationship evaluation result and the integration relationship quality score, and the recommendation degree in the integration relationship evaluation result is associated with the integration relationship quality score.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: Providing a quality assessment calling interface, wherein the quality assessment calling interface is used to evaluate the integration relationship of different cloud service architectures; An integration relationship evaluation request is received through the quality evaluation calling interface, and an integration relationship evaluation result corresponding to the integration relationship evaluation request is sent through the quality evaluation calling interface.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: When the integration relationship quality score corresponding to the integration relationship evaluation result is greater than a score threshold, re-modifying the cloud service architecture; When the integration relationship quality score corresponding to the integration relationship evaluation result is less than or equal to the score threshold, the cloud service architecture is submitted for cloud service architecture review and cloud service architecture verification.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: A recommended integration relationship is displayed, where the recommended integration relationship includes at least two cloud services, and an evaluation result of the recommended integration relationship is better than an evaluation result of an integration relationship between the first cloud service and the second cloud service.

11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: A recommended integration relationship set is displayed, wherein the recommended integration relationship set includes a first recommended integration relationship and a second recommended integration relationship. In the recommended integration relationship set, the first recommended integration relationship is displayed better than the second recommended integration relationship, and an evaluation result of the first recommended integration relationship is better than an evaluation result of the second recommended integration relationship.

12. A quality assessment device for a cloud service architecture, characterized in that: The method is applied to a cloud service platform, the cloud service platform is used to manage a cloud service architecture, the cloud service architecture includes at least two cloud services, and the device includes: A display unit, used to display a cloud architecture editing interface, wherein the cloud architecture editing interface includes at least one graphic element selection area, wherein the graphic element selection area includes at least one cloud graphic element, and the cloud graphic element corresponds to at least one cloud service; An acquisition unit, configured to acquire a user's graphic element selection instruction for a first cloud graphic element, wherein the first cloud graphic element corresponds to a first cloud service; The acquisition unit is further used to acquire a graphic element selection instruction of a user for a second cloud graphic element, where the second cloud graphic element corresponds to a second cloud service; The display unit is further used to display a cloud architecture diagram, wherein the cloud architecture diagram represents the cloud service architecture, the cloud architecture diagram includes the first cloud element and the second cloud element, and the first cloud service and the second cloud service in the cloud service architecture have an integration relationship, and the integration relationship is expressed in at least one of the following ways: a connection line between the first cloud element and the second cloud element in the cloud architecture diagram, and an inclusion relationship between the first cloud element and the second cloud element in the cloud architecture diagram; a processing unit, configured to evaluate the integration relationship between the first cloud service and the second cloud service according to at least one of the following information: types of the first cloud service and the second cloud service, communication methods of the first cloud service and the second cloud service, and communication contents of the first cloud service and the second cloud service, wherein the communication contents of the first cloud service and the second cloud service include at least one of the following: data contents of communication between the first cloud service and the second cloud service, and data formats of communication between the first cloud service and the second cloud service, and the communication methods of the first cloud service and the second cloud service include at least one of the following: communication protocols of the first cloud service and the second cloud service, and communication paths of the first cloud service and the second cloud service; The display unit is further configured to display to the user an evaluation result of the integration relationship between the first cloud service and the second cloud service.

13. The device according to claim 12, characterized in that The processing unit is also used for: According to the dependency information, a dependency evaluation result between the first cloud service and the third cloud service is given, wherein the dependency information includes at least one of the following: a strong dependency and a recommended dependency, wherein the strong dependency is that at least one of the first cloud service and the third cloud service exists in a binding relationship with another cloud service, and the recommended dependency is that at least one of the first cloud service and the third cloud service is recommended to exist together with another cloud service; The display unit is further used to display to the user a dependency evaluation result between the first cloud service and the third cloud service, wherein the dependency evaluation result includes at least one of the following: lack of at least one cloud service and recommendation to add at least one cloud service.

14. The device according to claim 12 or 13, characterized in that The processing unit is also used for: Parsing the cloud service architecture to obtain an integration relationship of cloud services included in the cloud service architecture; Based on the integration relationship of the cloud service, an integration relationship search is performed in the integration relationship knowledge graph to determine the associated integration relationship, and the associated integration relationship is used to determine the evaluation result of the integration relationship of the cloud service. The integration relationship knowledge graph is used to store the integration relationship between different cloud services.

15. The device according to claim 14, characterized in that The processing unit is also used for: The integrated relationship knowledge graph is constructed based on the integrated relationship data. The integrated relationship knowledge graph includes nodes and edges. The nodes are used to represent cloud services, and the edges are used to represent the integrated relationship between cloud services. The cloud service integrated relationship data includes historical integrated relationship data of different cloud services.

16. The device according to any one of claims 12 to 15, characterized in that The integration relationship evaluation result includes one or more of the following: unknown integration relationship, prohibited integration relationship, not recommended integration relationship, optional integration relationship, and preferred integration relationship.

17. The device according to claim 16, characterized in that The display unit is also used for: When the integration relationship evaluation result is that the integration relationship is prohibited from selection or the integration relationship is not recommended, the reasons why the integration relationship is prohibited from selection or the integration relationship is not recommended are displayed to the user.

18. The device according to claim 16, characterized in that There is a mapping relationship between the integration relationship evaluation result and the integration relationship quality score, and the recommendation degree in the integration relationship evaluation result is associated with the integration relationship quality score.

19. The device according to any one of claims 12 to 18, characterized in that The processing unit is also used for: Providing a quality assessment calling interface, wherein the quality assessment calling interface is used to evaluate the integration relationship of different cloud service architectures; An integration relationship evaluation request is received through the quality evaluation calling interface, and an integration relationship evaluation result corresponding to the integration relationship evaluation request is sent through the quality evaluation calling interface.

20. The device according to any one of claims 12 to 19, characterized in that The processing unit is also used for: When the integration relationship quality score corresponding to the integration relationship evaluation result is greater than a score threshold, re-modifying the cloud service architecture; When the integration relationship quality score corresponding to the integration relationship evaluation result is less than or equal to the score threshold, the cloud service architecture is submitted for cloud service architecture review and cloud service architecture verification.

21. The device according to any one of claims 12 to 20, characterized in that The display unit is also used for: A recommended integration relationship is displayed, where the recommended integration relationship includes at least two cloud services, and an evaluation result of the recommended integration relationship is better than an evaluation result of an integration relationship between the first cloud service and the second cloud service.

22. The device according to any one of claims 12 to 21, characterized in that The display unit is also used for: A recommended integration relationship set is displayed, wherein the recommended integration relationship set includes a first recommended integration relationship and a second recommended integration relationship. In the recommended integration relationship set, the first recommended integration relationship is displayed better than the second recommended integration relationship, and an evaluation result of the first recommended integration relationship is better than an evaluation result of the second recommended integration relationship.

23. A computing device cluster, characterized in that: The method comprises at least one computing device, wherein the computing device comprises a processor, wherein the processor is coupled to a memory, and the processor is used to store instructions. When the instructions are executed by the processor, the computing device cluster executes the method according to any one of claims 1 to 11.

24. A computer-readable storage medium having instructions stored thereon, characterized in that: When the instructions are executed, the computer is caused to perform the method according to any one of claims 1 to 11.

25. A computer program product, comprising instructions, characterized in that: When the instructions are executed, the computer implements the method according to any one of claims 1 to 11.

Images