CN113672278A - Service node version control method and device under micro-service architecture - Google Patents
Service node version control method and device under micro-service architecture Download PDFInfo
- Publication number
- CN113672278A CN113672278A CN202110965957.XA CN202110965957A CN113672278A CN 113672278 A CN113672278 A CN 113672278A CN 202110965957 A CN202110965957 A CN 202110965957A CN 113672278 A CN113672278 A CN 113672278A
- Authority
- CN
- China
- Prior art keywords
- service
- micro
- code
- version number
- git
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 74
- 230000008569 process Effects 0.000 claims abstract description 45
- 238000012795 verification Methods 0.000 claims abstract description 8
- 238000012856 packing Methods 0.000 claims abstract description 3
- 238000004590 computer program Methods 0.000 claims description 23
- 238000012544 monitoring process Methods 0.000 claims description 9
- 238000011161 development Methods 0.000 claims description 8
- 238000012986 modification Methods 0.000 claims description 5
- 230000004048 modification Effects 0.000 claims description 5
- 238000004806 packaging method and process Methods 0.000 claims description 5
- 238000007726 management method Methods 0.000 description 11
- 230000006870 function Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004886 process control Methods 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Mathematical Physics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a service node version control method and a device under a micro-service architecture, wherein the method comprises the following steps: generating a globally unique version number through code management software; packing the version number into a micro-service project operation directory file, reading the version number from the directory file when the process is started, and submitting the version number to a micro-service registration center through an API (application program interface) of the registration center; and then, the version number of each process instance of the micro service can be verified through an API (application program interface) of the micro service registration center, if the verification is passed, the codes are considered to be consistent, and if the verification is not passed, an alarm is given. Compared with the prior art, the service node version control method and device under the micro service architecture provided by the invention have the advantages that the consistency of all process code instances is realized, and the operation efficiency is improved.
Description
Technical Field
The invention relates to the technical field of micro services, in particular to a service node version control method and device under a micro service architecture.
Background
In the cloud computing era, micro-service architectures have been widely applied to the development and deployment of systems, and each logic service in micro-services can be provided with the same service by a plurality of process node programs. The micro service nodes can have mutual calling and mutual dependence. A large number of process nodes of each logic service may have a condition that running process codes are inconsistent, which may cause an error in a process of calling a same interface of a same service, for example, the same logic service has 5 different process instances providing the same service, but in a publishing process, 4 process instances already publish the latest logic, and the remaining 1 process instance forgets to publish the latest logic, so that there is a 20% probability that an error occurs in a calling interface, which causes an abnormality in the entire service, and causes a chain reflection that other dependent services have errors.
Therefore, it is necessary to provide a new service node version control method and apparatus under the micro service architecture to overcome the above-mentioned drawbacks.
Disclosure of Invention
The invention aims to provide a novel service node version control method and a novel service node version control device under a micro-service architecture, which realize the consistency of all process code instances and improve the operation efficiency.
In order to achieve the above object, the present invention provides a service node version control method under a micro-service architecture, including:
generating a globally unique version number through code management software;
packing the version number into a micro-service directory file, and submitting the directory file to a micro-service registration center;
and verifying the version number of each logic lower process instance of the micro-service through an API (application programming interface), wherein if the verification is passed, the codes are considered to be consistent, and if the verification is not passed, an alarm is given.
Further, the generating a globally unique version number by the code management software includes:
after the code development of the micro service is completed, code management is carried out through the version control of the git protocol;
each time the code of the micro-service is submitted, commit is done by git's command, which generates a globally unique version number git-commit-id.
Further, the version number includes commit-id, modification information of the code, a submission time of the code, and related submitter information and other related information.
Further, the packaging the version number into a directory file and submitting the directory file to the micro-service registry comprises:
in the development process of the micro-service, a project carries out project package management through maven, a standard maven plug-in is introduced through pom.xml, and a command git-commit-id: provision corresponding to git-commit-plug-in is executed through maven;
generating a standard git information maintained file git through the command under the directory of the target;
packaging git.
And uploading the data to metadata of the process of the registry by using the api provided by the microservice registry and the data structure of the dictionary so as to read and monitor the data.
Further, the verifying the version number of each process instance under the logic of the microservice through the api interface comprises:
acquiring a plurality of examples under the same micro service and version numbers of all deployment codes through an external API (application program interface) of a micro service registration center;
and deploying an external monitoring program to execute a timing task through the crontab, verifying the commit-id of the code version, recording if the commit-id is inconsistent, and verifying the commit-id in a double check mode.
The invention also provides a service node version control device under the micro-service architecture, which comprises a micro-service registration center, a code management module and a monitoring module;
the microservice registration center is used for containing code versions and code related information used by all started process instances;
the code management module is used for compiling and managing codes and submitting the codes to the micro-service registration center;
and the monitoring module is used for detecting and verifying the code version through the API interface code of the micro-service registration center.
The present invention further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the steps of the service node version control method under the micro service architecture.
The invention also provides a computer terminal, which comprises a memory, a processor and a computer program which is stored in the memory and can run on the processor, wherein the processor realizes the steps of the service node version control method under the micro-service architecture when executing the computer program.
Compared with the prior art, the service node version control method under the micro-service architecture can be used for centrally managing the code versions of a large number of service instances under the micro-service architecture, effectively and effectively combining git (code management), maven (project package management) and eureka (micro-service registration center), simultaneously inquiring the code version corresponding to each operation project and the submission information of related codes in real time, directly associating the code versions with specific code submission records when problems are located, and more clearly determining the specific codes used by service processes; meanwhile, the query can be carried out in real time through external monitoring measures, and the consistency of a large number of specific example codes of the same logic service is ensured through a monitoring program.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, the drawings in the following description are only some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts, wherein:
fig. 1 is a flowchart of a service node version control method under the micro service architecture of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, the present invention provides a service node version control method under a micro-service architecture, which can ensure a checking mechanism for code consistency of a large number of process instances under a service of the same logic level. Because the number of specifically deployed example processes of the same logic service is large in a large-scale micro-service system, the problem that the same codes are not all deployed synchronously in the deployment process can occur with a high probability, and the specific implementation of the same logic service is inconsistent, so that the inconsistency of the business logic level occurs. In the invention, git is code management, maven is project package management and eureka is a micro-service registration center.
S1, generating a globally unique version number through code management software; after the code is written, the code version management software gitlab after the code is submitted generates a globally unique submission version number git-commit-id.
After the development of all the codes of the micro-services is completed, all the codes are managed by the version control of the git protocol, and each time the codes of the micro-services are submitted, the codes are submitted by committing through the git command. After commit is performed, git generates a globally unique commit-id, code modification information, time of commit of the code, and associated submitter information and some other relevant information.
In the development process of all micro services, a project carries out package management of the project through maven, and simultaneously introduces a standard maven plug-in (git-commit-plugin plug-in) through pom. Through the command, a standard git information maintained file git.properties can be generated under a classes directory under the directory of the target, and globally unique commit-id, code modification information, code submission time, relevant submitter information and some other relevant information are recorded in the file in detail.
S2, packaging the version number into a micro-service directory file, and submitting the directory file to a micro-service registry; when maven is packed, the current git-commit-id information is recorded into a git.attributes file in a class directory through a utility git-commit-plugin, and when a program process instance of each micro-service is started, a code reads gir-commit-id information in the git.attributes file, and then the information is used as metadata information of the micro-service and is reported to metadata of an eureka cluster of a micro-service registration center.
After the file is generated, the information files of git. Therefore, when the program is deployed, the metadata information submitted by git commit submitted by all codes in the file can be read, when the deployment is started, the information can be read out from the file by the program and come into a memory of the process, and finally the information can be uploaded into metadata of the process under the service of the registry through api provided by the registry in the micro service system by a data structure of a dictionary and the like for subsequent monitoring modules to read and monitor.
S3, verifying the version number of each logic lower process instance of the micro service through an API interface, and if the verification is passed, judging that the codes are consistent, and if the verification is not passed, giving an alarm; the monitoring service acquires the matedata of all process instances below each logic service through the external API of the eureka, then compares the existing commit-ids, if the existing commit-ids are consistent, the codes of the online services are considered to be consistent, and if the existing commit-ids are not consistent, an alarm is given.
After the reporting is completed, the code versions and the code related information used by all the started process instances are included in the registry cluster. And then, a plurality of instances below the same micro service and versions of all deployment codes below the instances can be obtained through the api interface exposed to the outside by the book center.
An external monitoring program is deployed to execute a timing task through the crontab, the code versions commit-id of the instances are compared, recording can be carried out if inconsistency occurs, and comparison is carried out through a double check mode.
Short inconsistency occurs in the process of rolling release of the micro-service, so that the monitoring program needs to record the duration of inconsistency of a plurality of instances, and if the duration reaches the preset threshold (preset to 10 minutes in the invention), an alarm mechanism is triggered.
The information needed by the alarm can also be notified by mail through the contact in the commit information of git in the registration center.
Through the process deployment, the condition that the instance process codes under the condition that the micro-service has massive nodes are inconsistent can be quickly checked, and the integrity of the distributed instance under the micro-service architecture is ensured.
Metadata information submitted by related code may also be combined with documentation tools, for example: swagger. The commit meta-information of git corresponding to the code can be added and supplemented in the generated interface document meta-data, so that the code version and the code maintainer to which the deployment process belongs can be quickly found out in the development stage.
The invention has the following beneficial effects: by adopting the technical scheme of the invention, the problem of consistency of all process code instances can be realized under the condition of huge scale of micro-service instances, the consistency of logic processing codes of a system is ensured, and the problem that the code consistency of all instance processes can not be quickly positioned under the traditional micro-service architecture is solved. Meanwhile, by means of an external monitoring program, abnormal micro-services can be found quickly, and the problems that troubleshooting and positioning are performed after people find that the logic is inconsistent are solved, and the efficiency is low are solved.
The invention also provides a service node version control device under the micro-service architecture, which comprises a micro-service registration center, a code management module and a monitoring module;
the microservice registration center is used for containing code versions and code related information used by all started process instances;
the code management module is used for compiling and managing codes and submitting the codes to the micro-service registration center;
and the monitoring module is used for detecting and verifying the code version through the API interface code of the micro-service registration center.
In the prior art, service metadata information registered in an eureka registration center only has machine-related information, such as an ip of a machine, a hostname of the machine and the like, and the service process control still has great uncontrollable property, and whether logics of massive process examples under the same logic service are consistent cannot be compared through a ready-made effective method, so that certain difficulty is brought to the discipline problem. Through an automatic monitoring program, potential problems in a large number of service instances can be automatically and timely discovered. Meanwhile, when the service is in problem, the specific code submitting personnel, the code submitting time and the relevant information of the code submission can be located and tracked according to the commit-id of git. The method has the advantages of better tracking the project responsibility system determination and bringing great convenience to the troubleshooting of the problems on the line.
The present invention further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the steps of the service node version control method under the micro service architecture.
The invention also provides a computer terminal, which comprises a memory, a processor and a computer program which is stored in the memory and can run on the processor, wherein the processor realizes the steps of the service node version control method under the micro-service architecture when executing the computer program.
The processor, when executing the computer program, implements the functions of the modules/units in the above-described device embodiments. Illustratively, the computer program may be partitioned into one or more modules/units that are stored in the memory and executed by the processor to implement the invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program in the terminal device.
The computer terminal can be a desktop computer, a notebook, a palm computer, a cloud server and other computing equipment. May include, but is not limited to, a processor, memory. More or fewer components may be included, or certain components may be combined, or different components may be included, such as input-output devices, network access devices, buses, and so forth.
The Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The storage may be an internal storage unit, such as a hard disk or a memory. The memory may also be an external storage device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like. Further, the memory may also include both an internal storage unit and an external storage device. The memory is used for storing the computer program and other programs and data. The memory may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method embodiments may be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (8)
1. A service node version control method under a micro-service architecture is characterized by comprising the following steps:
generating a globally unique version number through code management software;
packing the version number into a micro-service operation directory file, and submitting the directory file to a micro-service registration center;
and verifying the version number of each logic lower process instance of the micro-service through an API (application programming interface), wherein if the verification is passed, the codes are considered to be consistent, and if the verification is not passed, an alarm is given.
2. The method of claim 1, wherein the generating a globally unique version number by code management software comprises:
after the code development of the micro service is completed, code management is carried out through the version control of the git protocol;
each time the code of the micro-service is submitted, commit is done by git's command, which generates a globally unique version number git-commit-id.
3. The service node version control method under micro service architecture as claimed in claim 2, wherein the version number includes commit-id, modification information of code, submission time of code, and related submitter information and other related information.
4. The method for controlling the service node version under the micro-service architecture according to claim 1, wherein the packaging the version number into a directory file and submitting the directory file to the micro-service registry comprises:
in the development process of the micro-service, a project carries out project package management through maven, a standard maven plug-in is introduced through pom.xml, and a command git-commit-id: provision corresponding to git-commit-plug-in is executed through maven;
generating a standard git information maintained file git through the command under the directory of the target;
packaging git.
And uploading the data to metadata of the process of the registry by using the api provided by the microservice registry and the data structure of the dictionary so as to read and monitor the data.
5. The method for controlling the version number of the service node under the micro-service architecture according to claim 1, wherein the verifying the version number of each process instance under the logic of the micro-service via the api interface comprises:
acquiring a plurality of examples under the same micro service and version numbers of all deployment codes through an external API (application program interface) of a micro service registration center;
and deploying an external monitoring program to execute a timing task through the crontab, verifying the commit-id of the code version, recording if the commit-id is inconsistent, and verifying the commit-id in a double check mode.
6. An apparatus applying the service node version control method under the micro-service architecture according to any one of claims 1 to 5, wherein the apparatus comprises a micro-service registry, a code management module and a monitoring module;
the microservice registration center is used for containing code versions and code related information used by all started process instances;
the code management module is used for compiling and managing codes and submitting the codes to the micro-service registration center;
and the monitoring module is used for detecting and verifying the code version through the API interface code of the micro-service registration center.
7. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, which when executed by a processor implements the steps of the service node version control method under micro service architecture according to any of the preceding claims 1-5.
8. A computer terminal, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the service node version control method under micro service architecture according to any one of claims 1 to 5 when executing the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110965957.XA CN113672278B (en) | 2021-08-23 | 2021-08-23 | Service node version control method and device under micro-service architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110965957.XA CN113672278B (en) | 2021-08-23 | 2021-08-23 | Service node version control method and device under micro-service architecture |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113672278A true CN113672278A (en) | 2021-11-19 |
| CN113672278B CN113672278B (en) | 2024-05-10 |
Family
ID=78544886
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110965957.XA Active CN113672278B (en) | 2021-08-23 | 2021-08-23 | Service node version control method and device under micro-service architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113672278B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106610836A (en) * | 2016-12-23 | 2017-05-03 | 国网信息通信产业集团有限公司 | Micro-service operation management tool |
| US20180181312A1 (en) * | 2016-12-22 | 2018-06-28 | Toyota Jidosha Kabushiki Kaisha | Program writing method, control method of apparatus, program for program writing, and control program of apparatus |
| CN110716815A (en) * | 2019-10-11 | 2020-01-21 | 集奥聚合(北京)人工智能科技有限公司 | Spring Gateway-based micro-service each version directional calling method |
| CN111796834A (en) * | 2020-06-30 | 2020-10-20 | 福信富通科技股份有限公司 | Method, device and equipment for deploying combinable micro-service development framework |
| CN111930423A (en) * | 2020-09-17 | 2020-11-13 | 四川新网银行股份有限公司 | Method for tracing software release version based on microservice |
| CN112087327A (en) * | 2020-08-26 | 2020-12-15 | 北京金山云网络技术有限公司 | Information state acquisition method and apparatus, storage medium, and electronic apparatus |
| CN112130880A (en) * | 2020-09-27 | 2020-12-25 | 平安医疗健康管理股份有限公司 | Micro-service publishing method and device, computer equipment and storage medium |
| CN112230987A (en) * | 2020-10-29 | 2021-01-15 | 电信科学技术第五研究所有限公司 | System and method for realizing distributed modular plug-in framework |
| CN112433882A (en) * | 2020-10-30 | 2021-03-02 | 福建福诺移动通信技术有限公司 | Method for recording and recovering micro-service deployment information |
| US20210064360A1 (en) * | 2019-08-27 | 2021-03-04 | Sap Se | Time-dependent activation of configuration content |
| CN112667251A (en) * | 2020-12-29 | 2021-04-16 | 数字广东网络建设有限公司 | Service deployment method, device, computer equipment and storage medium |
| CN113010266A (en) * | 2021-03-17 | 2021-06-22 | 北京金山云网络技术有限公司 | Cloud service restarting method and device |
-
2021
- 2021-08-23 CN CN202110965957.XA patent/CN113672278B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180181312A1 (en) * | 2016-12-22 | 2018-06-28 | Toyota Jidosha Kabushiki Kaisha | Program writing method, control method of apparatus, program for program writing, and control program of apparatus |
| CN106610836A (en) * | 2016-12-23 | 2017-05-03 | 国网信息通信产业集团有限公司 | Micro-service operation management tool |
| US20210064360A1 (en) * | 2019-08-27 | 2021-03-04 | Sap Se | Time-dependent activation of configuration content |
| CN110716815A (en) * | 2019-10-11 | 2020-01-21 | 集奥聚合(北京)人工智能科技有限公司 | Spring Gateway-based micro-service each version directional calling method |
| CN111796834A (en) * | 2020-06-30 | 2020-10-20 | 福信富通科技股份有限公司 | Method, device and equipment for deploying combinable micro-service development framework |
| CN112087327A (en) * | 2020-08-26 | 2020-12-15 | 北京金山云网络技术有限公司 | Information state acquisition method and apparatus, storage medium, and electronic apparatus |
| CN111930423A (en) * | 2020-09-17 | 2020-11-13 | 四川新网银行股份有限公司 | Method for tracing software release version based on microservice |
| CN112130880A (en) * | 2020-09-27 | 2020-12-25 | 平安医疗健康管理股份有限公司 | Micro-service publishing method and device, computer equipment and storage medium |
| CN112230987A (en) * | 2020-10-29 | 2021-01-15 | 电信科学技术第五研究所有限公司 | System and method for realizing distributed modular plug-in framework |
| CN112433882A (en) * | 2020-10-30 | 2021-03-02 | 福建福诺移动通信技术有限公司 | Method for recording and recovering micro-service deployment information |
| CN112667251A (en) * | 2020-12-29 | 2021-04-16 | 数字广东网络建设有限公司 | Service deployment method, device, computer equipment and storage medium |
| CN113010266A (en) * | 2021-03-17 | 2021-06-22 | 北京金山云网络技术有限公司 | Cloud service restarting method and device |
Non-Patent Citations (6)
| Title |
|---|
| L_小乌鸦: "第二篇：SpringCloud 构建微服务系统之服务注册和发现（nacos）", pages 1 - 13, Retrieved from the Internet <URL:https://blog.csdn.net/I_will_try/article/details/90202005> * |
| MYTT_10566: "Maven学习笔记 - git-commit-id-plugin插件", pages 1 - 9, Retrieved from the Internet <URL:https://blog.csdn.net/mytt_10566/article/details/100116670> * |
| YUXING MA: "World of Code: An Infrastructure for Mining the Universe of Open Source VCS Data", 《2019 IEEE/ACM 16TH INTERNATIONAL CONFERENCE ON MINING SOFTWARE REPOSITORIES (MSR)》, pages 143 - 154 * |
| 肖坚: "基于Docker的应用服务云平台的设计和实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》, pages 139 - 99 * |
| 蒋勇;: "基于微服务架构的基础设施设计", 软件, no. 05, pages 93 - 97 * |
| 马长振: "微服务架构协同开发规范与质量管理系统的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》, pages 138 - 357 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113672278B (en) | 2024-05-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111104392B (en) | Database migration method and device, electronic equipment and storage medium | |
| CN111694592A (en) | Management method and system for project version release | |
| CN109445837B (en) | Application program publishing method and device | |
| CN111723313A (en) | Page jump processing method, device, equipment and storage medium | |
| WO2019056475A1 (en) | Automated test task management method and apparatus, device, and storage medium | |
| CN111694612A (en) | Configuration checking method, device, computer system and storage medium | |
| CN111429250A (en) | Data management method and device in escort scene | |
| CN114168421A (en) | Customized code compatibility analysis system and method based on micro-service call chain | |
| CN110377323B (en) | Block chain DAPP management system | |
| CN114996127A (en) | Intelligent test method and system for solid state disk firmware module | |
| CN114816993A (en) | Full link interface test method, system, medium and electronic equipment | |
| CN114528201A (en) | Abnormal code positioning method, device, equipment and medium | |
| CN111176666B (en) | BIOS + ME mirror image refreshing method, system, equipment and readable medium | |
| CN113254326A (en) | Method and system for releasing firmware codes of solid state disk by utilizing Jenkins | |
| CN116599881A (en) | Cloud platform tenant modeling test method, device, equipment and storage medium | |
| CN115357594A (en) | Block chain-based data model updating method and related equipment | |
| CN113672278A (en) | Service node version control method and device under micro-service architecture | |
| CN116360931A (en) | Link tracking method, device, system and storage medium | |
| CN112200536B (en) | Test case monitoring management method, terminal equipment and storage medium | |
| CN114416560A (en) | Program crash analysis aggregation method and system | |
| CN114518899A (en) | Reverse software package tracking management method, system and storage medium | |
| CN114491662A (en) | Block chain-based data asset auditing method, system and equipment | |
| CN114157662A (en) | Cloud platform parameter adaptation method and device, terminal equipment and storage medium | |
| CN113504904A (en) | User-defined function implementation method and device, computer equipment and storage medium | |
| CN111581256A (en) | Interaction method and system for application program of intelligent measurement terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |