Service development method and device and computer program product
By generating and registering metadata for service nodes in a complex network environment, ensuring that the identity headers of the server and local child nodes are the same but the identification values are different, precise calls for service development are realized, and inefficiency and errors caused by static addressing methods are solved. The problem has improved development efficiency and accuracy.
Patent Information
- Application Number
- CN202411412794.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-11
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2044-10-11
AI Technical Summary
In complex network environments, service development based on static addressing is inefficient, and it is easy to cause call errors to cause service development failure.
By deploying the service node to the server, generating and registering metadata, matching child nodes from the specified component according to the target metadata, ensuring that the identity headers of the server child node and the local child node are the same but the identification values are different, and precise calls are achieved and necessary Detect traffic and enable routing rules to avoid errors.
Improve the accuracy and efficiency of service development, avoid service development failures caused by call errors, and improve development efficiency.
Smart Images

Figure CN118916184A_ABST
Abstract
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 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 technology.
[0005] In order to achieve the above-mentioned object, 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 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, registering the sub-nodes in each service node; automatically generating metadata corresponding to each sub-node during registration, and registering the metadata to a designated component after a specified sending condition is met; after registering to the designated component, obtaining a service development request, determining whether a sub-node call routing rule is enabled, and if enabled, calling the corresponding sub-node according to the sub-node call routing rule, wherein the sub-node call routing rule comprises parsing data on the service development request to obtain target metadata in the development request; matching the sub-node from the designated component based on the target metadata for calling for development; wherein, when automatically generating metadata corresponding to each sub-node in each service, the identification headers of the server sub-node and the local sub-nodes of different developers are made the same, and the identification values of the server sub-node and the local sub-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 specified 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 if the current traffic exceeds a threshold, calling a server sub-node in the same local area network.
[0009] Optionally, 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.
[0010] Optionally, during the process of matching a sub-node for development, 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 invocation.
[0011] According to a second aspect of the present invention, a service development device is provided, comprising a deployment unit, configured to deploy 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 a specified sending condition is met, the metadata is registered to a specified component; a development unit, configured to obtain a service development request after registering to the specified component, determine whether a 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 comprises performing data parsing on the service development request to obtain target metadata in the development request; and matching sub-nodes from the specified component based on the target metadata for calling for development; wherein, when automatically generating metadata corresponding to each sub-node in each service, the identification headers of the server sub-node and the local sub-nodes of different developers are made the same, and the identification values of the server sub-node and the local sub-nodes of different developers are made different.
[0012] According to a third aspect of the present invention, there is provided a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, wherein the computer instructions are used to cause the computer to execute the method described in any one of the implementations of the first aspect.
[0013] According to a fourth aspect of the present invention, there is provided an electronic device 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 method according to any one of the implementation modes of the first aspect is implemented.
[0015] This embodiment is used for a service development method, device and computer program product, wherein the method includes deploying different services as service nodes on a 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 after the specified sending conditions are met, the metadata is registered to the specified component. By automatically generating metadata of service sub-nodes according to unified specifications and matching specific sub-nodes of the metadata in the specified component, the problem of service development failure due to call errors and low development efficiency during service development is avoided. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0017] Figure 1 is a flow chart of a service development method according to an embodiment of the present invention; Figure 2 is a schematic diagram of an application scenario of a service development method according to an embodiment of the present invention; Figure 3 is a schematic diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION
[0018] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme 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 described embodiments 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 creative work should fall within the scope of protection of the present invention.
[0019] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so as to describe the embodiments of the present invention described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0020] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments 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.
[0021] 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: Step 101: 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 meeting the specified sending conditions, the metadata is registered to the specified component.
[0022] In this step, refer to Figure 2 , each service as a service node can be a service used to achieve independent business purposes, 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 sub-nodes, including sub-nodes on the server, and / or sub-nodes started and run locally by one or more different developers. The sub-node represents the specific implementation of the node. This step physically isolates the sub-nodes in different nodes, providing an isolated environment for calling service nodes during service development.
[0023] If there is an association between each service node, there may be occasional sub-node call errors during development. The solution to this situation in related technologies is usually IP addressing, which usually causes addressing errors in complex network environments because the real machine address cannot be obtained in complex network environments. Therefore, in this step, the sub-nodes of the deployed service nodes are registered with the specified components, and the matching of service sub-nodes is achieved through the specified components.
[0024] Furthermore, the designated component can be used to provide functions such as information registration and 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 to the designated component, but in a complex network environment, there are problems with network delays and partitions. If the designated component is communicated directly, the service sub-node status will not be updated in time, which will 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 a heartbeat mechanism, it indicates that the current state of the sub-node is the running state.
[0025] Generating metadata according to the specified unified specification may include that the sub-node identification headers of various nodes deployed on the same server are the same, and the identification values of local sub-nodes of different developers in the same node are different.
[0026] Step 102: After registering with the specified 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 and obtaining the target metadata in the development request; based on the target metadata, call the sub-node matched from the specified component for development.
[0027] In this step, after receiving a service development request from different terminals, the development request is parsed, and the parsing may be performed by a preset parsing module. The development request may be a development request obtained by the terminal after configuration, and the development request includes configuration parameters, which may be obtained after parsing, and the configuration parameters include an identification header and an identification value of the development request.
[0028] 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 run locally in each service node, and there are server sub-nodes at the same time, so 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.
[0029] 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 specified component, the child node corresponding to the metadata is determined as the matching child node.
[0030] In this optional implementation, when automatically generating metadata, the identification value of the sub-nodes on the server is the same, which can be empty; the local sub-nodes of different developers in each service node correspond to different, unique values. Exemplarily, service node A can include 3 sub-nodes registered in the specified component, namely: the sub-node on the server, with an identification header of k and an identification value of empty; the sub-node started and run locally by developer A, with an identification header of k and an identification value of A; the sub-node started and run locally by developer B, with an identification header of k and an identification value of A.
[0031] When generating metadata, in addition to registering the identification header and identification value to the specified component, the IP corresponding to the subnode is associated with the identification header and identification value during registration. When matching the service subnode, the matching subnode is determined from the specified component based on the identification value, and the subnode is called based on the IP corresponding to the matching subnode. It should be understood that the subnode can also be called directly based on the matched identification value, and in order to avoid errors 100%, it is preferably called using a determined IP.
[0032] Therefore, if the identification value in the development request is not empty, the child node with the same identification value is called; if the identification value in the development request is empty, the child node on the server is called. This method prevents different developers from 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.
[0033] 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 subnode is called.
[0034] In this optional implementation, if the specified component can match the same value as the identification value of the target metadata, the corresponding child node is called. For example, if developer A requests development through the terminal, the child node corresponding to developer A is determined from the specified component based on the information in the development request, and then the corresponding child node is accessed to implement the development. If a user who is not a developer but an unknown user requests development through the terminal, the server child node is called.
[0035] If there is an identification header but the child node cannot 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 unknown user, that is, the value is empty, when the development is requested through the terminal, the server child node is called.
[0036] As an optional implementation of this embodiment, during the process of matching a sub-node for development, 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.
[0037] In this optional implementation, some of the service nodes do not exist independently, but have a dependency or association relationship with other nodes. Therefore, it is possible to call other service nodes during the development of the current service node, such as reference 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 development request of the terminal. 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 development request of the terminal. The original identification header and identification value are used as parameters to constitute the header information in the new development request. Through the new development request, the child on the server in the downstream service node or the corresponding locally running child node can be further called.
[0038] As an optional implementation of this embodiment, after matching the child nodes from the specified component based on the target metadata, the method also includes: detecting the current traffic of the matched child nodes; if the current traffic exceeds a threshold, calling the server child node in the same local area network.
[0039] 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, it will cause slow response, which will affect development efficiency. In this case, after matching any server sub-node, the traffic of the current server sub-node is 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.
[0040] 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 service sub-node in the same local area network is called.
[0041] 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.
[0042] 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 to avoid development errors and low development efficiency.
[0043] 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.
[0044] According to an embodiment of the present invention, a service development device is also provided, including a deployment unit, configured to deploy different services as service nodes on a 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 after the specified sending conditions are met, the metadata is registered to a specified component; a development unit is configured to obtain a service development request after registering with the specified component, determine whether a 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 performing data parsing on the service development request to obtain target metadata in the development request; based on the target metadata, matching the sub-node from the specified component to call for development; wherein, when automatically generating metadata corresponding to each sub-node in each service, the identification header of the server sub-node and the local sub-nodes of different developers are made the same, and the identification values of the server sub-node and the local sub-nodes of different developers are made different.
[0045] 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 specified component, the child node corresponding to the metadata is determined as the matching child node.
[0046] 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 subnode is called.
[0047] As an optional implementation of this embodiment, after matching the child nodes from the specified component based on the target metadata, the method also includes: detecting the current traffic of the matched child nodes; if the current traffic exceeds a threshold, calling the server child node in the same local area network.
[0048] 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.
[0049] As an optional implementation of this embodiment, during the process of matching a sub-node for development, 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.
[0050] 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 executable 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.
[0051] 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.
[0052] 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.
[0053] Figure 3 A schematic block diagram of an example electronic device 300 that can be used to implement an embodiment 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 may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices.
[0054] 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. In the RAM 303, various programs and data required for the operation of the electronic device 300 can also be stored. 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.
[0055] A number of 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 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 through a computer network such as the Internet and / or various telecommunication networks.
[0056] The computing unit 301 may 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 running 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 may be implemented as a computer software program, which is tangibly included in a machine-readable medium, such as a storage unit 308. In some embodiments, part or all of the computer program may 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 may be performed.
[0057] Various implementations of the systems and techniques described above 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), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including 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.
[0058] The program code for implementing the method of the present invention can be written in any combination of one or more programming languages. These program codes 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 the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, partially on the machine as a stand-alone software package and partially on a remote machine, or entirely on a remote machine or server.
[0059] In the context of the present invention, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
Claims
1. A service development approach, It is 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 specified 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 matched from the specified component for development; 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, It is 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, It is 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, It is characterized in that If metadata with the same identification header and identification value as those in the target metadata can be matched from the specified component, the child node corresponding to the metadata is determined as the matched child node.
5. The service development method according to claim 1, It is characterized in that 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.
6. The service development method according to claim 1, It is 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.
7. A service development device, It is 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 performing data parsing on the service development request to obtain target metadata in the development request; and call a matching sub-node from a designated component based on the target metadata for development; 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.
8. A computer-readable storage medium, It is 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 6.
9. An electronic device, It is 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-6.
10. A computer program product, It is characterized in that The method comprises a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 6.
Citation Information
Patent Citations
Service generation system and method
CN109117152A
Service request routing method and device
CN110581890A
Distributed relational database based on HDFS metadata server and construction method
CN112395354A
Data processing method and device based on cloud native platform system
CN117499396A
Generating Interfaces From Data and Service Definitions For Developing Applications
US20200272434A1
