CN114615128B - Service management method and system, computer storage medium and electronic equipment - Google Patents

Service management method and system, computer storage medium and electronic equipment Download PDF

Info

Publication number
CN114615128B
CN114615128B CN202210220848.XA CN202210220848A CN114615128B CN 114615128 B CN114615128 B CN 114615128B CN 202210220848 A CN202210220848 A CN 202210220848A CN 114615128 B CN114615128 B CN 114615128B
Authority
CN
China
Prior art keywords
service
node
demand
description document
target service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202210220848.XA
Other languages
Chinese (zh)
Other versions
CN114615128A (en
Inventor
刘潋
王�琦
吕景俊
黄竺
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Netease Hangzhou Network Co Ltd
Original Assignee
Netease Hangzhou Network Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Netease Hangzhou Network Co Ltd filed Critical Netease Hangzhou Network Co Ltd
Priority to CN202210220848.XA priority Critical patent/CN114615128B/en
Publication of CN114615128A publication Critical patent/CN114615128A/en
Application granted granted Critical
Publication of CN114615128B publication Critical patent/CN114615128B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles

Abstract

The present disclosure relates to the field of computer technologies, and in particular, to a service management method and system, a storage medium, and an electronic device. The method comprises the following steps: determining a target service node corresponding to the current service and node description information of the target service node, wherein the target service node is a functional node with independent processing capability; acquiring an execution logic relation between target service nodes, and generating a demand description document corresponding to the current service by using node description information of each target service node and the execution logic relation between the service nodes according to a preset rule; and sending the demand description document to a service discovery and management center so that the service discovery and management center can automatically operate, maintain and manage the current service according to the demand description document. In the method, the target service node only needs to declare the node description information, and then a demand description document can be generated according to the node description information and the execution logic relationship, so that unified service remediation management and service automatic operation and maintenance management can be realized according to the demand description document.

Description

Service management method and system, computer storage medium and electronic equipment
Technical Field
The present disclosure relates to the field of computer technology, and more particularly, to a service management method, a service management system, a computer storage medium, and an electronic device.
Background
With the development of background technology, a large number of key behaviors overlap in the middle service of the actual production environment, but the service demands of different processing flows are arranged. In order to cope with the continuously evolving demand branches, the background service architecture transits from a single service architecture, a Service Oriented Architecture (SOA) to a micro service architecture, the service division is more and more refined, however, the development of the service cannot exceed the traditional development modes of demand, design architecture, division of the service, iterative development and test deployment.
However, in the conventional development mode, each service requirement needs to be tested from zero to completeness, more and more service instances bring heavy operation and maintenance pressure, service handover is difficult, unified integration and management are difficult, for large-scale complex application, not only is heavy, but also the whole application needs to be deployed when the service is upgraded or modified, the development efficiency is low, and automatic discovery and operation and maintenance management of the service cannot be realized.
It should be noted that the information of the present invention in the above background section is only for enhancing understanding of the background of the present disclosure, and thus may include information that does not form the prior art that is already known to those of ordinary skill in the art.
Disclosure of Invention
The present disclosure aims to provide a service management method and system, a computer storage medium, and an electronic device, so as to achieve unified service remediation management at least to a certain extent, and improve service development, operation, and operation and maintenance efficiency.
Other features and advantages of the present disclosure will be apparent from the following detailed description, or may be learned in part by the practice of the disclosure.
According to one aspect of the present disclosure, there is provided a service management method applied to a service generation module in a service management system, the service management system further including a service discovery and management center, the method including: determining a target service node corresponding to a current service and node description information of the target service node, wherein the target service node is a functional node with independent processing capability; acquiring an execution logic relation between the target service nodes, and generating a demand description document corresponding to the current service according to the node description information of each target service node and the execution logic relation between the service nodes according to a preset rule; and sending the requirement description document to the service discovery and management center so that the service discovery and management center can automatically operate and maintain the current service according to the requirement description document.
In an exemplary embodiment of the present disclosure, before the determining the node description information of the target service node and the target service node corresponding to the current service, the method further includes: carrying out fine granularity division on the supported services to obtain functional nodes with independent processing capacity; according to the functional nodes and the corresponding node description information, a node resource library is established; the node description information at least comprises configuration item information, operation and maintenance interface information, service logic information and node function description information of the functional node.
In an exemplary embodiment of the present disclosure, the obtaining an execution logic relationship between the target service nodes, and generating, according to a preset rule, a requirement description document corresponding to the current service from node description information of each target service node and the execution logic relationship between the service nodes, further includes: and registering the current service in the service discovery and management center according to the requirement description document to acquire the configuration capability and the operation and maintenance capability of the target service node corresponding to the current service.
In an exemplary embodiment of the present disclosure, the sending the requirement description document to the service discovery and management center, so that the service discovery and management center performs automatic operation and maintenance management on the current service according to the requirement description document, includes: and generating a configuration operation and maintenance component corresponding to the current service according to the requirement description document so as to carry out operation and maintenance management on the current service based on the configuration operation and maintenance component.
In an exemplary embodiment of the present disclosure, the requirement description document includes at least a configuration item description document and an operation and maintenance interface description document, and the generating a configuration operation and maintenance component corresponding to the current service according to the requirement description document includes: generating a configuration component according to the configuration item description document so as to realize configuration management of the current service; and generating an operation and maintenance component according to the operation and maintenance interface description document so as to realize operation and maintenance management of the current service.
In an exemplary embodiment of the present disclosure, the method further comprises: acquiring a demand description document of a current service according to a service request aiming at the current service; and according to the requirement description document, sequentially loading target service nodes for running the current service, and generating an actual running code corresponding to the current service, so as to be used as request response information of the service request to be fed back to a service requester.
In an exemplary embodiment of the present disclosure, the obtaining an execution logic relationship between the target service nodes, and generating, according to a preset rule, a requirement description document corresponding to the current service from node description information of each target service node and the execution logic relationship between the service nodes, includes: generating a demand creation form comprising configurable items according to the target service node; responding to the operation that a user sets a configurable item in the demand creation form aiming at the current service, creating the form according to the configured demand, and determining an execution logic relationship between the target service nodes; and according to the execution logic relationship, carrying out aggregation processing on the node description information of each target service node, and generating the requirement description document of the current service.
In an exemplary embodiment of the disclosure, the responding to the user setting a configurable item operation in the requirement creation form for the current service, creating a form according to the configured requirement, and determining an execution logic relationship between the target service nodes includes: responding to the demand parameter configuration, the dependency relationship configuration and the execution strategy configuration of the user on the target service nodes in the demand creation form, and determining the execution logic relationship among the target service nodes by combining the demand parameter configuration, the dependency relationship configuration, the execution strategy configuration and the node description information of the target service nodes.
In an exemplary embodiment of the disclosure, the generating a demand creation form including a configurable item according to the target service node includes: determining the target service node from a node resource library according to service node selection operation of a user; and acquiring the configurable items of the target service nodes, aggregating each target service node and the corresponding configurable items, and generating the demand creation form comprising the configurable items.
In an exemplary embodiment of the present disclosure, the determining the target service node from the node resource library according to a service node selection operation of the user further includes: responding to reconfiguration operation of a user on the service nodes in the node resource library, and generating a target service node meeting the functional requirement of the current service; and/or responding to the service node creation operation of the user, generating a new node meeting the functional requirement and storing the new node into the node resource library.
In an exemplary embodiment of the present disclosure, in response to a service node creation operation of a user, generating and saving a new node satisfying the function requirement to the node resource library, including: responding to the service node creation operation of a user, and generating the new node; generating a node description template of the new node according to a preset service instance configuration rule; generating node description information of the new node on the node description template according to a preset node description rule and the creation information of the new node; and storing the new node and the corresponding node description information to the node resource library.
According to one aspect of the present disclosure, there is provided a service management system including: the service generation module is used for determining a target service node corresponding to the current service and node description information of the target service node, wherein the target service node is a functional node with independent processing capability; acquiring an execution logic relation between the target service nodes, generating a demand description document corresponding to the current service according to the node description information of each target service node and the execution logic relation between the service nodes according to a preset rule, and sending the demand description document to a service discovery and management center; and the service discovery and management center is used for automatically operating and maintaining the current service according to the requirement description document.
In one exemplary embodiment of the present disclosure, the service generation module includes: the service creation unit is used for determining a target service node corresponding to the current service and node description information of the target service node; the demand description document generation unit is used for acquiring the execution logic relation between the target service nodes, generating a demand description document corresponding to the current service according to the node description information of each target service node and the execution logic relation between the service nodes according to a preset rule, and sending the demand description document to the service discovery and management center.
In one exemplary embodiment of the present disclosure, the service discovery and management center includes: and the demand registration module is used for registering the current service according to the demand description document so as to acquire the configuration capability and the operation and maintenance capability of the target service node corresponding to the current service.
In an exemplary embodiment of the present disclosure, the requirement description document includes at least a configuration item description document and an operation and maintenance interface description document, and the service discovery and management center includes: the configuration management module is used for generating a configuration component according to the configuration item description document so as to realize configuration management of the current service; the operation and maintenance management module is used for generating an operation and maintenance component according to the operation and maintenance interface description document so as to realize operation and maintenance management of the current service; the service operation module is used for acquiring a demand description document of the current service according to a service request aiming at the current service, sequentially loading and operating a target service node of the current service according to the demand description document, and generating an actual operation code corresponding to the current service so as to be used as request response information of the service request to be fed back to a service requester.
According to an aspect of the present disclosure, there is provided a computer storage medium having stored thereon a computer program which, when executed by a processor, implements the service management method of any one of the above.
According to one aspect of the present disclosure, there is provided an electronic device including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform any of the service management methods described above via execution of the executable instructions.
According to the service management method in the exemplary embodiment of the disclosure, the target service node corresponding to the current service and the node description information of the target service node are determined, the execution logic relation between the target service nodes is obtained, the node description information of each target service node and the execution logic between the service nodes are generated according to the preset rule, a demand description document corresponding to the current service is generated and sent to a service discovery and management center, and automatic operation and maintenance management is performed on the current service according to the demand description document. On the one hand, various traditional services or newly created services can be divided and integrated rapidly in a functional node mode, unified service remediation management is achieved, meanwhile, a large amount of development, test and deployment labor cost required by traditional service reconstruction can be avoided through multiplexing the functional nodes with independent processing capacity, and service development, operation and maintenance efficiency is improved. On the other hand, because each service is managed in a mode of a functional node, the services are highly free and decoupled, and can be expanded and upgraded according to actual service demands without affecting other services or other service nodes in the service; on the other hand, according to the node description information stated by each target service node and the acquired execution logic relationship, a demand description document of the current service can be generated according to preset rules, and further, the current service can be automatically operated and maintained according to the demand description document, so that the automatic discovery and operation and maintenance of the service are realized, and the service management efficiency is high.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The above, as well as additional purposes, features, and advantages of exemplary embodiments of the present disclosure will become readily apparent from the following detailed description when read in conjunction with the accompanying drawings. Several embodiments of the present disclosure are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings, in which:
FIG. 1 illustrates a flowchart of a service management method according to an exemplary embodiment of the present disclosure;
FIG. 2 illustrates a service node creation flow diagram according to an exemplary embodiment of the present disclosure;
FIG. 3 illustrates a schematic diagram of a target service node required for a game initiation sharing portion according to an exemplary embodiment of the present disclosure;
FIG. 4 illustrates a flowchart of determining an executive logic relationship between target service nodes in response to a user setting a configurable item operation in a demand creation form for a current service, the form being created according to a configured demand, according to an exemplary embodiment of the present disclosure;
FIG. 5 illustrates a directed acyclic descriptive diagram according to an exemplary embodiment of the present disclosure;
FIG. 6 illustrates a schematic diagram of a target service node and an executive logical relationship between target service nodes required for a social user participation process in accordance with an exemplary embodiment of the present disclosure;
FIG. 7 illustrates a flowchart of service request processing by a service management method according to an exemplary embodiment of the present disclosure;
FIG. 8 illustrates a schematic structure of a service management system according to an exemplary embodiment of the present disclosure;
FIG. 9 illustrates a schematic structure of a service management system according to an exemplary embodiment of the present disclosure;
FIG. 10 illustrates a schematic diagram of a storage medium according to an exemplary embodiment of the present disclosure; and
fig. 11 shows a block diagram of an electronic device according to an exemplary embodiment of the present disclosure.
In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.
Detailed Description
Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar structures, and thus detailed descriptions thereof will be omitted.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the disclosed aspects may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known structures, methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.
The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, or in one or more software-hardened modules, or in different networks and/or processor devices and/or microcontroller devices.
In related art in the field, conventional enterprise-level applications are monolithic application architectures, typically hierarchical structures such as presentation layer/application layer/domain layer/data layer, whereas micro-services are an architecture and organization method for developing software consisting of small stand-alone services communicating through well-defined APIs (Application Programming Interface, application program interfaces). Using a micro-service architecture, applications are built as independent components and each application process is run as a service. Because they are independently running, updates, deployments, and extensions can be made to each service to meet the needs of the application-specific functionality.
However, although the division of services is becoming finer, the "requirements" cannot always be exceeded " "design architecture">"division service">Iterative development->Traditional development mode of "test deployment". The traditional development mode has a great deal of manpower waste, precious technology development time is lost in similar and different products are required to be in a vast ocean, and team work cannot be effectively precipitated; the large amount of demand development work also brings uncontrollable quality risks, each demand needs to be tested from zero to completeness, and the quality code after full verification cannot be effectively inherited; and more demand examples bring heavy subsequent operation and maintenance pressure, and the handover is difficult and the unified integration and management are difficult. Meanwhile, with the development of enterprises, for large-scale complex applications, the applications become cumbersome: the whole application needs to be deployed all the time when upgrading or modifying a place, and has long compiling time, long regression testing period, reduced development efficiency and the like. That is, the related art has the following drawbacks:
1) The quick and unified integration management of various services cannot be realized;
2) Aiming at old service upgrade, modification or new service establishment, highly-free, decoupled, hot-pluggable and locally-seamless upgrade iterative operation cannot be realized;
3) The service development period is long, the efficiency is low, and the labor cost is high.
Based on this, in an exemplary embodiment of the present disclosure, there is first provided a service management method applied to a service generation module in a service management system further including a service discovery and management center. Referring to fig. 1, the service management method includes the steps of:
step S110: determining a target service node corresponding to the current service and node description information of the target service node, wherein the target service node is a functional node with independent processing capability;
step S120: acquiring an execution logic relation between target service nodes, and generating a demand description document corresponding to the current service by using node description information of each target service node and execution logic between the service nodes according to preset rules;
step S130: and sending the demand description to a service discovery and management center so that the service discovery and management center can automatically operate, maintain and manage the current service according to the demand description document.
According to the service management method in the present exemplary embodiment, by splitting services into functional nodes with independent processing capabilities in a fine-grained manner, and each target service node has corresponding node description information, so as to generate a requirement description document corresponding to a current service according to a preset rule and send the requirement description document to a service discovery and management center, thereby implementing automatic discovery and operation and maintenance management of the current service. The process can divide and rapidly integrate various traditional services or newly created services in a functional node mode, realizes unified service remediation management, can avoid a large amount of development, test and deployment labor cost required by traditional service reconstruction, and improves service development, operation and maintenance efficiency. Because each service is managed in a mode of a functional node, the service nodes are highly free and decoupled, and can be expanded and upgraded according to actual service demands without affecting other services or other service nodes in the service; and according to the node description information declared by each target service node and the acquired execution logic relation, a demand description document of the current service can be generated according to preset rules, and further, the current service can be automatically operated and maintained according to the demand description document, so that the automatic discovery and operation and maintenance of the service are realized, and the service management efficiency is high.
The service management method in the exemplary embodiment of the present disclosure is further described below with reference to fig. 1.
In step S110, a target service node corresponding to the current service and node description information of the target service node are determined, where the target service node is a functional node with independent processing capability.
In an exemplary embodiment of the present disclosure, the target service node is a functional node having an independent processing capability, and all services supported by the service management system may be finely divided into service nodes, and the service nodes and corresponding node description information may be stored in a node resource library. Alternatively, all services supported by the service management system may be finely divided into service nodes that are not separately divided; alternatively, according to the actual service management requirement, the non-redispersible service nodes may be combined into a combined service node, where the combined service node may be used to process a certain service function, and accordingly, the combined service node and the corresponding node description information may be stored in the node resource library.
In an exemplary embodiment of the present disclosure, the node description information includes at least configuration item information, operation and maintenance interface information, service logic information, and node function description information of the functional node. Wherein the configuration item information is relevant configuration information required by the service node.
In an exemplary embodiment of the present disclosure, a node repository may be established prior to determining a target service node and node description information of the target service node required for a current service. Firstly, carrying out fine granularity division on supported services to obtain functional nodes with independent processing capacity, and then establishing a node resource library according to the functional nodes and corresponding node description information.
As shown in fig. 2, which illustrates a service node creation flow diagram according to an exemplary embodiment of the present disclosure, as shown in fig. 2, the process includes the steps of:
in step S210, a service node is created.
In this exemplary embodiment, a basic node development template may be obtained and inherited, and coverage is implemented according to the attribute, function, and the like of the basic node development template, so as to develop service logic of a service node, fill node function description information, set configuration item information, set operation and maintenance interface information, and the like, so as to generate a complete service node. Through the present exemplary embodiment, service nodes can be created according to actual service requirements, and both conventional service and new access service can be performed by creating service nodes to perform fine granularity division on the service, so that service management is converted into node management, thereby facilitating unified management of various services without differentiation.
In step S220, a node description template of the service node is generated according to a preset service instance configuration rule.
In the present exemplary embodiment, a node description template of a service node may be generated according to a preset service instance configuration rule. According to the service instance configuration rule with description capability, the service nodes are provided with normalized node description templates so as to uniformly manage the node description information of various service nodes.
In an exemplary example, before generating the node description template of the service node according to the preset service instance configuration rule, the created basic specifications of the service node may also be checked, including but not limited to heartbeat detection, test Case running, and configuration item specification detection, etc., to ensure validity and executable performance of the service node.
In step S230, node description information of the service node is generated on the node description template according to the preset node description rule and the creation information of the service node.
In this exemplary embodiment, the node description information of the service node may be generated on the node description template according to a preset node description rule in combination with the creation information of the service node (such as service logic of the service node, node function description information, configuration item information, operation and maintenance interface information, etc.). The node description information can be realized through XPDL flow definition specifications, and of course, the node description information can also be realized in different modes according to actual service development requirements, and the comparison of the disclosure is not particularly limited.
In step S240, the service node and the corresponding node description information are saved to the node repository.
In the present exemplary embodiment, service nodes and corresponding node description information may be saved in a node resource library, and by enabling the service nodes in the node resource library of the present exemplary embodiment, a corresponding service function may be implemented, so that services may be decoupled into service nodes, high-degree-of-freedom management may be implemented, and service development efficiency may also be improved.
For example, a service instance for game sharing in a game includes two main line processes:
in-game player- & gt game client UI (interface) click sharing- & gt initiating sharing of H5 pages to social platformCollect 10 praise, get a chance of exchange ending in the game +.>Collect 15 praise->Obtaining a lottery opportunity in the game;
social platform userSocial platform 1/social platform 2/social platform 3 environments open sharing links +.>Authorized login of the corresponding platform->View player nurturing baby data +.>Praise friends->If binding game role->Additional 10 praise others opportunities->One-key start leading to game +.>Game player flow.
Therefore, the service requirement at least needs to deliver 14 server HTTP APIs, and at least includes peripheral requirements such as online H5 link management, health monitoring, data statistics reporting, peak pressure measurement, etc.
Fig. 3 shows a schematic diagram of target service nodes required by a game initiation sharing part according to an exemplary embodiment of the present disclosure, as shown in fig. 3, where the required target service nodes include a game sharing service node, a game rewards settlement service node, and a game data query service node, and each target service node has corresponding node description information, including at least configuration item information, operation and maintenance interface information, service logic information, and node function description information, and by determining and enabling the above target service nodes, service functions such as game sharing, game H5 data synchronization, game rewards settlement, and pull can be completed.
In an exemplary embodiment of the present disclosure, a user may select and enable a service node from a node repository to determine a target service node and node description information of the target service node corresponding to a current service. When the user starts the target service node corresponding to the current service, the user can register the current service in the service discovery and management center according to the requirement description document, namely, the user registers the target service node and the node description information corresponding to the current service in the service discovery and management center by taking the service as a registration unit, so as to acquire the configuration capability and the operation and maintenance capability of the target service node corresponding to the current service.
In some possible embodiments, the target service node may register configuration items it supports and the required rights of operators for each configuration with the configuration center, and declare operation and interface description information, so as to provide unified configuration capability and operation and maintenance capability for the target service node according to the registration information.
If there is a functional node newly added to the node resource library, service registration and access can be performed in the same manner, so as to realize rapid access and management of the service node.
In an exemplary embodiment, the node description information of each target service node and the execution logic relationship between the service nodes may be generated according to a preset rule, so as to generate a requirement description document corresponding to the current service. Firstly, generating a demand creation form comprising configurable items according to a target service node; secondly, setting a configurable item operation in the demand creation form aiming at the current service by a user, creating the form according to the configured demand, and determining an execution logic relationship between target service nodes; and finally, according to the execution logic relationship, carrying out aggregation processing on the node description information of each target service node, and generating a current service requirement description document.
According to the method and the device for automatically managing the operation and maintenance of the current service, after the execution logic relationship between the target service node and the target service node of the current service is determined, the node description information and the execution logic relationship can be generated into the requirement description document of the current service according to the preset rule because the target service node has the corresponding node description information, so that the relevant configuration and operation and maintenance management items corresponding to the current service can be obtained according to the requirement description document, and the automatic operation and maintenance management of the current service is realized. Optionally, the requirement description document and the corresponding current service may be stored correspondingly, for example, the current service identifier and the requirement description document are stored correspondingly, so that the corresponding requirement description document may be obtained according to the current service identifier, and the current service may be managed according to the requirement description document.
In some possible embodiments, the target service nodes may be determined from the node resource library according to the service node selection operation of the user, the configurable items of each target service node are obtained and aggregated, and the requirement creation form including the configurable items is generated. The meaning, the value range, the default value and other information of the form field item in the requirement creation form in the definition of the node description area can be set according to the actual service development requirement, and the disclosure does not limit the meaning in particular.
In some possible embodiments, after performing the service node selection operation, the user may request to initialize the selected target service node, so that configurable items of each target service node may be determined and aggregated to generate a demand creation form including the configurable items. By initializing each target service node, part of configuration item information of the target service node, such as dependency relationship among the target service nodes, and the like, which cannot be determined from the node description information, can be determined from the node description information of the target service node, and then the part of configuration information is used as a configurable item of the target service node.
Alternatively, the requirement creation form including the configurable item may be edited by a developer; optionally, the requirement creation form including the configurable item may also automatically configure the form according to a preset rule according to a service development requirement, which is not particularly limited in the present disclosure.
In an exemplary embodiment, if an existing service node in the node resource library cannot meet the functional requirement of the current service, a target service node meeting the functional requirement can be generated in response to a reconfiguration operation of a user on the service node in the node resource library; and/or responding to the service node creation operation of the user, generating a new node meeting the function requirement and storing the new node into a node resource library. For example, each service node may open a private function definition at some step to conduct the critical behavior of the custom node. The step of creating the new node may refer to step S210 to step S240, which are not described herein.
In an exemplary embodiment, the aggregation processing may be performed according to the target service node, so as to obtain a combined node that may satisfy the functions required by the current service. Accordingly, the demand description document of the current service can be generated according to the node description information of each target service node and the execution logic relationship between the target service nodes.
In the present exemplary embodiment, the demand description document of the current service includes at least a configuration item description document and an operation and maintenance interface description document corresponding to the current service generated according to the execution logical relationship between the node description information and the target service node. Wherein the configuration item description document can comprise a directed acyclic DAG description graph describing the node description rules of the target service nodes for executing logical relations and based on XPDL specifications and a requirement configuration item description document based on the service instance configuration rules with self-description capability; the operation and maintenance interface description document is generated based on a preset instance interface definition description rule.
According to the method and the device, through node description rules based on XPDL specifications, service instance configuration rules with self-description capability and instance interface definition description rules which are intensively managed, a demand description document with unified protocol specifications of the current service can be generated, whether for the traditional architecture service requiring service upgrade access or the newly developed service, the centralized integrated management of various services is realized through the unified protocol specifications without considering an original architecture, and the centralized integrated management of various services including but not limited to unified storage, scheduling, addition, deletion, modification and the like of various configurations, attributes and data segments of integrated services is realized, namely, the time, labor and quality risk cost can be reduced in terms of service integration, optimization, standardization and unified operation and maintenance management.
FIG. 4 is a flowchart illustrating a process for determining an execution logical relationship between target service nodes according to a configured demand creation form in response to a user setting a configurable item operation in the demand creation form for a current service according to an exemplary embodiment of the present disclosure, as shown in FIG. 4, the process including:
in step S410, the demand parameter configuration, the dependency configuration, and the execution policy configuration for the target service node in the demand creation form are responded to by the user.
In the present exemplary embodiment, the demand parameter configuration is a parameter configuration that is determined according to a target service node combination and is required to implement the current service, the dependency relationship configuration is to configure the execution timing of the target service node, the execution policy configuration is a rule policy configuration of the target service node in the execution process, for example, after the target service node 1 is executed, whether the target service node 2 or the target service node 3 is executed next is determined by the policy, and so on.
In an exemplary embodiment, the target service nodes, the dependencies among the target service nodes and the execution policies may be described by DAG (Directed acyclic graph, directed acyclic), as shown in fig. 5, a directed acyclic descriptive diagram according to an exemplary embodiment of the disclosure, as shown in fig. 5, by which the respective target service nodes (act-a, act-B, and act-C) may be assembled into a service by the dependencies and the execution policies (e.g., decision-a, success, or failure).
Continuing to refer to the service instance for game sharing in a certain game, as shown in fig. 6, aiming at the execution logic relationship between the target service node and the target service node required by the participation process of the social user, the service instance at least comprises a login authorization service node of the social platform 1, a login authorization service node of the social platform 2, a login authorization service node of the social platform 3, a game sharing data service node, a game role query service node, a social assistance service node, a game role data social binding service node and a one-key start deep link parameter service node, and the execution logic relationship between each target service node is shown by an arrow in fig. 6, and each target service node has corresponding node description information.
According to the present exemplary embodiment, according to the present service, a user only needs to perform requirement parameter configuration, dependency relationship configuration and execution policy configuration on a target service node in a requirement creation table, a complete flow of one service may be compared with "behavior", and "behavior" is formed by combining a plurality of single "actions" according to different "time sequences" and "execution policies.
In an exemplary embodiment, if a new target service node needs to be introduced, the new target service node may be issued to the requirement creation form according to node description information of the new target service node, so that a user may set a dependency relationship and an execution policy corresponding to the target service node. Through the embodiment, the service node description information can be issued to the demand creation form according to the service node description information, so that a user can configure the configurable items related to the service node, the introduction efficiency of a new service node is improved, and other service nodes are not affected.
In addition, in the exemplary embodiment of the present disclosure, a set of definition rules based on the DAG graph assembly program flow may be implemented, so that Nocode (code-free) expression of "behavior", "timing" and "execution policy" may be implemented, and the defined XPDL and DAG may be encapsulated and protocol details may be masked, so as to improve development efficiency.
In step S420, the execution logic relationship between the target service nodes is determined in combination with the demand parameter configuration, the dependency relationship configuration, the execution policy configuration, and the node description information of the target service nodes.
In the present exemplary embodiment, the execution logic relationship between the target service nodes may be determined in combination with the demand parameter configuration, the dependency relationship configuration, the execution policy configuration, and the node description information (such as configuration item information, operation and maintenance interface information, service logic information, and node function description information) of the target service nodes. Based on the above, after the target service node is initialized, the target service node can be linked with other target service nodes according to the execution logic relationship so as to realize the current service.
In step S130, the requirement description document is transmitted to the service discovery and management center, so that the service discovery and management center performs automatic operation and maintenance management on the current service according to the requirement description document.
In the present exemplary embodiment, the current service is managed according to the demand description document, including at least creation, operation, and operation maintenance of the demand service. After the service discovery and management center discovers the current service and the corresponding requirement description document, a configuration operation and maintenance component corresponding to the current service can be generated according to the requirement description document so as to carry out operation and maintenance management on the current service based on the configuration operation and maintenance component.
In an exemplary embodiment, a requirement description document of a current service may be obtained according to a service request for the current service, and a target service node for running the current service is sequentially loaded according to the requirement description document, so as to generate an actual running code corresponding to the current service, so as to be used as request response information of the service request to be fed back to a service requester. Optionally, the requirement description document can be saved in a serialization manner, after the requirement description document is acquired, each target service node and the corresponding configuration item are loaded and operated in sequence through a serialization process so as to generate an actual operation code corresponding to the current service, and the actual operation code is used for responding in real time, processing an actual service request and the like.
Fig. 7 shows a flowchart of service request processing by a service management method according to an exemplary embodiment of the present disclosure, and as shown in fig. 7, the process may include the steps of:
1) Receiving a service request, analyzing the service request through a proxy/gateway, acquiring service instance identification information, and acquiring and packaging a requirement description document corresponding to an instance from an instance configuration center Instance Conf Center according to the service instance identification through an operation Manager run Manager;
2) The instance configuration center Instance Conf Center sends the requirements description document to the run Engine load;
3) After the running Engine run Engine loads the service instance, the target service node is loaded successively according to the execution logic relation (time sequence and rule strategy) of the target service node in the demand description document to obtain an actual running code, and the actual running code is returned to the running Manager run Manager;
4) The running Manager run Manager packages the actual running code into serialized request response data, and presents the serialized request response data to the user in an http response mode, so that a complete service instance response is completed.
According to the method and the device for processing the service response, the required target service nodes can be assembled based on the requirement description information corresponding to the current service, the target service nodes are loaded successively to obtain the actual running code to enter the service response, the method and the device are not limited by the service type, and various service responses can be processed uniformly.
In an exemplary embodiment, the configuration component may be automatically generated according to the configuration item description document in the requirement description document, so as to implement configuration management on the current service, such as automatically loading a configuration page; and/or generating an operation and maintenance component, such as an automatic record and maintenance platform, according to the operation and maintenance interface description document in the description document so as to realize operation and maintenance management of the current service.
In an exemplary embodiment of the present disclosure, a service discovery and management center may introduce a distributed configuration center condul to implement service registration discovery of a service instance, and after a requirement description document of a current service is generated, submit the requirement description document to the distributed configuration center condul of the service discovery and management center, and after an integrated management background in the service discovery and management center discovers the requirement description document of the service instance, automatically load a configuration component according to the requirement item description document, and automatically load a carrier component according to an operation and maintenance interface description document, so as to perform automatic configuration and operation and maintenance management. For example, access, modification authority, health monitoring, data statistics and the like can be controlled according to node description information of each target service node, and the specific content of automatic configuration and operation and maintenance management is not particularly limited in the disclosure.
According to the exemplary embodiment of the present disclosure, according to the target service node selected by the current service, only the node description information such as the required configuration and the provided operation and maintenance interface is required to be declared, so that the requirement description document of the current service can be obtained by assembling the target service node and transmitted to the service discovery and management center, after the service discovery and management center discovers the service instance, the configuration component and the operation and maintenance component with the corresponding functions of the current service can be automatically loaded according to the requirement item description document, that is, the configuration component and the operation and maintenance component are automatically loaded according to the operation and maintenance interface description document, so as to implement configuration management and operation and maintenance management of the current service. The method realizes the data collaboration with high degree of freedom, various service examples can be found by an integrated management background (data center platform), and the operation and management operations such as automatic integrated data statistics, configuration operation and maintenance, health monitoring and the like are realized, so that the content originally processed by the technology in the example development and operation and maintenance period is lowered to each role participated in by the project, and development manpower is greatly liberated.
In an exemplary embodiment of the present disclosure, a service management system is also provided. Referring to fig. 8, the service management system 800 may include a service generation module 810 and a service discovery and management center 820. Specifically:
A service generating module 810, configured to determine a target service node corresponding to a current service and node description information of the target service node, where the target service node is a functional node with independent processing capability; acquiring an execution logic relation between target service nodes, generating a demand description document corresponding to the current service according to the node description information of each target service node and the execution logic relation between the service nodes according to a preset rule, and sending the demand description document to a service discovery and management center;
the service discovery and management center 820 is used for automatically operating and maintaining the current service according to the requirement description document.
In one exemplary embodiment of the present disclosure, the service generation module 810 may include a service creation unit and a requirement description document generation unit. Specifically: the service creation unit is used for determining a target service node corresponding to the current service and node description information of the target service node; the demand description document generation unit is used for acquiring the execution logic relation between the target service nodes, generating a demand description document corresponding to the current service according to the node description information of each target service node and the execution logic relation between the service nodes according to a preset rule, and sending the demand description document to the service discovery and management center.
In an exemplary embodiment of the present disclosure, the service discovery and management center may include a requirement registration module for registering a current service according to a requirement description document to obtain configuration capability and operation capability of a target service node corresponding to the current service.
In an exemplary embodiment of the present disclosure, the requirement description document includes at least a configuration item description document and an operation and maintenance interface description document, and the service discovery and management center may include: the configuration management module is used for generating a configuration component according to the configuration item description document so as to realize configuration management of the current service; the operation and maintenance management module is used for generating an operation and maintenance component according to the operation and maintenance interface description document so as to realize operation and maintenance management of the current service; the service operation module is used for acquiring a demand description document of the current service according to the service request aiming at the current service, sequentially loading target service nodes for operating the current service according to the demand description document, and generating an actual operation code corresponding to the current service to be used as request response information of the service request to be fed back to a service requester.
In one exemplary embodiment of the present disclosure, fig. 9 illustrates an architecture diagram of a service management system according to an exemplary embodiment of the present disclosure, as illustrated in fig. 9, features and functions of the service generation module 810 in fig. 8 may be embodied by the service development module 910, and the service execution module, the configuration management module, and the operation and maintenance management module included in the service discovery and management center 820 may be embodied in the execution engine 920, the configuration center 930, and the operation and maintenance integration background 940.
As shown in fig. 9, the service development module 910 determines a target service node required for the current service and node description information of the target service node, and generates a demand creation form including a configurable item according to the target service node; and the service development module 910 is configured to set a configurable item in a requirement creation form according to the current service, and generate a requirement description document including node description information and a target service node for executing a logical relationship according to the configured requirement creation form. The operation engine 920 is configured to obtain a requirement description document of a current service according to a service request for the current service, sequentially load a target service node for operating the current service according to the requirement description document, and generate an actual operation code corresponding to the current service, so as to be used as request response information of the service request and feed back to a service requester. The operation and maintenance integrated background 940 is used for automatically loading the configuration component according to the configuration item description document so as to realize configuration management of the current service; and the operation and maintenance integration background 940 is further used for automatically loading the operation and maintenance component according to the operation and maintenance interface description document, so as to realize operation and maintenance management of the current service. The operation and maintenance integration background 940 can automatically discover the creation of new service requirements, so that a corresponding management background page is generated by acquiring a corresponding requirement description document, that is, the service requirements can be automatically configured and managed once being created.
Since each functional module of the service management system according to the exemplary embodiment of the present disclosure is the same as that in the inventive embodiment of the service management method described above, a detailed description thereof will be omitted.
It should be noted that although several modules or units of the service management system are mentioned in the above detailed description, this division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
Furthermore, in exemplary embodiments of the present disclosure, a computer storage medium capable of implementing the above-described method is also provided. On which a program product is stored which enables the implementation of the method described above in the present specification. In some possible embodiments, the various aspects of the present disclosure may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the disclosure as described in the "exemplary methods" section of this specification, when the program product is run on the terminal device.
Referring to fig. 10, a program product 1000 for implementing the above-described method according to an exemplary embodiment of the present disclosure is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable medium for storing information
Combinations of the above. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: has a one
An electrical connection of one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
In addition, in an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided. Those skilled in the art will appreciate that the various aspects of the present disclosure may be implemented as a system, method, or program product. Accordingly, various aspects of the disclosure may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.
An electronic device 1100 according to such an embodiment of the present disclosure is described below with reference to fig. 11. The electronic device 1100 shown in fig. 11 is merely an example and should not be construed as limiting the functionality and scope of use of the disclosed embodiments.
As shown in fig. 11, the electronic device 1100 is embodied in the form of a general purpose computing device. Components of electronic device 1100 may include, but are not limited to: the at least one processing unit 1110, the at least one memory unit 1120, a bus 1130 connecting the different system components (including the memory unit 1120 and the processing unit 1110), and a display unit 1140.
Wherein the storage unit stores program code that is executable by the processing unit 1110 such that the processing unit 1110 performs steps according to various exemplary embodiments of the present disclosure described in the above-described "exemplary methods" section of the present specification.
The storage unit 1120 may include a readable medium in the form of a volatile storage unit, such as a Random Access Memory (RAM) 1121 and/or a cache memory 1122, and may further include a Read Only Memory (ROM) 1123.
Storage unit 1120 may also include a program/utility 1124 having a set (at least one) of program modules 1125, such program modules 1125 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
The bus 1130 may be a local bus representing one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a bus using any of a variety of bus architectures.
The electronic device 1100 may also communicate with one or more external devices 1200 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 1100, and/or any devices (e.g., routers, modems, etc.) that enable the electronic device 1100 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 1150. Also, electronic device 1100 can communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 1160. As shown, network adapter 1160 communicates with other modules of electronic device 1100 via bus 1130. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 1100, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.
Furthermore, the above-described figures are only schematic illustrations of processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (16)

