Service development method, device and computer program product

Abstract

The present invention discloses a service development method, device and computer program product, wherein the method comprises deploying different services as service nodes on a server, wherein each service node comprises at least one sub-node, and the sub-nodes in each service node comprise server sub-nodes and / or local sub-nodes of different developers; during the deployment process, the sub-nodes in each service node are registered; metadata corresponding to each sub-node is automatically generated during registration, and after the specified sending conditions are met, the metadata is registered to a specified component. By automatically generating metadata of service sub-nodes according to a unified specification, and matching the metadata with specific sub-nodes in a specified component, the problem of service development failure due to call errors and low development efficiency during service development is avoided.

Description

Technical Field

[0001] The present invention relates to the technical field of service development, and in particular to a service development method, device and computer program product. Background Art

[0002] Service development uses a range of methods to identify, analyze and resolve potential problems to ensure that services can operate normally and meet performance and security requirements.

[0003] In the process of developing different services, if the network environment is relatively complex and development is based on static addressing, there are usually call errors that lead to poor service development efficiency. Summary of the Invention

[0004] The main purpose of the present invention is to provide a service development method, device and computer program product to solve the technical problems existing in the related art.

[0005] To achieve the above-mentioned objective, according to a first aspect of the present invention, a service development method is provided, comprising deploying different services as service nodes on a server, wherein each service node includes at least one child node, and the child nodes in each service node include a server child node and / or local child nodes of different developers; during the deployment process, registering the child nodes in each service node; automatically generating metadata corresponding to each child node during registration, and registering the metadata with a designated component after specified sending conditions are met; after registering with the designated component, obtaining a service development request, determining whether a child node call routing rule is enabled, and if so, calling the corresponding child node according to the child node call routing rule, wherein the child node call routing rule includes parsing data of the service development request to obtain target metadata in the development request; and matching child nodes from the designated component based on the target metadata for calling the development request; wherein, when automatically generating metadata corresponding to each child node in each service, the identification header of the server child node and the local child nodes of different developers are made identical, and the identification values ​​of the server child node and the local child nodes of different developers are made different.

[0006] Optionally, if metadata with the same identification header and identification value as those in the target metadata can be matched from the designated component, the child node corresponding to the metadata is determined as the matched child node.

[0007] Optionally, if there is an identification value in the target metadata but no identical value is matched from the specified component, the server child node is called.

[0008] Optionally, after matching a sub-node from a designated component based on the target metadata, the method further includes: detecting current traffic of the matched sub-node; and calling a server sub-node in the same local area network if the current traffic exceeds a threshold.

[0009] Optionally, after determining whether the sub-node call routing rule is enabled, if the determination result is that it is not enabled, the server sub-node is called.

[0010] Optionally, during the development process of matching a sub-node, if the development is dependent on other services, a new development request is generated to match the corresponding service sub-node from the specified component for calling.

[0011] According to a second aspect of the present invention, a service development apparatus is provided, comprising a deployment unit configured to deploy different services as service nodes on a server, wherein each service node includes at least one subnode, and the subnodes in each service node include a server subnode and / or local subnodes of different developers; during the deployment process, the subnodes in each service node are registered; metadata corresponding to each subnode is automatically generated during registration, and after specified sending conditions are met, the metadata is registered with a specified component; a development unit is configured to, after registration with the specified component, obtain a service development request, determine whether a subnode call routing rule is enabled, and if so, call the corresponding subnode according to the subnode call routing rule, wherein the subnode call routing rule includes parsing data of the service development request to obtain target metadata in the development request; and matching subnodes from the specified component based on the target metadata for calling for development; wherein, when automatically generating metadata corresponding to each subnode in each service, the identification headers of the server subnode and the local subnodes of different developers are made the same, and the identification values ​​of the server subnode and the local subnodes of different developers are made different.

[0012] According to a third aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the method described in any one of the implementation modes of the first aspect.

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

