Visual architecture definition and management method and device based on micro-service architecture
By using a visual architecture definition and management method and device based on microservice architecture, the problem of the difficulty in reusing traditional technical architectures is solved, and the visualization and efficient processing of architecture management are realized, reducing the operational difficulty of the technology stack.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SHENZHEN COMTOP INFORMATION TECH
- Filing Date
- 2022-10-19
- Publication Date
- 2026-07-14
AI Technical Summary
Traditional technical architecture construction and writing methods suffer from problems such as different structural layering methods, difficulty in reuse, high difficulty in operating the technology stack, and lack of visibility of the technical architecture.
A method and apparatus for visual architecture definition and control based on microservice architecture is provided. By detecting architecture control commands, the method automatically determines the target microservice and architecture control type, obtains architecture control requirements, executes parameter configuration operations, and displays the results through a visualization module, thereby reducing the difficulty of reuse and the difficulty of selecting stack technologies.
It improves the efficiency of architecture management and processing, realizes the visualization of architecture management operations, and reduces the difficulty of reusing technical architecture and selecting stack technology.
Smart Images
Figure CN115599368B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of architecture management technology, and in particular to a visual architecture definition and management method and apparatus based on microservice architecture. Background Technology
[0002] In the process of translating product requirements into technical implementation, a common auxiliary tool is technical architecture. When analyzing and solving technical problems through technical architecture, the main starting points include: how to perform pure technical layering, development framework selection, language selection (primarily Java here), and the technical aspects of solving the various non-functional requirements involved in the problem (security, performance, big data), etc. Technical architecture specifically encompasses: the technical components involved in the actual operation of the application system, the relationships between these components, and the hardware deployment strategy.
[0003] However, the traditional methods of constructing and writing technical architectures have the following drawbacks:
[0004] 1. Due to system requirements, personal experience, and personal habits, the final technical architectures constructed often exhibit different layering methods and diverse structures, making them difficult to reuse. 2. The selection of technology stacks for technical architectures is complex and frequently results in incompatibility with the underlying framework. 3. After the technical architecture design is completed, it is not possible to intuitively view the dependencies and configuration files.
[0005] It is evident that reducing the difficulty of reusing technical architecture, the difficulty of operating the technology stack, and solving the problem of the invisibility of technical architecture are particularly important. Summary of the Invention
[0006] The technical problem to be solved by the present invention is to provide a method and device for visual architecture definition and management based on microservice architecture, which can reduce the difficulty of reusing technical architecture and the difficulty of operating the technology stack, while solving the problem of the invisibility after the technical architecture is adjusted.
[0007] To address the aforementioned technical problems, the first aspect of this invention discloses a visual architecture definition and management method based on a microservice architecture, the method comprising:
[0008] Detect the presence of architecture control instructions, which are instructions triggered by the target user to perform architecture configuration control operations on a preset editable microservice architecture;
[0009] When the architecture control instruction is detected, the target microservice corresponding to the architecture control instruction, the architecture to be controlled corresponding to the target microservice, and the architecture control type for the architecture to be controlled are determined. The architecture control type includes a first-level control type or a non-first-level control type. The first-level control type is a control type that requires parameter configuration operations to be performed on the architecture parameters of the architecture to be controlled. The architecture to be controlled includes several layered architectures, and each layered architecture includes architecture parameters corresponding to that layered architecture.
[0010] When the architecture management type of the architecture to be managed is determined to be the first-level management type, the architecture management requirements for the architecture to be managed are obtained, and the parameter configuration operation is performed on the architecture parameters of the architecture to be managed according to the architecture management requirements to obtain the parameter configuration result corresponding to the architecture to be managed. The parameter configuration result includes the updated architecture parameters after the parameter configuration operation is performed, and the parameter configuration result is displayed to the target user through the visualization module corresponding to the architecture to be managed.
[0011] As an optional implementation, in the first aspect of the present invention, when it is determined that the architecture management type of the architecture to be managed is the non-level 1 management type, the method further includes:
[0012] Determine the parent microservice of the target microservice, wherein the parent microservice of the target microservice is the microservice that corresponds to the highest service level of the target microservice in the preset service hierarchy;
[0013] Detect the architecture configuration status corresponding to the parent microservice. The architecture configuration status includes a first-level configuration status or a non-first-level configuration status, which indicates that the parent architecture corresponding to the parent microservice has completed the architecture configuration.
[0014] When the architecture configuration status corresponding to the parent microservice is detected to be non-first-level configuration status, the pre-determined standard architecture corresponding to the parent microservice is determined as the parent architecture corresponding to the parent microservice to update the parent architecture. The parent architecture is used to display to the target user through the visualization module corresponding to the architecture to be managed.
[0015] As an optional implementation, in the first aspect of the invention, each of the layered architectures further includes an editable component corresponding to the layered architecture, and each editable component includes an attribution technical asset matching the editable component;
[0016] The step of performing the parameter configuration operation on the architecture parameters of the architecture to be managed according to the architecture management requirements, and obtaining the parameter configuration result corresponding to the architecture to be managed, includes:
[0017] Among all the editable components, a target editing component that matches the architecture control requirements is identified, and among all the attribution technical assets corresponding to the target editing component, a target editing technical asset that matches the architecture control requirements is identified;
[0018] Based on the component identifier of the target editing component and the asset identifier of the target editing technology asset, the parameter configuration operation is performed on the architecture parameters of the architecture to be managed to obtain the parameter configuration result corresponding to the architecture to be managed.
[0019] As an optional implementation, in the first aspect of the present invention, the step of performing the parameter configuration operation on the architecture parameters of the architecture to be managed based on the component identifier of the target editing component and the asset identifier of the target editing technology asset, to obtain the parameter configuration result corresponding to the architecture to be managed, includes:
[0020] The target hierarchical architecture to which the target editing component belongs is determined based on the component identifier of the target editing component;
[0021] Based on the architecture management requirements, determine the hierarchical architecture to be managed for the target editing component;
[0022] Determine whether the target layered architecture is consistent with the layered architecture to be managed. If it is determined that the target layered architecture is consistent with the layered architecture to be managed, perform the parameter configuration operation on the architecture parameters of the architecture to be managed according to the architecture management requirements based on the asset identifier of the target editing technology asset, and obtain the parameter configuration result corresponding to the architecture to be managed.
[0023] As an optional implementation, in the first aspect of the present invention, when it is determined that the target layered architecture is inconsistent with the layered architecture to be managed, the method further includes:
[0024] Generate a disable flag to indicate that the target hierarchical architecture is inconsistent with the hierarchical architecture to be managed;
[0025] The system prompts the target user that the architecture management requirement is unenforceable based on the disabled flag, and obtains the adjustment instructions from the target user regarding the disabled flag, so as to update the architecture management instructions corresponding to the architecture management requirement based on the adjustment instructions.
[0026] As an optional implementation, in the first aspect of the present invention, the method further includes:
[0027] Based on the parameter configuration results, the architecture to be managed is updated to a reusable architecture with completed parameter configuration;
[0028] Detect the presence of architecture reuse control instructions, which are instructions used to perform architecture reuse operations on any technical architecture;
[0029] When the architecture reuse control instruction is detected, the reuse type of the architecture to be reused is determined. The reuse type includes the database reuse type or the community reuse type. The database reuse type is the selection and reuse of the corresponding type of technical architecture from a preset architecture repository. The community reuse type is the selection and reuse of the corresponding type of technical architecture from a preset asset community.
[0030] Based on the reuse type, a target reuse architecture corresponding to the architecture reuse control instruction is determined as the architecture to be reused.
[0031] As an optional implementation, in the first aspect of the present invention, after determining the target reuse architecture corresponding to the architecture reuse control instruction based on the reuse type as the architecture to be reused, the method further includes:
[0032] For the architecture to be reused and the reuse architecture parameters corresponding to the architecture to be reused, generate a target reuse project that matches the architecture to be reused according to the determined microservice management requirements;
[0033] According to the architecture reuse control instruction, a reuse parameter verification operation is performed on the target reuse project to obtain the parameter verification result corresponding to the target reuse project;
[0034] When the parameter verification result indicates that the reuse architecture parameters of the target reuse project do not match the preliminary adjustment result for the reuse architecture parameters in the architecture reuse control instruction, the target reuse project is updated according to the preliminary adjustment result, which is the expected result after performing the architecture reuse operation on the architecture to be reused through the architecture reuse control instruction.
[0035] A second aspect of this invention discloses a visual architecture definition and management device based on a microservice architecture, the device comprising:
[0036] The detection module is used to detect whether there are architecture control instructions, which are instructions triggered by the target user to perform architecture configuration control operations on a preset editable microservice architecture;
[0037] The determination module is used to determine the target microservice corresponding to the architecture management instruction, the architecture to be managed corresponding to the target microservice, and the architecture management type for the architecture to be managed when the detection module detects the existence of the architecture management instruction. The architecture management type includes a first-level management type or a non-first-level management type. The first-level management type is a management type that requires parameter configuration operations to be performed on the architecture parameters of the architecture to be managed. The architecture to be managed includes several layered architectures, and each layered architecture includes architecture parameters corresponding to that layered architecture.
[0038] The acquisition module is used to acquire the architecture control requirements for the architecture to be controlled when it is determined that the architecture control type of the architecture to be controlled is the first-level control type.
[0039] The parameter configuration module is used to perform the parameter configuration operation on the architecture parameters of the architecture to be managed according to the architecture management requirements, and obtain the parameter configuration result corresponding to the architecture to be managed. The parameter configuration result includes the updated architecture parameters after performing the parameter configuration operation. The parameter configuration result is displayed to the target user through the visualization module corresponding to the architecture to be managed.
[0040] As an optional implementation, in the second aspect of the present invention, the determining module is further configured to determine the parent microservice of the target microservice when it is determined that the architecture management type of the architecture to be managed is the non-first-level management type, wherein the parent microservice of the target microservice is the microservice corresponding to the highest service level of the target microservice in the preset service hierarchy;
[0041] The detection module is also used to detect the architecture configuration status corresponding to the parent microservice. The architecture configuration status includes a first-level configuration status or a non-first-level configuration status, which indicates that the parent architecture corresponding to the parent microservice has completed the architecture configuration.
[0042] The determining module is further configured to, when it detects that the architecture configuration status corresponding to the parent microservice is the non-first-level configuration status, determine the pre-determined standard architecture corresponding to the parent microservice as the parent architecture corresponding to the parent microservice, so as to update the parent architecture. The parent architecture is used to be displayed to the target user through the visualization module corresponding to the architecture to be managed.
[0043] As an optional implementation, in a second aspect of the invention, each of the layered architectures further includes an editable component corresponding to the layered architecture, and each editable component includes an attribution technical asset matching the editable component;
[0044] The parameter configuration module includes:
[0045] The determination submodule is used to determine the target editing component that matches the architecture management requirements among all the editable components, and to determine the target editing technology asset that matches the architecture management requirements among all the ownership technology assets corresponding to the target editing component;
[0046] The configuration submodule is used to perform the parameter configuration operation on the architecture parameters of the architecture to be managed based on the component identifier of the target editing component and the asset identifier of the target editing technology asset, so as to obtain the parameter configuration result corresponding to the architecture to be managed.
[0047] As an optional implementation, in the second aspect of the present invention, the configuration submodule performs the parameter configuration operation on the architecture parameters of the architecture to be managed based on the component identifier of the target editing component and the asset identifier of the target editing technology asset, and obtains the parameter configuration result corresponding to the architecture to be managed in the following specific ways:
[0048] The target hierarchical architecture to which the target editing component belongs is determined based on the component identifier of the target editing component;
[0049] Based on the architecture management requirements, determine the hierarchical architecture to be managed for the target editing component;
[0050] Determine whether the target layered architecture is consistent with the layered architecture to be managed. If it is determined that the target layered architecture is consistent with the layered architecture to be managed, perform the parameter configuration operation on the architecture parameters of the architecture to be managed according to the architecture management requirements based on the asset identifier of the target editing technology asset, and obtain the parameter configuration result corresponding to the architecture to be managed.
[0051] As an optional implementation, in a second aspect of the invention, the configuration submodule is further configured to:
[0052] When it is determined that the target layer architecture is inconsistent with the layer architecture to be managed, a disable flag is generated to indicate that the target layer architecture is inconsistent with the layer architecture to be managed.
[0053] The system prompts the target user that the architecture management requirement is unenforceable based on the disabled flag, and obtains the adjustment instructions from the target user regarding the disabled flag, so as to update the architecture management instructions corresponding to the architecture management requirement based on the adjustment instructions.
[0054] As an optional implementation, in a second aspect of the invention, the apparatus further includes:
[0055] The update module is used to update the architecture to be managed into a reusable architecture with completed parameter configuration based on the parameter configuration results.
[0056] The detection module is also used to detect whether there is an architecture reuse control instruction, which is an instruction used to perform architecture reuse operation on any technical architecture;
[0057] The determining module is further configured to determine the reuse type of the architecture to be reused when the architecture reuse control instruction is detected. The reuse type includes an inbound reuse type or a community reuse type. The inbound reuse type is the selection and reuse of the corresponding type of technical architecture from a preset architecture repository. The community reuse type is the selection and reuse of the corresponding type of technical architecture from a preset asset community.
[0058] The determining module is further configured to determine, based on the reuse type, a target reuse architecture corresponding to the architecture reuse control instruction, as the architecture to be reused.
[0059] As an optional implementation, in a second aspect of the invention, the apparatus further includes:
[0060] The generation module is used to generate a target reuse architecture that matches the architecture reuse control instruction based on the reuse type, after the determining module determines the target reuse architecture as the architecture to be reused, and generates a target reuse project that matches the architecture to be reused based on the architecture to be reused and the reuse architecture parameters corresponding to the architecture to be reused, according to the determined microservice control requirements.
[0061] The verification module is used to perform a reuse parameter verification operation on the target reuse project according to the architecture reuse control instruction, and obtain the parameter verification result corresponding to the target reuse project;
[0062] The update module is further configured to update the target reuse project according to the pre-adjustment result when the parameter verification result indicates that the reuse architecture parameters of the target reuse project do not match the pre-adjustment result for the reuse architecture parameters in the architecture reuse control instruction. The pre-adjustment result is the expected result obtained after performing the architecture reuse operation on the architecture to be reused through the architecture reuse control instruction.
[0063] A third aspect of this invention discloses another visual architecture definition and management device based on microservice architecture, the device comprising:
[0064] Memory containing executable program code;
[0065] A processor coupled to the memory;
[0066] The processor calls the executable program code stored in the memory to execute the visual architecture definition and management method based on microservice architecture disclosed in the first aspect of the present invention.
[0067] The fourth aspect of this invention discloses a computer storage medium storing computer instructions, which, when invoked, are used to execute the visual architecture definition and management method based on microservice architecture disclosed in the first aspect of this invention.
[0068] Compared with the prior art, the embodiments of the present invention have the following beneficial effects:
[0069] This invention provides a method for visual architecture definition and control based on a microservice architecture. The method includes: detecting the existence of an architecture control instruction, where the instruction is triggered by a target user to perform architecture configuration control operations on a preset editable microservice architecture; when an architecture control instruction is detected, determining the target microservice corresponding to the instruction, the architecture to be controlled corresponding to the target microservice, and the architecture control type for the architecture to be controlled, where the architecture control type includes a first-level control type or a non-first-level control type, and the first-level control type is a control type that requires parameter configuration operations to be performed on the architecture parameters of the architecture to be controlled; the architecture to be controlled includes several layered architectures, each layered architecture including architecture parameters corresponding to that layered architecture; when the architecture control type of the architecture to be controlled is determined to be a first-level control type, obtaining the architecture control requirements for the architecture to be controlled, and performing parameter configuration operations on the architecture parameters of the architecture to be controlled according to the architecture control requirements to obtain the parameter configuration result corresponding to the architecture to be controlled, the parameter configuration result including the updated architecture parameters after performing the parameter configuration operation, and displaying the parameter configuration result to the target user through a visualization module corresponding to the architecture to be controlled. As can be seen, implementing this invention can automatically determine the target microservice, the architecture to be managed, and the architecture management type corresponding to the detected architecture management command. This allows for the automatic acquisition of architecture management requirements for the primary management type, followed by intelligent parameter configuration operations on the architecture parameters of the architecture to be managed. The parameter configuration results are then displayed to the target user through a visualization module, improving the efficiency of management and control processing for the architecture to be managed and enabling visualization of architecture management operations. Furthermore, the visualized technical architecture facilitates user filtering and reuse, reducing the difficulty of reusing technical architectures and selecting stack technologies. Attached Figure Description
[0070] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0071] Figure 1This is a flowchart illustrating a visual architecture definition and management method based on microservice architecture disclosed in an embodiment of the present invention.
[0072] Figure 2 This is a flowchart illustrating another method for visual architecture definition and management based on microservice architecture disclosed in an embodiment of the present invention.
[0073] Figure 3 This is a schematic diagram of the structure of a visual architecture definition and management device based on microservice architecture disclosed in an embodiment of the present invention;
[0074] Figure 4 This is a schematic diagram of another visual architecture definition and management device based on microservice architecture disclosed in an embodiment of the present invention;
[0075] Figure 5 This is a schematic diagram of the structure of another visual architecture definition and management device based on microservice architecture disclosed in an embodiment of the present invention. Detailed Implementation
[0076] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0077] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this invention are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or end that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or ends.
[0078] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.
[0079] This invention discloses a visual architecture definition and management method and apparatus based on microservice architecture. Upon detecting an architecture management command, it automatically determines the target microservice, the architecture to be managed, and the architecture management type corresponding to the command. This allows for the automatic acquisition of architecture management requirements for the primary management type, followed by intelligent parameter configuration operations on the architecture parameters of the architecture to be managed. The configuration results are then displayed to the target user through a visualization module, improving the efficiency of management processing for the architecture to be managed and providing visualization functionality for architecture management operations. Furthermore, the visualized technical architecture facilitates user selection and reuse, reducing the difficulty of reusing technical architectures and choosing stack technologies. These will be described in detail below.
[0080] Example 1
[0081] Please see Figure 1 , Figure 1 This is a flowchart illustrating a visual architecture definition and management method based on a microservice architecture disclosed in an embodiment of the present invention. Figure 1 The described method for visual architecture definition and management based on microservice architecture can be applied to a device for visual architecture definition and management based on microservice architecture, and this embodiment of the invention is not limited thereto. Figure 1 As shown, this visual architecture definition and management method based on microservice architecture can include the following operations:
[0082] 101. Detect whether there are architecture control instructions. Architecture control instructions are instructions triggered by the target user to perform architecture configuration control operations on the preset editable microservice architecture.
[0083] 102. When an architecture control instruction is detected, determine the target microservice corresponding to the architecture control instruction, the architecture to be controlled corresponding to the target microservice, and the architecture control type for the architecture to be controlled. The architecture control type includes first-level control type or non-first-level control type.
[0084] In this embodiment of the invention, the first-level control type is the control type that requires parameter configuration operations to be performed on the architecture parameters of the architecture to be controlled. The architecture to be controlled includes several layered architectures, and each layered architecture includes architecture parameters corresponding to that layered architecture.
[0085] 103. When the architecture control type of the architecture to be controlled is determined to be a level 1 control type, obtain the architecture control requirements for the architecture to be controlled.
[0086] 104. Based on the architecture management requirements, perform parameter configuration operations on the architecture parameters of the architecture to be managed to obtain the parameter configuration results corresponding to the architecture to be managed.
[0087] In this embodiment of the invention, the parameter configuration result includes the updated architecture parameters after performing the parameter configuration operation, and the parameter configuration result is displayed to the target user through the visualization module corresponding to the architecture to be managed.
[0088] In this embodiment of the invention, it should be noted that the architecture management requirement specifically instructs the user on the display interface. Specifically, it can be the user defining, viewing, adjusting attribute configurations, and reusing the architecture of the microservices and technical architecture provided on the display interface. This embodiment of the invention does not limit this.
[0089] It is evident that implementation Figure 1 The described visual architecture definition and control method based on microservice architecture can automatically determine the target microservice, the architecture to be managed, and the architecture control type corresponding to the detected architecture control command. It then automatically obtains the architecture control requirements for the primary control type, intelligently performs parameter configuration operations on the architecture parameters of the architecture to be managed, and displays the configuration results to the target user through a visualization module. This improves the efficiency of control processing for the architecture to be managed and enables visualization of architecture control operations. Furthermore, the visualized technical architecture facilitates user selection and reuse, reducing the difficulty of reusing technical architectures and selecting stack technologies.
[0090] In an optional embodiment, the method may further include the following operations:
[0091] Based on the parameter configuration results, update the architecture to be managed to a reusable architecture with completed parameter configuration;
[0092] Detect the presence of architecture reuse control instructions, which are used to perform architecture reuse operations on any technical architecture;
[0093] When an architecture reuse control instruction is detected, the reuse type of the architecture to be reused is determined. The reuse type includes the database reuse type or the community reuse type. The database reuse type is to select and reuse the corresponding type of technical architecture from the preset architecture repository. The community reuse type is to select and reuse the corresponding type of technical architecture from the preset asset community.
[0094] Based on the reuse type, determine the target reuse architecture corresponding to the architecture reuse control instruction, and use it as the architecture to be reused.
[0095] It should be noted that the architecture to be reused corresponding to this type of inbound reuse is specifically the architecture whose architecture parameters have been configured and stored in the architecture repository.
[0096] Furthermore, after determining the target reuse architecture corresponding to the architecture reuse control instruction based on the reuse type, as the architecture to be reused, the method may also include the following operations:
[0097] Based on the reusable architecture and the corresponding reusable architecture parameters, generate a target reusable project that matches the architecture to be reused, according to the determined microservice management requirements;
[0098] According to the architecture reuse control instructions, perform reuse parameter verification operations on the target reuse project to obtain the parameter verification results corresponding to the target reuse project;
[0099] When the parameter verification result indicates that the reuse architecture parameters of the target reuse project do not match the preliminary adjustment results for the reuse architecture parameters in the architecture reuse control instruction, the target reuse project is updated according to the preliminary adjustment results. The preliminary adjustment results are the expected results after the architecture reuse operation is performed on the architecture to be reused through the architecture reuse control instruction.
[0100] It should be noted that the reuse architecture parameters corresponding to the architecture to be reused include the technical architecture associated with the architecture to be reused, specific dependencies, and related asset architecture configurations, etc., which are not limited in this embodiment of the invention.
[0101] As can be seen, in this optional embodiment, the reuse type of the architecture to be reused can be automatically determined based on the detected architecture reuse control instructions, thereby determining the architecture to be reused, reducing the reuse difficulty of performing architecture reuse operations on the architecture to be reused and improving reuse efficiency; it can also intelligently verify the target reuse project after generating the target reuse project, and then intelligently update the target reuse project that does not match the pre-adjustment results, thereby improving the reuse accuracy and reliability of the final target reuse project.
[0102] Example 2
[0103] Please see Figure 2 , Figure 2 This is a flowchart illustrating another method for visual architecture definition and management based on microservice architecture disclosed in an embodiment of the present invention. Figure 2 The described method for visual architecture definition and management based on microservice architecture can be applied to a device for visual architecture definition and management based on microservice architecture, and this embodiment of the invention is not limited thereto. Figure 2 As shown, this visual architecture definition and management method based on microservice architecture can include the following operations:
[0104] 201. Detect the existence of architecture control commands. Architecture control commands are commands triggered by the target user to perform architecture configuration control operations on a preset editable microservice architecture.
[0105] 202. When an architecture control instruction is detected, determine the target microservice corresponding to the architecture control instruction, the architecture to be controlled corresponding to the target microservice, and the architecture control type for the architecture to be controlled. The architecture control type includes first-level control type or non-first-level control type.
[0106] 203. When the architecture control type of the architecture to be controlled is determined to be a level 1 control type, obtain the architecture control requirements for the architecture to be controlled.
[0107] 204. Based on the architecture management requirements, perform parameter configuration operations on the architecture parameters of the architecture to be managed to obtain the parameter configuration results corresponding to the architecture to be managed.
[0108] For further descriptions of steps 201-204 in this embodiment of the invention, please refer to the other specific descriptions of steps 101-104 in Embodiment 1. These descriptions will not be repeated in this embodiment of the invention.
[0109] 205. When it is determined that the architecture management type of the architecture to be managed is not a first-level management type, determine the parent microservice of the target microservice.
[0110] In this embodiment of the invention, the parent microservice of the target microservice is the microservice that corresponds to the highest service level of the target microservice in the preset service hierarchy.
[0111] 206. Detect the architecture configuration status corresponding to the parent microservice. The architecture configuration status includes a first-level configuration status or a non-first-level configuration status, which indicates that the parent architecture corresponding to the parent microservice has completed the architecture configuration.
[0112] 207. When it is detected that the architecture configuration status corresponding to the parent microservice is not in the first-level configuration status, the pre-determined standard architecture corresponding to the parent microservice will be determined as the parent architecture corresponding to the parent microservice, so as to update the parent architecture.
[0113] In this embodiment of the invention, the parent architecture is used to display the architecture to be managed to the target user through the visualization module corresponding to the architecture to be managed. Specifically, the target user can view the dependencies required by the architecture and the configuration files required by the architecture through the visualization module. The user can also modify the version of the corresponding technical architecture, the asset configuration of the corresponding technical architecture, attributes, etc. through the interface.
[0114] It is evident that implementation Figure 2The described visual architecture definition and management method based on microservice architecture, for non-first-level management types, can intelligently determine the parent microservice of the target microservice, and then intelligently update the parent architecture based on the architecture configuration status of the parent microservice through the standard architecture. This ensures that even if the user does not configure or adjust the microservice / technical architecture, the target microservice still has a default available technical architecture, which helps to reduce the difficulty for users to manage and reuse the technical architecture of the target microservice.
[0115] In an optional embodiment, each hierarchical architecture further includes an editable component corresponding to the hierarchical architecture, and each editable component includes an attribution technical asset matching the editable component;
[0116] The above-mentioned method of performing parameter configuration operations on the architecture parameters of the architecture to be managed according to the architecture management requirements, and obtaining the parameter configuration results corresponding to the architecture to be managed, may specifically include the following operations:
[0117] Identify the target editing components that match the architecture control requirements from all editable components, and identify the target editing technical assets that match the architecture control requirements from all the associated technical assets of the target editing components;
[0118] Based on the component identifier of the target editing component and the asset identifier of the target editing technology asset, perform parameter configuration operations on the architecture parameters of the architecture to be managed, and obtain the parameter configuration results corresponding to the architecture to be managed.
[0119] Specifically, each architecture to be managed may include four layered structures: interaction layer, scenario layer, domain layer, and external service layer.
[0120] Optionally, the method of performing parameter configuration operations on the architecture parameters of the architecture to be managed based on the component identifier of the target editing component and the asset identifier of the target editing technology asset, to obtain the parameter configuration results corresponding to the architecture to be managed, may specifically include the following operations:
[0121] The target hierarchical architecture to which the target editing component belongs is determined based on the component identifier of the target editing component;
[0122] Determine the hierarchical architecture to be managed for the current management target editing component based on the architecture management requirements;
[0123] Determine whether the target layered architecture is consistent with the layered architecture to be managed. If the target layered architecture is consistent with the layered architecture to be managed, perform parameter configuration operations on the architecture parameters of the architecture to be managed according to the architecture management requirements based on the asset identifier of the target editing technical asset, and obtain the parameter configuration results corresponding to the architecture to be managed.
[0124] Optionally, when it is determined that the target layered architecture is inconsistent with the layered architecture to be managed, the method may further include the following operations:
[0125] Generate a disable flag to indicate inconsistency between the target hierarchical architecture and the hierarchical architecture to be managed;
[0126] The system indicates that the target user's architecture management requirement cannot be executed based on the disabled flag, and obtains the adjustment instructions from the target user regarding the disabled flag. The system then updates the architecture management instructions corresponding to the architecture management requirement based on the adjustment instructions.
[0127] Specifically, in practical applications, all technical architectures (including the overall technical architecture, components of each layer, etc.) can be displayed to users in the form of an interface. Through the editable options on the left side of the display interface, users can select and drag any technical architecture asset to the functional group that matches the technical architecture asset, thereby realizing online definition of the technical architecture, moving, deleting, copying, and editing of attributes.
[0128] As can be seen, in this optional embodiment, after obtaining the architecture management requirements, the target editing components and target editing technical assets corresponding to the architecture management requirements can be intelligently determined, which improves the management accuracy of subsequent architecture management operations; and before performing parameter configuration operations on the target editing components, it is intelligently determined whether the target layered architecture is consistent with the layered architecture to be managed. If not, a disable flag is generated to reduce the occurrence of errors in the target reuse project generated in the group due to user misoperation, thereby improving the operational accuracy of parameter configuration operations on the architecture to be managed.
[0129] Example 3
[0130] Please see Figure 3 , Figure 3 This is a schematic diagram of a visual architecture definition and management device based on a microservice architecture, as disclosed in an embodiment of the present invention. The device can be a visual architecture definition and management terminal, a visual architecture definition and management device, a visual architecture definition and management system, or a visual architecture definition and management server. The visual architecture definition and management server can be a local server, a remote server, or a cloud server (also known as a cloud server). When the visual architecture definition and management server is not a cloud server, it can communicate with the cloud server; this embodiment of the present invention does not impose any limitations. Figure 3As shown, the visual architecture definition and management device based on microservice architecture may include a detection module 301, a determination module 302, an acquisition module 303, and a parameter configuration module 304, wherein:
[0131] The detection module 301 is used to detect whether there are architecture control instructions. Architecture control instructions are instructions triggered by the target user to perform architecture configuration control operations on a preset editable microservice architecture.
[0132] The determination module 302 is used to determine the target microservice corresponding to the architecture control instruction, the architecture to be managed corresponding to the target microservice, and the architecture control type for the architecture to be managed when the detection module 301 detects the existence of the architecture control instruction. The architecture control type includes a first-level control type or a non-first-level control type. The first-level control type is the control type that requires parameter configuration operations to be performed on the architecture parameters of the architecture to be managed. The architecture to be managed includes several layered architectures, and each layered architecture includes architecture parameters corresponding to that layered architecture.
[0133] The acquisition module 303 is used to acquire the architecture control requirements for the architecture to be controlled when the architecture control type of the architecture to be controlled is determined to be a level 1 control type.
[0134] The parameter configuration module 304 is used to perform parameter configuration operations on the architecture parameters of the architecture to be managed according to the architecture management requirements, and obtain the parameter configuration results corresponding to the architecture to be managed. The parameter configuration results include the updated architecture parameters after the parameter configuration operations are performed. The parameter configuration results are displayed to the target user through the visualization module corresponding to the architecture to be managed.
[0135] It is evident that implementation is as follows Figure 3 The described microservice-based visual architecture definition and control device can automatically determine the target microservice, the architecture to be managed, and the architecture control type corresponding to the detected architecture control command. It then automatically obtains the architecture control requirements for the primary control type, intelligently performs parameter configuration operations on the architecture parameters of the architecture to be managed, and displays the configuration results to the target user through a visualization module. This improves the efficiency of control processing for the architecture to be managed and enables visualization of architecture control operations. Furthermore, the visualized technical architecture facilitates user selection and reuse, reducing the difficulty of reusing technical architectures and selecting stack technologies.
[0136] In an optional embodiment, the determining module 302 is further configured to determine the parent microservice of the target microservice when the architecture management type of the architecture to be managed is determined to be a non-level 1 management type. The parent microservice of the target microservice is the microservice that corresponds to the highest service level of the target microservice in the preset service hierarchy.
[0137] The detection module 301 is also used to detect the architecture configuration status corresponding to the parent microservice. The architecture configuration status includes a first-level configuration status or a non-first-level configuration status, which indicates that the parent architecture corresponding to the parent microservice has completed the architecture configuration.
[0138] The determination module 302 is also used to determine the pre-determined standard architecture corresponding to the parent microservice as the parent architecture corresponding to the parent microservice when the architecture configuration status corresponding to the parent microservice is detected to be a non-first-level configuration status, so as to update the parent architecture. The parent architecture is used to display to the target user through the visualization module corresponding to the architecture to be managed.
[0139] It is evident that implementation is as follows Figure 3 The described visual architecture definition and management device based on microservice architecture can intelligently determine the parent microservice of the target microservice for non-first-level management types. Then, based on the architecture configuration status of the parent microservice, it can intelligently update the parent architecture through the standard architecture. This ensures that even if the user does not configure or adjust the microservice / technical architecture, the target microservice still has a default available technical architecture. In other words, it helps to reduce the difficulty for users to manage and reuse the technical architecture of the target microservice.
[0140] In another alternative embodiment, each hierarchical architecture also includes an editable component corresponding to the hierarchical architecture, and each editable component includes an attribution technology asset that matches the editable component.
[0141] like Figure 4 As shown, the parameter configuration module 304 includes a determination submodule 3041 and a configuration submodule 3042, wherein:
[0142] The determination submodule 3041 is used to determine the target editing component that matches the architecture control requirements among all editable components, and to determine the target editing technical assets that match the architecture control requirements among all the associated technical assets of the target editing component.
[0143] The configuration submodule 3042 is used to perform parameter configuration operations on the architecture parameters of the architecture to be managed based on the component identifier of the target editing component and the asset identifier of the target editing technology asset, and obtain the parameter configuration results corresponding to the architecture to be managed.
[0144] In this optional embodiment, optionally, the configuration submodule 3042 performs parameter configuration operations on the architecture parameters of the architecture to be managed based on the component identifier of the target editing component and the asset identifier of the target editing technology asset, and obtains the parameter configuration result corresponding to the architecture to be managed in the following specific ways:
[0145] The target hierarchical architecture to which the target editing component belongs is determined based on the component identifier of the target editing component;
[0146] Determine the hierarchical architecture to be managed for the current management target editing component based on the architecture management requirements;
[0147] Determine whether the target layered architecture is consistent with the layered architecture to be managed. If the target layered architecture is consistent with the layered architecture to be managed, perform parameter configuration operations on the architecture parameters of the architecture to be managed according to the architecture management requirements based on the asset identifier of the target editing technical asset, and obtain the parameter configuration results corresponding to the architecture to be managed.
[0148] Optionally, configuration submodule 3042 is also used for:
[0149] When it is determined that the target layer architecture is inconsistent with the layer architecture to be managed, a disabling flag is generated to indicate that the target layer architecture is inconsistent with the layer architecture to be managed.
[0150] The system indicates that the target user's architecture management requirement cannot be executed based on the disabled flag, and obtains the adjustment instructions from the target user regarding the disabled flag. The system then updates the architecture management instructions corresponding to the architecture management requirement based on the adjustment instructions.
[0151] It is evident that implementation is as follows Figure 4 The described microservice-based visual architecture definition and control device, upon receiving architecture control requirements, can intelligently determine the target editing components and target editing technical assets corresponding to those requirements, improving the accuracy of subsequent architecture control operations. Furthermore, before performing parameter configuration operations on the target editing components, it intelligently determines whether the target layered architecture is consistent with the layered architecture to be controlled. If not, it generates a disable flag to reduce errors in target reuse projects generated in the group due to user misoperation, thus improving the accuracy of parameter configuration operations on the architecture to be controlled.
[0152] In yet another alternative embodiment, such as Figure 4 As shown, the device also includes an update module 305, wherein:
[0153] Update module 305 is used to update the architecture to be managed to a reusable architecture with completed parameter configuration based on the parameter configuration results.
[0154] The detection module 301 is also used to detect whether there is an architecture reuse control instruction. The architecture reuse control instruction is an instruction used to perform architecture reuse operations on any technical architecture.
[0155] The determination module 302 is also used to determine the reuse type of the architecture to be reused when an architecture reuse control instruction is detected. The reuse type includes the inbound reuse type or the community reuse type. The inbound reuse type is to select and reuse the corresponding type of technical architecture from the preset architecture repository. The community reuse type is to select and reuse the corresponding type of technical architecture from the preset asset community.
[0156] The determination module 302 is also used to determine the target reuse architecture corresponding to the architecture reuse control instruction based on the reuse type, as the architecture to be reused.
[0157] Further optional, such as Figure 4 As shown, the device also includes a generation module 306 and a verification module 307, wherein:
[0158] The generation module 306 is used to determine the target reuse architecture corresponding to the architecture reuse control instruction based on the reuse type by the module 302, and then, according to the determined microservice control requirements, generate a target reuse project that matches the architecture to be reused, based on the architecture to be reused and the reuse architecture parameters corresponding to the architecture to be reused.
[0159] The verification module 307 is used to perform reuse parameter verification operations on the target reuse project according to the architecture reuse control instructions, and obtain the parameter verification results corresponding to the target reuse project.
[0160] The update module 305 is also used to update the target reuse project according to the pre-adjustment result when the parameter verification result indicates that the reuse architecture parameters of the target reuse project do not match the pre-adjustment result for the reuse architecture parameters in the architecture reuse control instruction. The pre-adjustment result is the expected result after the architecture reuse operation is performed on the architecture to be reused through the architecture reuse control instruction.
[0161] It is evident that implementation is as follows Figure 4 The described microservice-based visual architecture definition and control device can automatically determine the reuse type of the architecture to be reused based on the detected architecture reuse control instructions, thereby reducing the reuse difficulty of performing architecture reuse operations on the architecture to be reused and improving reuse efficiency. It can also intelligently verify the target reuse project after generating the target reuse project, and then intelligently update the target reuse project that does not match the pre-adjustment results, thereby improving the reuse accuracy and reliability of the final target reuse project.
[0162] Example 4
[0163] Please see Figure 5 , Figure 5 This is a schematic diagram of another visual architecture definition and management device based on microservice architecture disclosed in an embodiment of the present invention. Figure 5As shown, this visual architecture definition and management device based on microservice architecture may include:
[0164] Memory 401 storing executable program code;
[0165] Processor 402 coupled to memory 401;
[0166] The processor 402 calls the executable program code stored in the memory 401 to execute the steps in the visual architecture definition and management method based on microservice architecture described in Embodiment 1 or Embodiment 2 of the present invention.
[0167] Example 5
[0168] This invention discloses a computer storage medium storing computer instructions. When these computer instructions are invoked, they are used to execute the steps in the visual architecture definition and management method based on microservice architecture described in Embodiment 1 or Embodiment 2 of this invention.
[0169] Example 6
[0170] This invention discloses a computer program product, which includes a non-transitory computer storage medium storing a computer program, and the computer program is operable to cause a computer to perform the steps in the visual architecture definition and control method based on microservice architecture described in Embodiment 1 or Embodiment 2.
[0171] The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.
[0172] Through the detailed description of the above embodiments, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer storage medium, including read-only memory (ROM), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), one-time programmable read-only memory (OTPROM), electrically-erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, disk storage, magnetic tape storage, or any other computer-readable medium that can be used to carry or store data.
[0173] Finally, it should be noted that the visual architecture definition and management method and apparatus based on microservice architecture disclosed in the embodiments of the present invention are merely preferred embodiments of the present invention and are only used to illustrate the technical solutions of the present invention, not to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A visual architecture definition and control method based on microservice architecture, characterized in that, The method includes: Detect the presence of architecture control instructions, which are instructions triggered by the target user to perform architecture definition control operations on a preset editable microservice architecture; When the architecture control instruction is detected, the target microservice corresponding to the architecture control instruction, the architecture to be controlled corresponding to the target microservice, and the architecture control type for the architecture to be controlled are determined. The architecture control type includes a first-level control type or a non-first-level control type. The first-level control type is a control type that requires parameter configuration operations to be performed on the architecture parameters of the architecture to be controlled. The architecture to be controlled includes several layered architectures, and each layered architecture includes architecture parameters corresponding to that layered architecture. When the architecture management type of the architecture to be managed is determined to be the first-level management type, the architecture management requirements for the architecture to be managed are obtained, and the parameter configuration operation is performed on the architecture parameters of the architecture to be managed according to the architecture management requirements to obtain the parameter configuration result corresponding to the architecture to be managed. The parameter configuration result includes the updated architecture parameters after the parameter configuration operation is performed, and the parameter configuration result is displayed to the target user through the visualization module corresponding to the architecture to be managed. When it is determined that the architecture control type of the architecture to be controlled is the non-level 1 control type, the method further includes: Determine the parent microservice of the target microservice, wherein the parent microservice of the target microservice is the microservice that corresponds to the highest service level of the target microservice in the preset service hierarchy; Detect the architecture configuration status corresponding to the parent microservice. The architecture configuration status includes a first-level configuration status or a non-first-level configuration status, which indicates that the parent architecture corresponding to the parent microservice has completed the architecture configuration. When the architecture configuration status corresponding to the parent microservice is detected to be non-first-level configuration status, the pre-determined standard architecture corresponding to the parent microservice is determined as the parent architecture corresponding to the parent microservice to update the parent architecture. The parent architecture is used to display to the target user through the visualization module corresponding to the architecture to be managed.
2. The method for visual architecture definition and management based on microservice architecture according to claim 1, characterized in that, Each of the hierarchical architectures also includes an editable component corresponding to the hierarchical architecture, and each editable component includes an attribution technical asset matching the editable component; The step of performing the parameter configuration operation on the architecture parameters of the architecture to be managed according to the architecture management requirements, and obtaining the parameter configuration result corresponding to the architecture to be managed, includes: Among all the editable components, a target editing component that matches the architecture control requirements is identified, and among all the attribution technical assets corresponding to the target editing component, a target editing technical asset that matches the architecture control requirements is identified; Based on the component identifier of the target editing component and the asset identifier of the target editing technology asset, the parameter configuration operation is performed on the architecture parameters of the architecture to be managed to obtain the parameter configuration result corresponding to the architecture to be managed.
3. The method for visual architecture definition and control based on microservice architecture according to claim 2, characterized in that, The step of performing the parameter configuration operation on the architecture parameters of the architecture to be managed based on the component identifier of the target editing component and the asset identifier of the target editing technology asset, to obtain the parameter configuration result corresponding to the architecture to be managed, includes: The target hierarchical architecture to which the target editing component belongs is determined based on the component identifier of the target editing component; Based on the architecture management requirements, determine the hierarchical architecture to be managed for the target editing component; Determine whether the target layered architecture is consistent with the layered architecture to be managed. If it is determined that the target layered architecture is consistent with the layered architecture to be managed, perform the parameter configuration operation on the architecture parameters of the architecture to be managed according to the architecture management requirements based on the asset identifier of the target editing technology asset, and obtain the parameter configuration result corresponding to the architecture to be managed.
4. The method for visual architecture definition and control based on microservice architecture according to claim 3, characterized in that, When it is determined that the target layered architecture is inconsistent with the layered architecture to be managed, the method further includes: Generate a disable flag to indicate that the target hierarchical architecture is inconsistent with the hierarchical architecture to be managed; The system prompts the target user that the architecture management requirement is unenforceable based on the disabled flag, and obtains the adjustment instructions from the target user regarding the disabled flag, so as to update the architecture management instructions corresponding to the architecture management requirement based on the adjustment instructions.
5. The method for visual architecture definition and control based on microservice architecture according to claim 3 or 4, characterized in that, The method further includes: Based on the parameter configuration results, the architecture to be managed is updated to a reusable architecture with completed parameter configuration; Detect the presence of architecture reuse control instructions, which are instructions used to perform architecture reuse operations on any technical architecture; When the architecture reuse control instruction is detected, the reuse type of the architecture to be reused is determined. The reuse type includes the database reuse type or the community reuse type. The database reuse type is the selection and reuse of the corresponding type of technical architecture from a preset architecture repository. The community reuse type is the selection and reuse of the corresponding type of technical architecture from a preset asset community. Based on the reuse type, a target reuse architecture corresponding to the architecture reuse control instruction is determined as the architecture to be reused.
6. The method for visual architecture definition and control based on microservice architecture according to claim 5, characterized in that, After determining the target reuse architecture corresponding to the architecture reuse control instruction based on the reuse type, as the architecture to be reused, the method further includes: For the architecture to be reused and the reuse architecture parameters corresponding to the architecture to be reused, generate a target reuse project that matches the architecture to be reused according to the determined microservice management requirements; According to the architecture reuse control instruction, a reuse parameter verification operation is performed on the target reuse project to obtain the parameter verification result corresponding to the target reuse project; When the parameter verification result indicates that the reuse architecture parameters of the target reuse project do not match the preliminary adjustment result for the reuse architecture parameters in the architecture reuse control instruction, the target reuse project is updated according to the preliminary adjustment result, which is the expected result after performing the architecture reuse operation on the architecture to be reused through the architecture reuse control instruction.
7. A visual architecture definition and control device based on microservice architecture, characterized in that, The apparatus is used to execute the visual architecture definition and management method based on microservice architecture as described in any one of claims 1-6, and the apparatus comprises: The detection module is used to detect whether there are architecture control instructions. The architecture control instructions are instructions triggered by the target user to perform architecture definition control operations on a preset editable microservice architecture. The determination module is used to determine the target microservice corresponding to the architecture management instruction, the architecture to be managed corresponding to the target microservice, and the architecture management type for the architecture to be managed when the detection module detects the existence of the architecture management instruction. The architecture management type includes a first-level management type or a non-first-level management type. The first-level management type is a management type that requires parameter configuration operations to be performed on the architecture parameters of the architecture to be managed. The architecture to be managed includes several layered architectures, and each layered architecture includes architecture parameters corresponding to that layered architecture. The acquisition module is used to acquire the architecture control requirements for the architecture to be controlled when it is determined that the architecture control type of the architecture to be controlled is the first-level control type. The parameter configuration module is used to perform the parameter configuration operation on the architecture parameters of the architecture to be managed according to the architecture management requirements, and obtain the parameter configuration result corresponding to the architecture to be managed. The parameter configuration result includes the updated architecture parameters after performing the parameter configuration operation. The parameter configuration result is displayed to the target user through the visualization module corresponding to the architecture to be managed.
8. A visual architecture definition and control device based on microservice architecture, characterized in that, The device includes: Memory containing executable program code; A processor coupled to the memory; The processor calls the executable program code stored in the memory to execute the visual architecture definition and management method based on microservice architecture as described in any one of claims 1-6.
9. A computer storage medium, characterized in that, The computer storage medium stores computer instructions, which, when invoked, are used to execute the visual architecture definition and control method based on microservice architecture as described in any one of claims 1-6.