WO2022193979A1 - Procédé et système de développement de microservice, et dispositif informatique et support - Google Patents

Procédé et système de développement de microservice, et dispositif informatique et support Download PDF

Info

Publication number
WO2022193979A1
WO2022193979A1 PCT/CN2022/079551 CN2022079551W WO2022193979A1 WO 2022193979 A1 WO2022193979 A1 WO 2022193979A1 CN 2022079551 W CN2022079551 W CN 2022079551W WO 2022193979 A1 WO2022193979 A1 WO 2022193979A1
Authority
WO
WIPO (PCT)
Prior art keywords
microservice
node
development
public
address
Prior art date
Application number
PCT/CN2022/079551
Other languages
English (en)
Chinese (zh)
Inventor
施瑜
刘源
Original Assignee
易保网络技术(上海)有限公司
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 易保网络技术(上海)有限公司 filed Critical 易保网络技术(上海)有限公司
Publication of WO2022193979A1 publication Critical patent/WO2022193979A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • 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/04—Network management architectures or arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • 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/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • 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/50—Network services
    • H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
    • 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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context

Definitions

  • the present invention relates to the field of computer technology, and in particular, to a microservice development method, system, and associated computer equipment and medium.
  • Microservice architecture is a new technology for deploying applications and services in the cloud. Microservices are split from the original single business system into multiple small applications that can be independently developed, involved, operated and maintained. Microservices is an architectural style, for example, an application needs to be composed of at least one microservice. Each microservice in the system can be deployed independently, and each microservice is loosely coupled. Each microservice, as a small application, is only focused on accomplishing one task and doing it well. Moreover, when technicians upgrade a microservice, they often test the microservice to ensure that the updated microservice can be used normally with other microservices in the software application.
  • a microservice development method applied to the development of microservice nodes includes: deploying a running instance of the microservice; converting the IP address of the development microservice node and the The microservice name of the deployed microservice is registered with the microservice registration server; and the test of the running instance of the microservice is initiated.
  • the IP address of the development microservice node is associated with the microservice name of the microservice on the microservice registration server.
  • the running instance of the microservice is privately accessed.
  • the development microservice node invokes the running instance of the microservice deployed on the public microservice node.
  • invoking the running instance of the microservice deployed on the public microservice node includes: the development microservice node querying the microservice registration server for the microservice called by the test the microservice name.
  • the development microservice node obtains an IP address associated with the microservice name from the microservice registration server, wherein the IP address includes the public microservice node IP address.
  • the development microservice node selects the IP address of the public microservice node for testing, so as to invoke the running instance of the microservice deployed on the public microservice node.
  • the development microservice node when the IP address also includes the IP address of the development microservice node, the development microservice node preferentially selects the IP address of the development microservice node to call the microservice. Run the example to test.
  • the development microservice node is a computing node composed of one or more entity computers.
  • the method runs under the Spring Cloud microservice framework.
  • a microservice development method applied to a public microservice node includes: deploying a running instance of the microservice, wherein the running instance of the microservice keeps run for other nodes to test; register the IP address of the public microservice node and the microservice name of the deployed microservice with the microservice registration server.
  • the IP address of the public microservice node is associated with the microservice name of the microservice on the microservice registration server.
  • the running instance of the microservice is publicly accessible.
  • the public microservice node obtains the IP address associated with the microservice name from the microservice registration server.
  • the public microservice node selects the obtained IP address to invoke the running instance of the microservice deployed on other nodes.
  • the public microservice node is a computing node composed of one or more entity computers.
  • the method runs under the Spring Cloud microservice framework.
  • a micro-service development system for developing micro-service nodes, wherein the system includes: a deployment module, the deployment module deploys a running instance of the micro-service; a registration module , the registration module registers the IP address of the development microservice node and the microservice name of the deployed microservice to the microservice registration server; and a test module, which initiates the operation of the microservice instance test.
  • the IP address of the development microservice node is associated with the microservice name of the microservice on the microservice registration server.
  • the running instance of the microservice is accessed privately.
  • test module when the test module initiates the test on the running instance of the microservice, invokes the test module of the microservice deployed on the public microservice node. Run the instance.
  • the test module invoking the running instance of the microservice deployed on the public microservice node includes: the registration module queries the microservice registration server for the test service The microservice name of the called microservice.
  • the microservice development system obtains the IP address associated with the microservice name, wherein the IP address includes the IP address of the public microservice node.
  • the test module selects the IP address of the public microservice node for testing, so as to invoke the running instance of the microservice deployed on the public microservice node.
  • the test module when the IP address also includes the IP address of the development microservice node, the test module preferentially selects the IP address of the development microservice node to call the microservice. Run the example to test.
  • the development microservice node is a computing node composed of one or more entity computers.
  • the system runs under the Spring Cloud microservice framework.
  • a microservice development system applied to a public microservice node includes: a deployment module, the deployment module deploys a running instance of the microservice, wherein the The running instance of the microservice keeps running for other nodes to test; the registration module registers the IP address of the public microservice node and the microservice name of the deployed microservice with the microservice registration server.
  • the IP address of the public microservice node is associated with the microservice name of the microservice on the microservice registration server.
  • the running instance of the microservice is publicly accessible.
  • the system obtains the IP address associated with the microservice name from the microservice registration server.
  • system further includes a calling module, the calling module selects the obtained IP address to call the running instance of the microservice deployed on other nodes.
  • the public microservice node is a computing node composed of one or more entity computers.
  • the system runs under the Spring Cloud microservice framework.
  • a computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing a computer program according to the present invention when the processor executes the program The steps of the method of the aspect.
  • a recording medium having stored thereon a computer program executed by a computer to implement the steps of the method according to an aspect of the present invention.
  • single or multiple microservice nodes can be developed and debugged without simultaneously starting the entire microservice link or other microservice nodes unrelated to the single or multiple microservice nodes;
  • a microservice node can implement routing selection by calling other microservice nodes or development nodes, thereby saving microservice node resources.
  • Figure 1 shows a schematic diagram 100 of microservice development according to one embodiment of the present invention.
  • FIG. 2 shows a schematic diagram 200 of microservice development according to another embodiment of the present invention.
  • FIG. 3 shows a microservice development method 300 applied to develop a microservice node according to an embodiment of the present invention.
  • FIG. 4 shows a microservice development method 400 applied to a public microservice node according to an embodiment of the present invention.
  • FIG. 5 shows a microservice development system 500 applied to develop a microservice node according to an embodiment of the present invention.
  • FIG. 6 shows a microservice development system 600 applied to a public microservice node according to an embodiment of the present invention.
  • FIG. 7 is an example block diagram 700 of a computer device for the methods described herein, according to one embodiment of the present invention.
  • These computer program instructions may be stored in a computer readable memory, the instructions may instruct a computer or other programmable processor to perform functions in a particular manner, such that the instructions stored in the computer readable memory constitute the flowcharts and/or A manufactured product of the instruction components for the function/operation specified in one or more of the blocks of the block diagram.
  • the present disclosure proposes a microservice development method, system, and computer device and medium.
  • the method, device and computer medium involved in the present invention can be used for micro-service development between public micro-service nodes, micro-service registration servers and development micro-service nodes in a micro-service link. Nodes implement a limited number of microservice startups, and can be dev-tested against a single or several microservices.
  • FIG. 1 shows a schematic diagram 100 of microservice development according to one embodiment of the present invention.
  • the microservice development method according to the present invention may include three parties, namely a public microservice node 101 , a microservice registration server 102 and a development microservice node 103 .
  • the node server is not necessarily a single entity computer, but may be a computing node composed of one or more computers, servers or computing devices. All or part of the running instance of the microservice can be run on the computing node.
  • the public microservice node 101 is a public node on which multiple running instances of the microservices 110, 120 to N are deployed (depending on the computing capability of the public microservice node).
  • the running instance of the microservice running on the public microservice node 101 is public and can be invoked by any remote node.
  • the development microservice node 103 is a private node on which a running instance of the microservice 110 runs, and the running instance can only be accessed and debugged by the developer.
  • the microservice registration server is a public service registration server, on which the IP address of the microservice node and the microservice name of the microservice deployed on the microservice node can be registered, and the IP address of the microservice node can be deployed on the server.
  • the microservice name associated with the microservice can also obtain the IP address of the associated microservice node by parsing the microservice name of the microservice.
  • the present disclosure provides a brand-new microservice development method. Methods can run under the Spring Cloud microservices framework. As shown in FIG. 1 , the development microservice node 103 deploys only the running instance of the microservice 110 , while the public microservice node 101 may deploy multiple running instances of the microservice 120 to N depending on its computing capability. At the beginning of the method, the public microservice node 101 and the development microservice node 103 respectively register their IP addresses and the microservice name of the deployed microservice with the microservice registration server. When the running instance of the microservice is started, the microservice name of the microservice and the IP address of the node where the microservice is deployed will be registered on the microservice registration server and associated as a mapping relationship.
  • the IP address of the node and the microservice name of the microservice deployed on the node are associated.
  • the node can obtain the address of the node where the microservice associated with the microservice name is deployed by querying the microservice name. The specific method will be introduced below.
  • the development microservice node 103 may begin testing the running instance of the microservice 110 .
  • testing of a running instance of microservice 110 may involve invoking a running instance of microservice 120 .
  • the development microservice node 103 will query the microservice registration server 102 for the microservice name of the microservice 120.
  • the microservice registration server 102 parses the microservice name of the microservice 120 and finds the IP address associated with the microservice name on the microservice registration server 102, ie, the IP address of the public microservice node.
  • the development microservice node will periodically obtain the IP address of the node associated with the microservice name from the microservice registration server 102 .
  • the development microservice node 103 selects the obtained IP address of the public microservice node to call the running instance of the microservice 120 on the public microservice node 101 for testing, thereby avoiding deploying the running instance of the microservice 120 to the local development microservice node work.
  • remotely calling the running instance of the microservice on the public microservice development node can realize the joint development and invocation of the microservice by multiple private development microservice nodes. In parallel, the utilization efficiency of running instances of microservices is improved.
  • the public microservice node 103 can also call the running instance of the microservice on the development microservice node 101 when necessary.
  • the development microservice node 101 invokes the running instance of the microservice 120 of the public microservice node 103
  • the running instance of the microservice 120 may need information of the running instance of the microservice 110 . Therefore, the public microservice node 103 will query the microservice name of the microservice 110 on the microservice registration server 102 .
  • the public microservice node 103 obtains the IP address associated with the microservice name of the microservice 110 from the microservice registration server 102 , that is, the IP address of the development microservice node 101 . .
  • the public microservice node 103 selects the IP address to call the running instance of the microservice 110 deployed on the development microservice node, so as to satisfy the development microservice node 101's call to the running instance of the microservice 120 on the public microservice node 103.
  • This implementation develops the testing of the microservice by the microservice node.
  • FIG. 2 shows a schematic diagram 200 of microservice development according to another embodiment of the present invention.
  • the microservice development method described in FIG. 2 can further realize the optimal routing of the microservice by the development microservice node.
  • the public microservice node 201 in FIG. 2 is also deployed with a running instance of the microservice 210 , and other parts are the same as those in FIG. 1 .
  • the development microservice node 203 begins testing the running instance of the microservice 210, this may involve the running instance of the microservice 220. Therefore, when the running example of the microservice is started, the microservice name of the microservice is registered on the microservice registration server 202 .
  • the microservice registration server 202 resolves the microservice name and obtains the associated IP address (the IP address of the public microservice node 201).
  • the development microservice node 203 periodically obtains the associated IP address from the microservice registration server 202 .
  • the development microservice node 203 selects the IP address of the public microservice node 201 to call the running instance of the microservice 220 on the public microservice node 201 .
  • the running instance of microservice 220 is invoked, it may in turn involve the running instance of microservice 210 . Therefore, the development microservice node 203 queries the microservice registration server 202 for the microservice name of the microservice 210 .
  • the microservice registration server 202 resolves the microservice name of the microservice 210.
  • the microservice The service name is associated with the IP addresses of the two microservice nodes. Therefore, the development microservice node 203 will obtain the IP addresses of two or more microservice nodes. After obtaining multiple IP addresses (eg, two) associated with the microservice name of the microservice 210, the microservice node 203 will preferentially route to its own IP address (the IP address of the microservice node 203), thereby invoking the deployment.
  • the running instance of the microservice 210 on the local microservice node is developed, so that the local developer can call the running instance of the microservice 210 on the local development microservice node 203 .
  • FIG. 3 shows a microservice development method 300 applied to develop a microservice node according to an embodiment of the present invention.
  • the method includes three steps.
  • Step S301 deploys a running instance of the microservice;
  • step S302 registers the IP address of the development microservice node and the microservice name of the deployed microservice to the microservice registering a server; and
  • step S303 initiating a test on the running instance of the microservice.
  • step S301 the development microservice node deploys a running instance of the microservice thereon.
  • one or more running instances of the microservice to be tested can be deployed without deploying all the running instances of the related microservices on the development microservice node.
  • the running instance of the microservice on the development microservice node is private and accessible by the developer.
  • step S302 the development microservice node registers its IP address and the microservice name of the microservice deployed on it with the microservice registration server.
  • the microservice name of the microservice and the IP address of the node where the microservice is deployed will be registered on the microservice registration server and associated as a mapping relationship.
  • the development microservice node queries the microservice name on the microservice registration server, and then the microservice registration server can parse the microservice name and obtain the IP addresses on which the microservice to which the microservice name belongs is deployed.
  • step S303 the development microservice node will initiate a test on the running instance of the deployed microservice.
  • the testing of the running instance of the deployed microservice may involve a running instance of the microservice that is not deployed on the development microservice node.
  • the development microservice node will invoke the running instance of the microservice deployed on the public microservice node.
  • the invocation method specifically includes that the development microservice node registers the microservice name of the microservice called by the test with the microservice registration server.
  • the microservice registration server will resolve the microservice name and obtain the IP address associated with the microservice name, that is, the IP address of the public microservice node where the running instances of multiple microservices are deployed.
  • the development microservice node will periodically obtain the associated IP address (for example, the IP address of the public microservice node) from the microservice registration server, so the development microservice node selects the IP address of the public microservice node to call and deploy it on the public microservice node The running instance of the microservice on the server, so as to realize the test of the running example of the microservice.
  • the development microservice node when the microservice registration server parses the microservice name and finds that the microservice name is associated with multiple IP addresses, the development microservice node will obtain the multiple IP addresses. In the case where multiple IP addresses include the IP address of the development microservice node, the development microservice node will preferentially select the IP address of the development microservice node to call the running example of the microservice for testing.
  • FIG. 4 shows a microservice development method 400 applied to a public microservice node according to an embodiment of the present invention.
  • the method includes two steps, step S401 deploys a running instance of the microservice, wherein the running instance of the microservice keeps running for other nodes to test; step S402 deploys the public microservice node The IP address and the microservice name of the deployed microservice are registered with the microservice registration server.
  • the public microservice node deploys a plurality of running instances of the microservice thereon, and the specific deployment quantity may depend on the computing capability of the public microservice node.
  • the public microservice node becomes the running pool of the running examples of the public microservice.
  • Other nodes can invoke the required running instance of the microservice from the common pool, wherein the running instance of the microservice is publicly accessible.
  • step S402 the public microservice node registers its IP address and the microservice name of the microservice deployed on it with the microservice registration server.
  • the IP address of the public microservice node is associated with the microservice name of the microservice deployed thereon on the microservice registration server.
  • the running instance of the microservice on the public microservice node may involve running instances of other microservices.
  • public microservice nodes can call running instances of other microservices.
  • the specific calling method is similar to the calling method in method 300 .
  • FIG. 5 shows a microservice development system 500 applied to develop a microservice node according to an embodiment of the present invention.
  • the method includes three modules, a deployment module 501, which deploys a running instance of a microservice; a registration module 502, which registers the IP address of the development microservice node and the microservice name of the deployed microservice is registered with the microservice registration server; and a test module 503, the test module 503 initiates a test on the running instance of the microservice.
  • the deployment module 501 deploys a running instance of the microservice thereon.
  • one or more running instances of the microservice to be tested can be deployed without deploying all the running instances of the related microservices on the development microservice node.
  • the running instance of the microservice on the development microservice node is private and accessible by the developer.
  • the registration module 502 registers its IP address and the microservice name of the microservice deployed thereon with the microservice registration server. On the microservice registry server, the IP address will be associated with the microservice name.
  • the development microservice node queries the microservice name on the microservice registration server, and then the microservice registration server can parse the microservice name to obtain the IP addresses on which the microservice to which the microservice name belongs is deployed.
  • the testing module 503 will initiate testing of the running instance of the deployed microservice.
  • the testing of the running instance of the deployed microservice may involve a running instance of the microservice that is not deployed on the development microservice node.
  • the development microservice node will invoke the running instance of the microservice deployed on the public microservice node.
  • system 500 can also perform calls to microservices.
  • the calling method specifically includes that the registration module 502 registers the microservice name of the microservice called by the test with the microservice registration server.
  • the microservice registration server will resolve the microservice name and obtain the IP address associated with the microservice name, that is, the IP address of the public microservice node where the running instances of multiple microservices are deployed.
  • the system 500 obtains the associated IP address, that is, the IP address of the public microservice node, from the microservice registration server.
  • the testing module 503 selects the IP address of the public microservice node to call the running instance of the microservice deployed on the public microservice node, so as to test the running instance of the microservice.
  • the system 500 obtains the multiple IP addresses from the microservice registration server.
  • the testing module 503 will preferentially select the IP address of the development microservice node to call the running example of the microservice for testing.
  • FIG. 6 shows a microservice development system 600 applied to a public microservice node according to an embodiment of the present invention.
  • the method includes two modules, a deployment module 601, which deploys a running instance of a microservice, wherein the running instance of the microservice keeps running for other nodes to test; a registration module 602, the registration module 602 registers the IP address of the public microservice node and the microservice name of the deployed microservice with the microservice registration server.
  • the deployment module 601 deploys a plurality of running instances of microservices thereon, and the specific deployment quantity may depend on the computing capability of the public microservice nodes.
  • the public microservice node becomes the running pool of the running examples of the public microservice.
  • Other nodes can invoke the required running instance of the microservice from the common pool, wherein the running instance of the microservice is publicly accessible.
  • the registration module 602 registers its IP address and the microservice name of the microservice deployed thereon with the microservice registration server.
  • the IP address of the public microservice node is associated with the microservice name of the microservice deployed thereon on the microservice registration server.
  • the running instance of the microservice on the public microservice node may involve running instances of other microservices.
  • system 600 may invoke running instances of other microservices.
  • the system can obtain the IP address from the microservice registration server, so as to select the IP address for invocation. The specific manner is similar to that in the system 500 .
  • the present invention is not limited to these embodiments, and the present invention can also be implemented in the following manner: a computer device for executing the above method or a The form of a computer program for executing the above-described method, the form of a computer program for realizing the functions of the above-described apparatus, or the form of a computer-readable recording medium on which the computer program is recorded.
  • FIG. 7 shows a computer device for the above-mentioned data encryption and decryption method according to an embodiment of the present invention.
  • computer device 700 includes memory 701 and processor 702 .
  • computer device 700 also includes a computer program stored on memory 701 and executable on processor 702 .
  • the processor executes the program, the steps shown in FIG. 1 , FIG. 2 , FIG. 3 and FIG. 4 are simultaneously implemented.
  • the present invention can also be implemented as a recording medium in which a program for causing a computer to execute the data encryption/decryption method as described above is stored.
  • disks for example, magnetic disks, optical disks, etc.
  • cards for example, memory cards, optical cards, etc.
  • semiconductor memories for example, ROM, nonvolatile memory, etc.
  • tapes etc.
  • Types eg, magnetic tapes, cassette tapes, etc.
  • the above-mentioned recording medium is loaded on the computer, the computer program recorded in the recording medium is read out by the computer and stored in the memory, the processors (CPU: Central Processing Unit), MPU: Micro Processing Unit (microprocessing unit) reads the computer program from the memory and executes it, thereby executing the data masking and restoring method in the above-mentioned embodiment and realizing the functions of the device of the data masking and restoring method in the above-mentioned embodiment.
  • CPU Central Processing Unit
  • MPU Micro Processing Unit

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Debugging And Monitoring (AREA)

Abstract

La présente invention concerne un procédé et un système de développement de microservice, ainsi qu'un dispositif informatique associé et un support. En particulier, la présente invention concerne un procédé de développement de microservice appliqué à un nœud de microservice en développement, et est caractérisé en ce que le procédé comprend : le déploiement d'une instance d'exécution d'un microservice ; l'enregistrement d'une adresse IP du nœud de microservice en développement et d'un nom de microservice du microservice déployé à l'aide d'un serveur d'enregistrement de microservice ; et le lancement d'un test sur l'instance d'exécution du microservice.
PCT/CN2022/079551 2021-03-16 2022-03-07 Procédé et système de développement de microservice, et dispositif informatique et support WO2022193979A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110280004.XA CN115086412A (zh) 2021-03-16 2021-03-16 一种微服务开发方法、系统以及计算机设备和介质
CN202110280004.X 2021-03-16

Publications (1)

Publication Number Publication Date
WO2022193979A1 true WO2022193979A1 (fr) 2022-09-22

Family

ID=83246348

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/079551 WO2022193979A1 (fr) 2021-03-16 2022-03-07 Procédé et système de développement de microservice, et dispositif informatique et support

Country Status (2)

Country Link
CN (1) CN115086412A (fr)
WO (1) WO2022193979A1 (fr)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107979508A (zh) * 2017-11-24 2018-05-01 深圳乐信软件技术有限公司 微服务测试方法及装置
US20180198845A1 (en) * 2017-01-09 2018-07-12 International Business Machines Corporation Local Microservice Development for Remote Deployment
CN110324209A (zh) * 2019-08-02 2019-10-11 泰康保险集团股份有限公司 微服务系统监控方法、装置、电子设备及计算机可读介质
CN111782519A (zh) * 2020-06-29 2020-10-16 中国工商银行股份有限公司 测试方法、装置和电子设备
CN111782518A (zh) * 2020-06-29 2020-10-16 中国工商银行股份有限公司 测试方法、装置和电子设备
CN111782520A (zh) * 2020-06-29 2020-10-16 中国工商银行股份有限公司 测试方法、装置和电子设备
US20200401457A1 (en) * 2019-06-18 2020-12-24 Nutanix, Inc. Deploying microservices into virtualized computing systems

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107102847A (zh) * 2016-02-23 2017-08-29 中国水电工程顾问集团有限公司 基于微服务的软件开发方法、装置及系统
CN110636093B (zh) * 2018-06-25 2022-04-26 中兴通讯股份有限公司 微服务注册和发现方法、设备、存储介质以及微服务系统
CN111490890A (zh) * 2019-01-28 2020-08-04 珠海格力电器股份有限公司 基于微服务架构的分级注册方法、装置、存储介质及设备
CN110134455A (zh) * 2019-04-12 2019-08-16 平安医疗健康管理股份有限公司 一种应用管理系统及方法
CN110647469B (zh) * 2019-09-24 2023-09-08 广州荔支网络技术有限公司 一种微服务的测试方法、装置、计算机设备和存储介质
CN112463211A (zh) * 2020-07-28 2021-03-09 上海汇招信息技术有限公司 一种兼容多种开发架构的系统架构改造方法及系统架构

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180198845A1 (en) * 2017-01-09 2018-07-12 International Business Machines Corporation Local Microservice Development for Remote Deployment
CN107979508A (zh) * 2017-11-24 2018-05-01 深圳乐信软件技术有限公司 微服务测试方法及装置
US20200401457A1 (en) * 2019-06-18 2020-12-24 Nutanix, Inc. Deploying microservices into virtualized computing systems
CN110324209A (zh) * 2019-08-02 2019-10-11 泰康保险集团股份有限公司 微服务系统监控方法、装置、电子设备及计算机可读介质
CN111782519A (zh) * 2020-06-29 2020-10-16 中国工商银行股份有限公司 测试方法、装置和电子设备
CN111782518A (zh) * 2020-06-29 2020-10-16 中国工商银行股份有限公司 测试方法、装置和电子设备
CN111782520A (zh) * 2020-06-29 2020-10-16 中国工商银行股份有限公司 测试方法、装置和电子设备

Also Published As

Publication number Publication date
CN115086412A (zh) 2022-09-20

Similar Documents

Publication Publication Date Title
US8677327B2 (en) Service testing method and service testing system
WO2020062673A1 (fr) Procédé de test de contrat intelligent, support d'informations, terminal de test et dispositif de test
US20120047492A1 (en) Deployment of a tool for testing migrated applications
CN110647469A (zh) 一种微服务的测试方法、装置、计算机设备和存储介质
CN107241315B (zh) 银行网关接口的接入方法、装置及计算机可读存储介质
US11748487B2 (en) Detecting a potential security leak by a microservice
US10366228B2 (en) Detection and mitigation of malicious invocation of sensitive code
KR102262395B1 (ko) Nfv 시스템의 상호 운용성을 테스트하기 위한 테스트 장치
US20230333960A1 (en) Dynamic distributed tracing instrumentation in a microservice architecture
US20210288885A1 (en) Simulation and testing of infrastucture as a service scale using a container orchestration engine
US10579502B2 (en) Resuming applications using pass-through servers and trace data
US20230086377A1 (en) Dynamic automation of prerequisite component deployment in disconnected environments
US20110252403A1 (en) Component relinking in migrations
CN102662745B (zh) 一种虚拟机管理系统与方法
CN113434283B (zh) 服务调度方法及装置、服务器、计算机可读存储介质
WO2022193979A1 (fr) Procédé et système de développement de microservice, et dispositif informatique et support
US20200220778A1 (en) Debugging a network switch by replaying configuration
US11474930B2 (en) Software bug reproduction
CN111949484A (zh) 信息处理方法、装置、电子设备和介质
US10223238B1 (en) Multiple-stage crash reporting
US20220114222A1 (en) Identification of a computer processing unit
CN112506781B (zh) 测试监控方法、装置、电子设备、存储介质及程序产品
US20230008839A1 (en) Smart environment assessment of prerequisites to private cloud provisioning
CN113157607B (zh) 一种设备适配方法、装置、存储介质和计算机设备
EP3916540A1 (fr) Compilation de compositions de fonction unilingue dans une seule entité

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22770334

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22770334

Country of ref document: EP

Kind code of ref document: A1