[0014] According to a fifth aspect of the present invention, a computer program product is provided. When the computer program is executed by a processor, the computer program implements the method according to any one of the implementation modes of the first aspect.

[0015] This embodiment provides a service development method, apparatus, and computer program product. The method includes deploying different services as service nodes on a server, wherein each service node includes at least one subnode, including server subnodes and / or local subnodes of different developers. During the deployment process, the subnodes within each service node are registered. During registration, metadata corresponding to each subnode is automatically generated, and upon meeting specified sending conditions, the metadata is registered with a specified component. By automatically generating metadata for service subnodes according to unified specifications and matching the metadata to specific subnodes within a specified component, service development failures and low development efficiency due to call errors are avoided during service development. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0017] Figure 1 is a flow chart of a service development method according to an embodiment of the present invention;

[0018] Figure 2 This is a schematic diagram of an application scenario of a service development method according to an embodiment of the present invention;

[0019] Figure 3 is a schematic diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

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

[0021] It should be noted that the terms "first," "second," and the like in the specification and claims of the present invention and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate for the embodiments of the present invention described herein. In addition, the terms "including," "having," and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to these processes, methods, products, or apparatuses.

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

[0023] According to an embodiment of the present invention, a service development method is provided, such as Figure 1 As shown, it includes the following steps 101 to 102:

[0024] Step 101: Deploy different services as service nodes on the server, wherein each service node includes at least one child node, and the child nodes in each service node include server child nodes and / or local child nodes of different developers; during the deployment process, register the child nodes in each service node; automatically generate metadata corresponding to each child node during registration, and after the specified sending conditions are met, the metadata is registered to the specified component.

[0025] In this step, refer to Figure 2 , each service serving as a service node can be a service used to achieve an independent business purpose, and each service is deployed to the server as an independent node. Use the server to deploy each independent service, and each independent service as one of the service nodes can form a dependency with other service nodes. Furthermore, each service node can have multiple child nodes, including child nodes on the server, and / or child nodes started and run locally by one or more different developers. The child node represents the specific implementation of the node. This step physically isolates the child nodes in different nodes, providing an isolated environment for calling service nodes during service development.

[0026] If each service node has an associated relationship, sub-node call errors may occasionally occur during development. The solution to this problem in related technologies is usually IP addressing, which often leads to addressing errors in complex network environments because the actual machine address may not be available. Therefore, in this step, the sub-nodes of the deployed service node are registered with the specified component, and the service sub-nodes are matched through the specified component.

[0027] Furthermore, the designated component can be used to provide functions such as information registration, information query and call. Unlike configuration files and domain name systems, manual management is not required. During the deployment process, the sub-node can be directly registered with the designated component. However, in a complex network environment, there are problems with network delays and partitioning. If you communicate directly with the designated component, it will cause the service sub-node status to be updated in a timely manner, which will in turn cause call errors. Therefore, when deploying, first, the sub-nodes in each node generate metadata according to the specified unified specifications. For example, when different service nodes are deployed, the sub-nodes in each service node generate metadata on the server, and then send the metadata to the designated component when the specified conditions are met. The specified condition can be that after the sub-nodes in each node are connected to the designated component through the heartbeat mechanism, it indicates that the current state of the sub-node is running.

[0028] Generating metadata according to a specified unified specification may include ensuring that sub-node identification headers of nodes deployed on the same server are the same and that identification values ​​of local sub-nodes of different developers in the same node are different.

[0029] Step 102: After registering with the designated component, obtain the service development request and determine whether the sub-node call routing rule is enabled. If enabled, call the corresponding sub-node according to the sub-node call routing rule, wherein the sub-node call routing rule includes parsing the service development request and obtaining the target metadata in the development request; based on the target metadata, call the sub-node matched from the designated component for development.

[0030] In this step, after receiving a service development request from a different terminal, the development request is parsed, which can be performed by a preset parsing module. The development request can be a development request obtained after the terminal is configured, and the development request includes configuration parameters. The configuration parameters can be obtained after parsing, and the configuration parameters include an identification header and identification value of the development request.

[0031] The development request is sent from the terminal, and the ultimate goal is to determine which service sub-node needs to be called for development in this development request. Since there are many service nodes, there are many sub-nodes started and running locally in each service node, and there are also server sub-nodes. Therefore, the corresponding sub-node can be determined by metadata matching. The target metadata in the development request is transmitted to the specified component, and the specified component matches the sub-node based on the metadata.

[0032] As an optional implementation of this embodiment, if metadata with the same identification header and identification value as those in the target metadata can be matched from the designated component, the child node corresponding to the metadata is determined as the matching child node.

[0033] In this optional implementation, when automatically generating metadata, the identification value of the child nodes on the server is the same, which can be empty. Local child nodes of different developers within each service node correspond to different, unique values. For example, service node A may include three child nodes registered with a designated component: a child node on the server, with an identification header of k and an empty identification value; a child node started and run locally by developer A, with an identification header of k and an identification value of A; and a child node started and run locally by developer B, with an identification header of k and an identification value of A.

[0034] When generating metadata, in addition to registering the identification header and identification value with the designated component, the IP address corresponding to the child node is associated with the identification header and identification value during registration. When matching a service child node, a matching child node is determined from the designated component based on the identification value, and the child node is called based on the IP address corresponding to the matching child node. It should be understood that a child node can also be called directly based on the matched identification value, but to fully avoid errors, it is preferably called using a specific IP address.

[0035] Therefore, if the identifier value in the development request is not empty, the child node with the same identifier value is called. If the identifier value in the development request is empty, the child node on the server is called. This method avoids different developers jumping to other developer child nodes or server child nodes when developing service nodes, such as Figure 2 In the example, if service node 2 contains child nodes on the server or locally running child nodes, such as developer A child node and opener B child node, the above method can prevent developer A from jumping to developer B child node or server child node when developing service node 2.

[0036] As an optional implementation of this embodiment, if there is an identification value in the target metadata but the same value cannot be matched from the specified component, the server child node is called.

[0037] In this optional implementation, if the specified component matches the target metadata's identification value, the corresponding child node is called. For example, if developer A requests development through a terminal, the corresponding child node is determined from the specified component based on the information in the development request, and the development is then accessed. If a user, not a developer, requests development through a terminal, whose identity is unclear, the server child node is called.

[0038] If there is an identification header but no child node can be matched based on the identification value, the server child node is called as the final child node. If the user is not a developer but an unidentified user (i.e., the value is empty), and development is requested through the terminal, the server child node is called.

[0039] As an optional implementation of this embodiment, during the development process of matching a sub-node, if the development depends on other services, a new development request is generated to match the corresponding service sub-node from the specified component for calling.

[0040] In this optional implementation, some of the service nodes do not exist independently, but have dependencies or associations with other nodes. Therefore, it is possible to call other service nodes during the development of the current service node, such as Figure 2 , if developing service node 1 or 2, it is also necessary to call the downstream service node to run. In this case, the development is carried out after calling the corresponding sub-node through the terminal's development request. If it is necessary to continue calling other service nodes during the development process, a new development request is automatically generated. The generated new development request contains an identification header and an identification value in the request header. The generated identification header and identification value are obtained by passing the current service node of the upstream service node to the downstream service node. For example, when the current service node is called for development, it is determined based on the original identification header and identification value in the terminal's development request. The original identification header and identification value serve as parameters to constitute the header information in the new development request. Through the new development request, you can further call the child on the server of the downstream service node or the corresponding locally running child node.

[0041] As an optional implementation of this embodiment, after matching a sub-node from a specified component based on the target metadata, the method further includes: detecting the current traffic of the matched sub-node; if the current traffic exceeds a threshold, calling a server sub-node in the same local area network.

[0042] In this optional implementation, local sub-nodes of different developers will basically not face the problem of excessive pressure. There are multiple sub-nodes on the server. If any sub-node is under excessive pressure, the response will be slow, which will affect the development efficiency. In this case, after matching any server sub-node, the traffic of the current server sub-node will be detected. If the traffic exceeds the threshold, another server sub-node will be replaced for calling to avoid development errors, low development efficiency and other defects.

[0043] As an optional implementation of this embodiment, after determining whether the routing rule for calling the child node is enabled, if the determination result is that it is not enabled, the service child node in the same local area network is called.

[0044] In this optional implementation, the routing rules can be turned on or off by terminal configuration, and when turned off, the server sub-node can be called for development requests.

[0045] This embodiment deploys different services as independent service nodes on the server, and registers the server sub-nodes and local startup sub-nodes in the service nodes to the specified components through metadata, so that the corresponding sub-nodes can be accurately called, avoiding development errors and the resulting low development efficiency.

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

[0047] According to an embodiment of the present invention, a service development apparatus is also provided, comprising a deployment unit configured to deploy different services as service nodes on a server, wherein each service node includes at least one subnode, and the subnodes in each service node include a server subnode and / or local subnodes of different developers; during the deployment process, the subnodes in each service node are registered; metadata corresponding to each subnode is automatically generated during registration, and after specified sending conditions are met, the metadata is registered with a specified component; a development unit configured to, after registration with the specified component, obtain a service development request, determine whether a subnode call routing rule is enabled, and if enabled, call the corresponding subnode according to the subnode call routing rule, wherein the subnode call routing rule includes parsing data of the service development request to obtain target metadata in the development request; and matching subnodes from the specified component based on the target metadata for calling for development; wherein, when automatically generating metadata corresponding to each subnode in each service, the identification headers of the server subnode and the local subnodes of different developers are made the same, and the identification values ​​of the server subnode and the local subnodes of different developers are made different.

[0048] As an optional implementation of this embodiment, if metadata with the same identification header and identification value as those in the target metadata can be matched from the designated component, the child node corresponding to the metadata is determined as the matching child node.

[0049] As an optional implementation of this embodiment, if there is an identification value in the target metadata but no identical value is matched from the designated component, the server subnode is called.

[0050] As an optional implementation of this embodiment, after matching a sub-node from a specified component based on the target metadata, the method further includes: detecting the current traffic of the matched sub-node; if the current traffic exceeds a threshold, calling a server sub-node in the same local area network.

[0051] As an optional implementation of this embodiment, after determining whether the sub-node calling routing rule is enabled, if the determination result is that it is not enabled, the server sub-node is called.

[0052] As an optional implementation of this embodiment, during the development process of matching a sub-node, if the development depends on other services, a new development request is generated to match the corresponding service sub-node from the specified component for calling.

[0053] According to an embodiment of the present invention, the present invention also provides an electronic device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can implement the method described in any of the above embodiments when executing.

[0054] According to an embodiment of the present invention, the present invention further provides a readable storage medium, which stores computer instructions, and the computer instructions are used to enable a computer to implement the method described in any of the above embodiments when executed.

[0055] According to an embodiment of the present invention, the present invention further provides a computer program product, which can implement the method described in any of the above embodiments when executed by a processor.

[0056] Figure 3A schematic block diagram of an example electronic device 300 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices, and other similar computing devices.

[0057] like Figure 3 As shown, the electronic device 300 includes a computing unit 301, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 302 or a computer program loaded from a storage unit 308 into a random access memory (RAM) 303. Various programs and data required for the operation of the electronic device 300 can also be stored in the RAM 303. The computing unit 301, the ROM 302, and the RAM 303 are connected to each other via a bus 304. An input / output (I / O) interface 305 is also connected to the bus 304.

[0058] Multiple components in the electronic device 300 are connected to the I / O interface 305, including an input unit 306, such as a keyboard, a mouse, etc.; an output unit 307, such as various types of displays, speakers, etc.; a storage unit 308, such as a magnetic disk, an optical disk, etc.; and a communication unit 309, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 309 allows the electronic device 300 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0059] The computing unit 301 can be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 301 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units that run machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 301 performs the various methods and processes described above, such as the object matching method. For example, in some embodiments, the object matching method can be implemented as a computer software program that is tangibly contained in a machine-readable medium, such as the storage unit 308. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 300 via the ROM 302 and / or the communication unit 309. When the computer program is loaded into the RAM 303 and executed by the computing unit 301, one or more steps of the method described above can be performed.

[0060] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0061] The program code for implementing the method of the present invention can be written in any combination of one or more programming languages. Such program code can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when the program code is executed by the processor or controller, the functions / operations specified in the flow chart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0062] In the context of the present invention, machine-readable medium can be a tangible medium that can contain or store a program for use with an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. Machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. More specific examples of machine-readable storage media can include electrical connections based on one or more lines, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

Claims

1. A service development method, characterized in that: include: Deploy different services as service nodes on the server, wherein each service node includes at least one sub-node, and the sub-nodes in each service node include server sub-nodes and / or local sub-nodes of different developers; during the deployment process, register the sub-nodes in each service node; automatically generate metadata corresponding to each sub-node during registration, and after the specified sending conditions are met, the metadata is registered to the specified component; After registering with the designated component, obtain the service development request, determine whether the sub-node call routing rule is enabled, and if enabled, call the corresponding sub-node according to the sub-node call routing rule, wherein the sub-node call routing rule includes parsing the service development request to obtain the target metadata in the development request; based on the target metadata, call the sub-node from the designated component match for development, wherein, if metadata identical to the identification header and identification value in the target metadata can be matched from the designated component, the sub-node corresponding to the metadata is determined as the matched sub-node; if there is an identification value in the target metadata but the same value cannot be matched from the designated component, call the server sub-node; When automatically generating metadata corresponding to each subnode in each service, the identification headers of the server subnode and the local subnodes of different developers are made the same, and the identification values ​​of the server subnode and the local subnodes of different developers are made different.

2. The service development method according to claim 1, characterized in that: During the development process of matching a subnode, if other services are still required to complete the development, a new development request is generated to match the corresponding service subnode from the specified component for calling.

3. The service development method according to claim 1, characterized in that: After matching the child nodes from the specified component based on the target metadata, the method further includes: Detect the current traffic of the matched child nodes; If the current traffic exceeds the threshold, the server child node in the same LAN is called.

4. The service development method according to claim 1, characterized in that: After determining whether the sub-node call routing rule is enabled, if the determination result is that it is not enabled, the server sub-node is called.

5. A service development device, characterized in that: include: The deployment unit is configured to deploy different services as service nodes on the server, wherein each service node includes at least one sub-node, and the sub-nodes in each service node include server sub-nodes and / or local sub-nodes of different developers; during the deployment process, the sub-nodes in each service node are registered; metadata corresponding to each sub-node is automatically generated during registration, and the metadata is registered to the specified component after the specified sending conditions are met; The development unit is configured to obtain a service development request after registering with a designated component, determine whether a sub-node call routing rule is enabled, and if enabled, call a corresponding sub-node according to the sub-node call routing rule, wherein the sub-node call routing rule includes parsing data on the service development request to obtain target metadata in the development request; based on the target metadata, call a sub-node matched from a designated component for development, wherein if metadata identical to an identification header and an identification value in the target metadata can be matched from the designated component, the sub-node corresponding to the metadata is determined as a matched sub-node; if there is an identification value in the target metadata but the same value cannot be matched from the designated component, the server sub-node is called; When automatically generating metadata corresponding to each subnode in each service, the identification headers of the server subnode and the local subnodes of different developers are made the same, and the identification values ​​of the server subnode and the local subnodes of different developers are made different.

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

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

8. A computer program product, characterized in that The invention comprises a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 4.

Images