1. A service management method, applied to a service generation module in a service management system, the service management system further comprising a service discovery and management center, the method comprising:
according to the service node selection operation of a user, determining a target service node corresponding to the current service and node description information of the target service node from a node resource library, wherein the target service node is a functional node with independent processing capability;
generating a demand creation form comprising configurable items according to the target service nodes, responding to the operation of setting the configurable items in the demand creation form by a user aiming at the current service, creating the form according to the configured demand, and determining an execution logic relationship between the target service nodes; according to a preset rule, generating a demand description document corresponding to the current service by using the node description information of each target service node and the execution logic relation between the service nodes;
And sending the requirement description document to the service discovery and management center so that the service discovery and management center generates a configuration operation and maintenance component corresponding to the current service according to the requirement description document, and carrying out operation and maintenance management on the current service based on the configuration operation and maintenance component.
2. The method of claim 1, wherein prior to said determining the node description information of the target service node and the target service node to which the current service corresponds, the method further comprises:
carrying out fine granularity division on the supported services to obtain functional nodes with independent processing capacity;
according to the functional nodes and the corresponding node description information, a node resource library is established;
the node description information at least comprises configuration item information, operation and maintenance interface information, service logic information and node function description information of the functional node.
3. The method of claim 1, wherein the generating the demand description document corresponding to the current service by the performing logic relationship between the node description information of each of the target service nodes and the service node according to a preset rule further comprises:
And registering the current service in the service discovery and management center according to the requirement description document to acquire the configuration capability and the operation and maintenance capability of the target service node corresponding to the current service.
4. The method of claim 1, wherein the requirement description document includes at least a configuration item description document and an operation and maintenance interface description document, and the generating the configuration operation and maintenance component corresponding to the current service according to the requirement description document includes:
generating a configuration component according to the configuration item description document so as to realize configuration management of the current service;
and generating an operation and maintenance component according to the operation and maintenance interface description document so as to realize operation and maintenance management of the current service.
5. The method according to claim 1, wherein the method further comprises:
acquiring a demand description document of a current service according to a service request aiming at the current service;
and according to the requirement description document, sequentially loading target service nodes for running the current service, and generating an actual running code corresponding to the current service, so as to be used as request response information of the service request to be fed back to a service requester.
6. The method of claim 1, wherein generating the requirement description document corresponding to the current service by associating the node description information of each target service node with the execution logic relationship between the service nodes according to a preset rule, comprises:
and according to the execution logic relationship, carrying out aggregation processing on the node description information of each target service node, and generating the requirement description document of the current service.
7. The method of claim 6, wherein the responding to the user setting a configurable item operation in the demand creation form for the current service, creating a form according to the configured demand, determining an execution logical relationship between the target service nodes, comprises:
responding to the demand parameter configuration, the dependency relationship configuration and the execution strategy configuration of the user on the target service nodes in the demand creation form, and determining the execution logic relationship among the target service nodes by combining the demand parameter configuration, the dependency relationship configuration, the execution strategy configuration and the node description information of the target service nodes.
8. The method of claim 6, wherein generating a demand creation form comprising a configurable item from the target service node comprises:
Determining the target service node from a node resource library according to service node selection operation of a user;
and acquiring the configurable items of the target service nodes, aggregating each target service node and the corresponding configurable items, and generating the demand creation form comprising the configurable items.
9. The method of claim 8, wherein the determining the target serving node from a node resource library according to a serving node selection operation of a user, further comprises:
responding to reconfiguration operation of a user on the service nodes in the node resource library, and generating a target service node meeting the functional requirement of the current service; and/or
And responding to the service node creation operation of the user, generating a new node meeting the functional requirement and storing the new node into the node resource library.
10. The method of claim 9, wherein generating and saving new nodes meeting the functional requirements to the node repository in response to a service node creation operation of a user comprises:
responding to the service node creation operation of a user, and generating the new node;
generating a node description template of the new node according to a preset service instance configuration rule;
Generating node description information of the new node on the node description template according to a preset node description rule and the creation information of the new node;
and storing the new node and the corresponding node description information to the node resource library.
11. A service management system, comprising:
the service generation module is used for determining a target service node corresponding to the current service and node description information of the target service node from a node resource library according to service node selection operation of a user, wherein the target service node is a functional node with independent processing capability; generating a demand creation form comprising configurable items according to the target service nodes, responding to the operation of setting the configurable items in the demand creation form by a user aiming at the current service, creating the form according to the configured demand, and determining an execution logic relationship between the target service nodes; according to a preset rule, generating a demand description document corresponding to the current service by using node description information of each target service node and an execution logic relation between the service nodes, and sending the demand description document to a service discovery and management center;
And the service discovery and management center is used for generating a configuration operation and maintenance component corresponding to the current service according to the requirement description document so as to carry out operation and maintenance management on the current service based on the configuration operation and maintenance component.
12. The system of claim 11, wherein the service generation module comprises:
the service creation unit is used for determining a target service node corresponding to the current service and node description information of the target service node;
a demand description document generation unit, configured to generate a demand creation form including a configurable item according to the target service node, set a configurable item operation in the demand creation form in response to a user for the current service, and determine an execution logic relationship between the target service nodes according to the configured demand creation form; and generating a demand description document corresponding to the current service according to the node description information of each target service node and the execution logic relation between the service nodes according to a preset rule, and sending the demand description document to a service discovery and management center.
13. The system of claim 11, wherein the service discovery and management center comprises:
And the demand registration module is used for registering the current service according to the demand description document so as to acquire the configuration capability and the operation and maintenance capability of the target service node corresponding to the current service.
14. The system of claim 11, wherein the requirement description document includes at least a configuration item description document and an operation and maintenance interface description document, and the service discovery and management center includes:
the configuration management module is used for generating a configuration component according to the configuration item description document so as to realize configuration management of the current service;
the operation and maintenance management module is used for generating an operation and maintenance component according to the operation and maintenance interface description document so as to realize operation and maintenance management of the current service;
the service operation module is used for acquiring a demand description document of the current service according to a service request aiming at the current service, sequentially loading and operating a target service node of the current service according to the demand description document, and generating an actual operation code corresponding to the current service so as to be used as request response information of the service request to be fed back to a service requester.
15. A storage medium having stored thereon a computer program which, when executed by a processor, implements the service management method according to any of claims 1 to 10.
16. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the service management method of any one of claims 1 to 10 via execution of the executable instructions.
CN202210220848.XA 2022-03-08 2022-03-08 Service management method and system, computer storage medium and electronic equipment Active CN114615128B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210220848.XA CN114615128B (en) 2022-03-08 2022-03-08 Service management method and system, computer storage medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210220848.XA CN114615128B (en) 2022-03-08 2022-03-08 Service management method and system, computer storage medium and electronic equipment

Publications (2)

Publication Number Publication Date
CN114615128A CN114615128A (en) 2022-06-10
CN114615128B true CN114615128B (en) 2024-02-23

Family

ID=81861794

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210220848.XA Active CN114615128B (en) 2022-03-08 2022-03-08 Service management method and system, computer storage medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN114615128B (en)

Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7493624B1 (en) * 2003-12-30 2009-02-17 Sap Ag Management architecture and method employed within a clustered node configuration
CN103546327A (en) * 2013-11-05 2014-01-29 重庆邮电大学 Method for building hybrid-topology network management model based on JXTA
WO2015000362A1 (en) * 2013-07-05 2015-01-08 华为技术有限公司 Service node configuration method, service node pond register and system
CN106921532A (en) * 2015-12-25 2017-07-04 中国电信股份有限公司 A kind of performance management method, the device of business catenary system
CN107844399A (en) * 2017-10-10 2018-03-27 武汉斗鱼网络科技有限公司 Method, storage medium, electronic equipment and the system of automatic monitoring data storehouse service
CN108536447A (en) * 2018-04-11 2018-09-14 上海掌门科技有限公司 Operation management method
CN109120678A (en) * 2018-07-26 2019-01-01 北京百度网讯科技有限公司 The method and apparatus of service tray for distributed memory system
CN110308983A (en) * 2019-04-19 2019-10-08 中国工商银行股份有限公司 Method for balancing resource load and system, service node and client
WO2019218510A1 (en) * 2018-05-17 2019-11-21 平安科技（深圳）有限公司 Multi-service system interaction method and apparatus, storage medium, and electronic terminal
CN110995489A (en) * 2019-12-03 2020-04-10 北京锐安科技有限公司 Large data platform server management method, device, server and storage medium
CN111447103A (en) * 2020-03-09 2020-07-24 杭州海康威视***技术有限公司 Virtual device management system, electronic device, virtual device management method, and medium
CN113055492A (en) * 2021-03-25 2021-06-29 深圳云之家网络有限公司 Control method and device for service gray scale link, computer equipment and storage medium
CN113422812A (en) * 2021-06-08 2021-09-21 北京邮电大学 Service chain deployment method and device
CN113608767A (en) * 2021-08-10 2021-11-05 掌阅科技股份有限公司 Service upgrade processing method, electronic device and storage medium
WO2021226784A1 (en) * 2020-05-11 2021-11-18 深圳市欢太科技有限公司 Node configuration method and apparatus, distributed system, and computer readable medium
CN113704083A (en) * 2021-03-09 2021-11-26 腾讯科技（深圳）有限公司 Test case generation method and device, storage medium and electronic equipment
CN114003312A (en) * 2021-10-29 2022-02-01 广东智联蔚来科技有限公司 Big data service component management method, computer device and storage medium
CN114115821A (en) * 2021-12-03 2022-03-01 北京百度网讯科技有限公司 Application development method and platform, application deployment method and node, system and equipment

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9906604B2 (en) * 2015-03-09 2018-02-27 Dell Products L.P. System and method for dynamic discovery of web services for a management console
US20170180372A1 (en) * 2015-12-16 2017-06-22 Fluke Corporation Project documentation sharing and collaboration in a cloud-based environment
US10091057B2 (en) * 2015-12-28 2018-10-02 Ca, Inc. Configuring distributed monitoring systems
CN110971432B (en) * 2018-09-29 2021-05-18 华为技术有限公司 Data transmission method and related device

Patent Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7493624B1 (en) * 2003-12-30 2009-02-17 Sap Ag Management architecture and method employed within a clustered node configuration
WO2015000362A1 (en) * 2013-07-05 2015-01-08 华为技术有限公司 Service node configuration method, service node pond register and system
CN103546327A (en) * 2013-11-05 2014-01-29 重庆邮电大学 Method for building hybrid-topology network management model based on JXTA
CN106921532A (en) * 2015-12-25 2017-07-04 中国电信股份有限公司 A kind of performance management method, the device of business catenary system
CN107844399A (en) * 2017-10-10 2018-03-27 武汉斗鱼网络科技有限公司 Method, storage medium, electronic equipment and the system of automatic monitoring data storehouse service
CN108536447A (en) * 2018-04-11 2018-09-14 上海掌门科技有限公司 Operation management method
WO2019218510A1 (en) * 2018-05-17 2019-11-21 平安科技（深圳）有限公司 Multi-service system interaction method and apparatus, storage medium, and electronic terminal
CN109120678A (en) * 2018-07-26 2019-01-01 北京百度网讯科技有限公司 The method and apparatus of service tray for distributed memory system
CN110308983A (en) * 2019-04-19 2019-10-08 中国工商银行股份有限公司 Method for balancing resource load and system, service node and client
CN110995489A (en) * 2019-12-03 2020-04-10 北京锐安科技有限公司 Large data platform server management method, device, server and storage medium
CN111447103A (en) * 2020-03-09 2020-07-24 杭州海康威视***技术有限公司 Virtual device management system, electronic device, virtual device management method, and medium
WO2021226784A1 (en) * 2020-05-11 2021-11-18 深圳市欢太科技有限公司 Node configuration method and apparatus, distributed system, and computer readable medium
CN113704083A (en) * 2021-03-09 2021-11-26 腾讯科技（深圳）有限公司 Test case generation method and device, storage medium and electronic equipment
CN113055492A (en) * 2021-03-25 2021-06-29 深圳云之家网络有限公司 Control method and device for service gray scale link, computer equipment and storage medium
CN113422812A (en) * 2021-06-08 2021-09-21 北京邮电大学 Service chain deployment method and device
CN113608767A (en) * 2021-08-10 2021-11-05 掌阅科技股份有限公司 Service upgrade processing method, electronic device and storage medium
CN114003312A (en) * 2021-10-29 2022-02-01 广东智联蔚来科技有限公司 Big data service component management method, computer device and storage medium
CN114115821A (en) * 2021-12-03 2022-03-01 北京百度网讯科技有限公司 Application development method and platform, application deployment method and node, system and equipment

Also Published As

Publication number Publication date
CN114615128A (en) 2022-06-10

Similar Documents

Publication Publication Date Title
CN110532020B (en) Data processing method, device and system for micro-service arrangement
US10462018B2 (en) Managing a number of secondary clouds by a master cloud service manager
CN107005422B (en) System and method for topology based management of next day operations
US20070220494A1 (en) A Method of Rapid Software Application Development for a Wireless Mobile Device
Soldani et al. ToscaMart: a method for adapting and reusing cloud applications
US20230054760A1 (en) Deployment strategies for continuous delivery of software rtifacts in cloud platforms
CN112711397A (en) Method and system for establishing system based on micro-service and top-level design
CN113849399A (en) Automatic testing system and method for multi-machine cooperative software under multi-localization platform
Krainyk et al. Internet-of-Things Device Set Configuration for Connection to Wireless Local Area Network.
CN111522623B (en) Modularized software multi-process running system
Brabra et al. Toward higher-level abstractions based on state machine for cloud resources elasticity
CN114615128B (en) Service management method and system, computer storage medium and electronic equipment
Siebra et al. From theory to practice: The challenges of a DevOps infrastructure as code implementation
CN112418796B (en) Sub-process task node activation method and device, electronic equipment and storage medium
CN115291928A (en) Task automatic integration method and device of multiple technology stacks and electronic equipment
Zengin et al. Clam: Managing cross-layer adaptation in service-based systems
Dalvi Cloud infrastructure self service delivery system using infrastructure as code
Ullah et al. IoT resource management using direct discovery mechanism in OCF framework
WO2022154811A1 (en) System configuration freeze and change management of services deployed via continuous delivery on datacenters configured in cloud platforms
Riti et al. Infrastructure as Code
Akue et al. Integrating an online configuration checker with existing management systems: Application to CIM/WBEM environments
Edmondson et al. Automating testing of service-oriented mobile applications with distributed knowledge and reasoning
Fortino et al. INTER-meth: a methodological approach for the integration of heterogeneous IoT systems
Calcaterra et al. Policy-based holistic application management with bpmn and tosca
US20230071504A1 (en) Multi-client orchestrated automated testing platform

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant