CN110740046B - Method and device for analyzing service contract - Google Patents

Method and device for analyzing service contract Download PDF

Info

Publication number
CN110740046B
CN110740046B CN201810789229.6A CN201810789229A CN110740046B CN 110740046 B CN110740046 B CN 110740046B CN 201810789229 A CN201810789229 A CN 201810789229A CN 110740046 B CN110740046 B CN 110740046B
Authority
CN
China
Prior art keywords
service
service contract
contract data
data
instance
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810789229.6A
Other languages
Chinese (zh)
Other versions
CN110740046A (en
Inventor
张晋军
刘海锋
易阳华
丁俊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Jingdong Century Trading Co Ltd
Beijing Jingdong Shangke Information Technology Co Ltd
Original Assignee
Beijing Jingdong Century Trading Co Ltd
Beijing Jingdong Shangke Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Jingdong Century Trading Co Ltd, Beijing Jingdong Shangke Information Technology Co Ltd filed Critical Beijing Jingdong Century Trading Co Ltd
Priority to CN201810789229.6A priority Critical patent/CN110740046B/en
Publication of CN110740046A publication Critical patent/CN110740046A/en
Application granted granted Critical
Publication of CN110740046B publication Critical patent/CN110740046B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50Network service management, e.g. ensuring proper service fulfilment according to agreements

Abstract

The invention discloses a method and a device for analyzing service contracts, and relates to the technical field of computers. One embodiment of the method comprises the following steps: extracting service contract data of a service contract from the running service instance; inquiring the latest service contract data of the service contract in the result set; analyzing the service contract data and the latest service contract data to determine whether the service contract has changed; when the service contract changes, the service contract data is recorded in the result set. The implementation mode can ensure the consistency of the finally obtained service contract data and the actual running condition; and can accurately and efficiently determine whether the service contract has changed.

Description

Method and device for analyzing service contract
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for analyzing a service contract.
Background
With the development of computer technology, microservices are increasingly being used in computer applications. According to the micro-service concept, each micro-service can be independently developed and deployed, and in practical application, a plurality of running examples can exist in each micro-service, so that horizontal expansion and high availability can be achieved.
In general, a plurality of micro services can be set in a computer application according to service boundary division, each micro service has single functional responsibility, and the micro services communicate with each other mainly through an RPC mode or a hypertext transfer protocol (HTTP) mode, and cooperate to complete all functions of the application. RPC is a way of inter-process communication, allowing remote services to be invoked like local services; the HTTP approach is an application layer communication protocol between clients, browsers, other servers, and web servers. The primary service call is composed of two parties (two micro services), the party initiating the call is called a service calling party, and the party called is called a service provider; both parties communicate in accordance with a certain information format, which is called a service contract. The service contract may be updated or changed, and if the service contracts of both parties are different, normal communication is not possible, so that the related parties want to know timely and accurately whether and how the service contract is changed.
In the prior art, how to learn the change of the service contract is as follows:
1. manually recording and arranging service contracts and documents with changed versions, and manually informing related parties. For version change, version information can be added into the service contract, so that manual check is facilitated;
2. Filling in the content of the service contract or importing the existing service contract in a special editor. The editor can export a service contract document, and the editor can manually discover the change of the service contract and inform the relevant party;
3. by means of the annotation mechanism of language, the service provider writes the annotations related to the service contract in the code at proper places, when the application is started, corresponding service contract documents can be automatically generated according to the annotations, at the moment, the service contract is located in the program memory, the service contract documents can be accessed through Uniform Resource Locator (URL) addresses, and the related parties are also manually found out and notified of the changes of the service contract.
In the process of implementing the present invention, the inventor finds that at least the following problems exist in the prior art:
1. the method has the advantages that the method is low in efficiency, easy to make mistakes, inaccurate, untimely in notification or missing in a manner of manually discovering the change of the service contract and manually notifying the related party;
2. the application deployment and release link is not related to the document maintenance link, and the service contract document maintained by the application deployment and release link may not be consistent with the actual running condition.
Disclosure of Invention
In view of this, the embodiment of the invention provides a method and a device for analyzing service contracts, which can ensure the consistency of the finally obtained service contract data and the actual running condition; and can accurately and efficiently determine whether the service contract has changed.
To achieve the above object, according to one aspect of an embodiment of the present invention, there is provided a method of analyzing a service contract.
The method for analyzing the service contract comprises the following steps: extracting service contract data of a service contract from the running service instance; querying the latest service contract data of the service contract in a result set; analyzing the service contract data and the latest service contract data to determine whether the service contract has changed; and when the service contract is changed, recording the service contract data in the result set.
Optionally, the service contract data includes contract content, summary information, a timestamp, an instance identification, a service identification, or a whether identification is processed for the service contract.
Optionally, analyzing the service contract data and the latest service contract data to determine whether the service contract has changed comprises: searching unprocessed service contract data in the service contract data carrying the service identifier based on whether the service identifier is processed or not, and adding the service contract data into a circulation set; traversing whether the service contract data in the circulating set exists in the comparison set; if not, adding the service contract data in the circulation set into the comparison set; if the service contract data in the circulating set is inconsistent with the summary information of the service contract data in the comparing set, adding the service contract data in the circulating set into the comparing set; if the service contract data in the circulation set are consistent, the service contract data in the circulation set are not added into the comparison set; comparing the abstract information of the latest service contract data with the abstract information of the service contract data in the comparison set; if the service contract is inconsistent, the service contract is changed; if so, the service contract is unchanged.
Optionally, the method further comprises: displaying the result set; or comparing any two service contract data of the service contracts in the result set, and displaying the comparison result.
Optionally, before extracting the service contract data from the running service instance, further includes: adding service contract annotations to the service instances; the attributes of the service contract notes comprise annotation description of the method, name of the method, request type of the method and return value of the method.
Optionally, extracting the service contract data from the running service instance includes: analyzing the service contract annotation of the service instance to obtain annotation information; service contract data is extracted based on the annotation information.
Optionally, parsing the service contract annotation of the service instance to obtain annotation information includes: during the operation of the service instance, acquiring the service instance in a push mode or a pull mode, and analyzing the service contract annotation of the service instance to generate annotation information; or acquiring the service instance by adopting a pushing mode or a pulling mode during the deployment of the service instance, detecting the code of the service instance from a code version control system by using an application deployment tool, scanning the code of the service instance to find out the service contract annotation, and analyzing the service contract annotation to generate annotation information.
Optionally, the pulling mode includes: the communication protocol of the service instance is utilized to communicate with the service instance periodically or randomly to obtain the service instance.
Optionally, extracting the service contract data from the running service instance includes: service contract data is extracted from the running service instance using a reflection mechanism.
Optionally, before analyzing the service contract data and the latest service contract data to determine whether the service contract has changed further comprises: and converting the service contract data into a preset format or a preset structure and removing blank parts.
Optionally, recording the service contract data into the result set includes: generating version information for the service contract data; and recording the version information, the contract content, the abstract information, the service identification and the timestamp into the result set.
Optionally, the method further comprises: and when the service contract is changed, the version information, the contract content, the abstract information, the service identification and the time stamp are sent to a service calling party.
Optionally, querying the result set for the latest service contract data for the service contract includes: and inquiring the latest service contract data of the service contract in the result set by utilizing the timestamp.
To achieve the above object, according to still another aspect of an embodiment of the present invention, there is provided an apparatus for analyzing a service contract.
The device for analyzing the service contract comprises the following components: the extraction module is used for extracting service contract data of the service contract from the running service instance; the query module is used for querying the latest service contract data of the service contract in the result set; an analysis module for analyzing the service contract data and the latest service contract data to determine whether the service contract has changed; and the recording module is used for recording the service contract data in the result set when the service contract changes.
Optionally, the service contract data includes contract content, summary information, a timestamp, an instance identification, a service identification, or a whether identification is processed for the service contract.
Optionally, the analysis module is further configured to: searching unprocessed service contract data in the service contract data carrying the service identifier based on whether the service identifier is processed or not, and adding the service contract data into a circulation set; traversing whether the service contract data in the circulating set exists in the comparison set; if not, adding the service contract data in the circulation set into the comparison set; if the service contract data in the circulating set is inconsistent with the summary information of the service contract data in the comparing set, adding the service contract data in the circulating set into the comparing set; if the service contract data in the circulation set are consistent, the service contract data in the circulation set are not added into the comparison set; comparing the abstract information of the latest service contract data with the abstract information of the service contract data in the comparison set; if the service contract is inconsistent, the service contract is changed; if so, the service contract is unchanged.
Optionally, the apparatus further comprises: the display module is used for displaying the result set; or comparing any two service contract data of the service contracts in the result set, and displaying the comparison result.
Optionally, the apparatus further comprises: an adding module, configured to add service contract annotations to the service instances; wherein the attributes of the service contract annotation comprise annotation description of the device, name of the device, request type of the device and return value of the device.
Optionally, the extraction module is further configured to: analyzing the service contract annotation of the service instance to obtain annotation information; service contract data is extracted based on the annotation information.
Optionally, the extraction module is further configured to: during the operation of the service instance, acquiring the service instance in a push mode or a pull mode, and analyzing the service contract annotation of the service instance to generate annotation information; or acquiring the service instance by adopting a pushing mode or a pulling mode during the deployment of the service instance, detecting the code of the service instance from a code version control system by using an application deployment tool, scanning the code of the service instance to find out the service contract annotation, and analyzing the service contract annotation to generate annotation information.
Optionally, the pulling mode includes: the communication protocol of the service instance is utilized to communicate with the service instance periodically or randomly to obtain the service instance.
Optionally, the extraction module is further configured to: service contract data is extracted from the running service instance using a reflection mechanism.
Optionally, the apparatus further comprises: and the conversion module is used for converting the service contract data into a preset format or a preset structure and removing blank parts.
Optionally, the recording module is further configured to: generating version information for the service contract data; and recording the version information, the contract content, the abstract information, the service identification and the timestamp into the result set.
Optionally, the apparatus further comprises: and the sending module is used for sending the version information, the contract content, the abstract information, the service identifier and the timestamp to a service calling party when the service contract is changed.
Optionally, the query module is further configured to: and inquiring the latest service contract data of the service contract in the result set by utilizing the timestamp.
To achieve the above object, according to still another aspect of an embodiment of the present invention, there is provided an electronic device that analyzes a service contract.
An electronic device for analyzing a service contract according to an embodiment of the present invention includes: one or more processors; and the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors are enabled to realize a method for analyzing service contracts.
To achieve the above object, according to still another aspect of the embodiments of the present invention, there is provided a computer-readable storage medium.
A computer readable storage medium of an embodiment of the present invention has stored thereon a computer program which, when executed by a processor, implements a method of analyzing a service contract of an embodiment of the present invention.
One embodiment of the above invention has the following advantages or benefits: because the service contract data is adopted, which extracts the service contract from the running service instance; inquiring the latest service contract data of the service contract in the result set; analyzing the service contract data and the latest service contract data to determine whether the service contract has changed; when the service contract changes, the technical means of recording the service contract data in the result set overcomes the defect that the maintained service contract document possibly does not accord with the actual running condition; the method has the technical problems of low efficiency, easy error, inaccuracy and untimely notification or omission, and further achieves the purpose of ensuring the consistency of the finally obtained service contract data and the actual running condition; whether the service contract changes or not can be accurately and efficiently determined, and the technical effect of the related party can be timely notified.
Further effects of the above-described non-conventional alternatives are described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of the main steps of a method of analyzing a service contract according to an embodiment of the invention;
FIG. 2 is a schematic diagram of the main flow of a method of analyzing a service contract according to one referenceable embodiment of the invention;
FIG. 3 is a schematic diagram of the main flow of extracting service contract data according to one referenceable embodiment of the invention;
FIG. 4 is a schematic diagram of the main flow of extracting service contract data according to another referenceable embodiment of the invention;
FIG. 5 is a schematic diagram of the main flow of analyzing service contract data according to one referenceable embodiment of the invention;
FIG. 6 is a schematic diagram of the main modules of an apparatus for analyzing a service contract according to an embodiment of the invention;
FIG. 7 is an exemplary system architecture diagram in which embodiments of the present invention may be applied;
fig. 8 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It should be noted that the embodiments of the present invention and the technical features in the embodiments may be combined with each other without collision.
The communication method between the micro services is to communicate by using an RPC method or an HTTP method based on a certain service contract. For the RPC scheme, the two parties need to acquire the following: interface name, method name, in-and out-of-parameters of each method, which fields the in-parameters include and types of fields, which fields the out-parameters include and types of fields, wherein if a field is an object type, the field type inside needs to be known. For the HTTP scheme, the two parties need to acquire the following: a fixed portion in the URL and a variable portion in the URL, wherein each function corresponds to one URL.
In practical applications, the service contracts of all running instances of a micro service may not be completely consistent, and the reason for this phenomenon is many, and it may be that the user divides the running instances into two groups, one group running according to one service contract, and the other group running according to another service contract; it is also possible that the service contract changes due to changes in business logic, etc. The stable content after each change of the service contract is called a version, multiple versions are generated by multiple changes of the service contract, and multiple versions can be simultaneously operated in an online environment.
It is obvious that a service contract may fail to be invoked when it is changed without the knowledge of the service caller, and it may take a lot of time to solve the cause of the invocation failure. It is also necessary for the demand investigation phase to keep track of the exact details of the service contract, which otherwise cannot be done in the encoding phase.
Therefore, in any situation, it is highly desirable for the service caller to be able to know timely and accurately whether and how the service contract changes; for service providers, it is desirable to have a method to assist them in maintaining service contracts and changes, and preferably to automatically notify service invokers, saving time and effort.
Fig. 1 is a schematic diagram of the main steps of a method of analyzing a service contract according to an embodiment of the invention.
As shown in fig. 1, the method for analyzing a service contract according to an embodiment of the present invention mainly includes the following steps:
step S101: service contract data for a service contract is extracted from the running service instance.
In the prior art, the application deployment and release link is not related to the document maintenance link, and the service contract document maintained may not be in accordance with the actual running condition. Therefore, the embodiment of the invention provides that the service contract data of the used service contract is extracted from the running service instance, thereby ensuring the effectiveness of the service contract and finding the change of the service contract in time.
When extracting service contract data of a service contract, the service contract data may be extracted from all running service instances, or may be extracted from only one or more specified running service instances.
In embodiments of the present invention, the service contract data may include contract content, summary information, time stamps, instance identifications, service identifications, or whether to process identifications of the service contract. Wherein, the contract content refers to specific content of the service contract, which can be in the form of an original character string (original_json); the summary information refers to the summary of the contract content, and can be represented by MD5, hash value, and the like; the timestamp may be a version of the service contract generation time; the instance identity is an identity of the service instance; the service identifier is used for indicating what communication mode is adopted between the service provider and the service caller, if the service identifier is in the RPC mode, the interface name is the service identifier, and if the service identifier is in the HTTP mode, the service identifier is the URL; whether or not the processing flag is used to indicate whether or not the service contract data has been processed (i.e., whether or not the service contract data has been analyzed).
Taking table 1 as an example to describe service contract data, service_id represents a service identifier; the handle_flag indicates whether to process the flag; instance_id represents an instance identifier; digest represents summary information; timestamp represents a timestamp; original_json represents contract content. The service instance com.jd.server1 has a total of four service contract data, wherein the summary information of the first and fourth service instances are the same, but come from different service instances; likewise, the second and third summary information are the same and come from different service instances, which means that the service instance "com.jd.server1" is in an online environment, there are two different service contract formats, whose summary information is xxxxx1 and xxxxx2, respectively.
TABLE 1
Md5 is a technology of information summarization, and after Md5 processes, a string with a fixed length (i.e. summary information) will be output no matter how long the string information is input, the same output summary must be output when the same string is input, and different output summaries must be output when different strings are input. Note that the probability of occurrence of "different inputs" producing "the same output" is one-fourth of 16 to 32, so it can be considered that it is almost impossible to occur.
Service contract data may be extracted from the service instance by way of annotations. In the embodiment of the invention, before the service contract data is extracted from the running service instance, the service contract annotation can be added to the service instance. The attributes of the service contract annotations include, among other things, the annotation description of the method, the name of the method, the request type of the method (e.g., "POST," "GET," etc.), and the return value of the method.
For example, add service contract notes to the method of the service instance:
"@ ApiOperation (value=" third party added album ", httpmethod=" POST ", response = basevo. Class, notes=" third party added album ")"; and
adding service contract annotations to parameters of the service instance:
"@ apiModelProperty (value=" album name ", required=true)
private String name;
apiModelProperty (value= "third party album Id", required = true)
private String thirdAlbumId; third party album Id
apiModelProperty (value= "third party album Id", required = true)
private String thirdSystemId; the// third party system Id).
Note that in the above example, the notes indicating the method, the value indicating the name of the method, the httpMethod indicating the request type of the method, and the response indicating the return value of the method, the required indicating that this attribute is necessary and cannot be null.
Specifically, extracting service contract data from a service instance by way of annotation may be achieved by: analyzing service contract annotation of the service instance to obtain annotation information; service contract data is extracted based on the annotation information. Parsing the service contract annotation can result in annotation information that includes basic information of the service contract, such that service contract data can be obtained based on the annotation information.
In the embodiment of the invention, the annotation information obtained by analyzing the service contract annotation of the service instance can be realized by the following two modes: acquiring the service instance by adopting a pushing mode or a pulling mode during the operation of the service instance, and analyzing the service contract annotation of the service instance to generate annotation information; or, during the deployment of the service instance, the service instance is acquired in a push mode or a pull mode, the code of the service instance is detected from the code version control system by using an application deployment tool, the code of the service instance is scanned to find service contract annotation, and the service contract annotation is analyzed to generate annotation information.
The service contract notes two ways of use, the first during service instance deployment and the second during service instance operation, the effects of which are the same. For the first approach, many companies now use application deployment tools that can retrieve a specified version of code from a code version control system, compile and build it, package it into an executable binary software package, and then distribute it to a host, such as a physical machine, virtual machine, or container. After the code is detected, a step can be inserted to scan the code according to annotation grammar, find out all service contract annotations and analyze to generate annotation information. For the second mode, the analysis of service contract annotation can be completed by using the support of the program language to the annotation mechanism, and annotation information is generated.
The mode of actively transmitting data by the service instance is called a push mode; the manner in which data is acquired by communication is referred to as a "pull mode". In the embodiment of the invention, the pulling mode comprises the following steps: the service instance is obtained by periodically or randomly communicating with the service instance using a communication protocol of the service instance.
It should be noted that, the manner of acquiring the service instance by using random communication can reduce the traffic.
In addition, service contract data can be derived from the running service instance using a reflection mechanism of the programming language (e.g., java). In the embodiment of the invention, the extraction of the service contract data from the running service instance can be realized by the following ways: service contract data is extracted from the running service instance using a reflection mechanism.
The reflection mechanism is that in the running state, for any one class, all the attributes and methods of the class can be known; any method and attribute of any object can be invoked; i.e. the information can be obtained dynamically and the object method can be invoked dynamically. The reflection mechanism is a part of the running time of the program language system, can easily acquire the interface name of the service, the method name of the service and the in-out parameters of each method, and can also recursively know the information of the fields of each parameter until the atom type. However, the reflection mechanism can only be used in RPC mode.
In the embodiment of the invention, before whether the service contract is changed or not is analyzed based on the latest service contract data, the service contract data can be converted into a preset format or a preset structure and blank parts can be removed.
The method reduces the storage size of the service contract and avoids the error of analysis of the next link caused by different spaces of the same content. In addition, the preset format or preset structure may be defined by the service provider, and the service caller adheres to the convention and uses the preset format or preset structure.
Such as service contract data:
after the blank portion is removed:
“{“Service_name”:“com.xxx.yyy.zzz”,“Methods”:[{“name”:“xxx_method”,“in_parameters”:[{“type”:“string”}].“out_parameters”:[{“type”:“ref_type1”}]}],“ref_type1”:{“field1”:“xxx”,“field2”:“yyy”}}”。
step S102: and inquiring the latest service contract data of the service contract in the result set.
In general, each service contract corresponds to a plurality of service contract data, one service contract data corresponds to one version of service contract, and in the prior art, all service contract data of each service contract are maintained independently, are not stored and managed in a centralized way, and are inconvenient for later inquiry and analysis. The embodiment of the invention adopts a centralized storage and management mode to record the service contract data corresponding to the same service contract in the result set, so that whether the service contract data are changed or not can be quickly found. The latest service contract data of the service contract is the recorded service contract of the latest version.
Since the service contract data includes a time stamp, it can be determined which service contract data is newly recorded based on the time stamp. In the embodiment of the present invention, step S102 may be implemented by: the latest service contract data of the service contract is queried in the result set by means of the time stamp.
Step S103: the service contract data and the latest service contract data are analyzed to determine if the service contract has changed.
After the service contract data and the latest service contract data are obtained in step S101 and step S102, the service contract data and the latest service contract data are analyzed, so that whether the service contract is changed or not can be accurately and efficiently determined, for example, the service contract data and the latest service contract data are directly compared.
Whether the service contract is changed or not can be determined by the service identification of the service contract, whether the service contract data such as identification, abstract information and the like is processed or not, and filtering and analyzing can be performed when a plurality of service contract data are processed simultaneously. In the embodiment of the present invention, step S103 may be implemented by: searching unprocessed service contract data in the service contract data carrying the service identifier based on whether the service identifier is processed or not, and adding the service contract data into a circulation set; traversing whether service contract data in the cyclic set exists in the comparison set; if not, adding the service contract data in the circulation set into the comparison set; if the service contract data in the circulating set is inconsistent with the summary information of the service contract data in the comparing set, the service contract data in the circulating set is added into the comparing set; if the service contract data in the circulating set are consistent, the service contract data in the circulating set are not added into the comparison set; comparing the abstract information of the latest service contract data with the abstract information of the service contract data in the comparison set; if the service contract is inconsistent, the service contract is changed; if so, the service contract is unchanged.
The service contract data can be filtered through the service identification and whether the service identification is processed or not, and the service contract data which is analyzed is removed, so that the calculated amount is reduced, and the calculation resources are released. Further, since the digest information is a digest of the contract content and can represent the contract content, the calculation amount can be further reduced by merely comparing the digest information.
Step S104: when the service contract changes, the service contract data is recorded in the result set.
It may be determined whether the service contract has changed or not in step S103, and if not, no further processing is required, and if so, service contract data, that is, service contract data representing the latest version, may be recorded in the result set.
In the embodiment of the invention, the recording of the service contract data in the result set can be realized by the following ways: generating version information for the service contract data; the contract content, summary information, version information, service identification, and time stamp are recorded into a result set. That is, the result set may record information such as specific content of the service contract, a summary of the contract content, a version corresponding to the contract content, what communication method is used between the service provider and the service caller, and the time of generating the service contract of the version. The version information can be generated based on rules established in the system, so that the comparison accords with the common understanding of the version by people, and the version information is convenient for communication and use.
Taking table 2 as an example to illustrate the result set, service_id represents a service identifier; version represents version information; digest represents summary information; timestamp represents a timestamp; original_json represents contract content. The service instance "com.jd.server1" has two records in the result set, the corresponding summary information is different, and the summary information of V1.1 is: xxxxxx1, xxxxxx2, and the abstract information of V1.2 is xxxx1, xxxx3.
TABLE 2
The method for analyzing the service contract according to the embodiment of the invention can further comprise the following steps: displaying a result set; or comparing any two service contract data of the service contracts in the result set, and displaying the comparison result.
And the service contracts of all versions are completely reserved, so that the transition of the service contracts can be conveniently known and the problem can be conveniently examined. For example, the call fails on the current version, but the last version is successful, and by comparing the differences of the two versions, the problem can be found quickly. In addition, during display, the format of the displayed data can be changed, and the format conforming to reading habit is adopted.
Due to the manual discovery of changes in service contracts and the manual notification of interested parties, the system is inefficient, prone to error, inaccurate, and timely or missing notifications. Therefore, the embodiment of the invention provides that when the service contract is changed, the version information, the contract content, the abstract information, the service identifier and the time stamp can be sent to the service calling party.
The method for analyzing the service contract according to the embodiment of the invention can be seen in that the service contract data of the service contract is extracted from the running service instance; inquiring the latest service contract data of the service contract in the result set; analyzing the service contract data and the latest service contract data to determine whether the service contract has changed; when the service contract changes, the technical means of recording the service contract data in the result set overcomes the defect that the maintained service contract document possibly does not accord with the actual running condition; the method has the technical problems of low efficiency, easy error, inaccuracy and untimely notification or omission, and further achieves the purpose of ensuring the consistency of the finally obtained service contract data and the actual running condition; whether the service contract changes or not can be accurately and efficiently determined, and the technical effect of the related party can be timely notified.
Fig. 2 is a schematic diagram of the main flow of a method of analyzing a service contract according to one referenceable embodiment of the invention.
As shown in fig. 2, the method for analyzing a service contract according to the embodiment of the present invention is mainly divided into two parts, namely, service contract data collection and service contract analysis, specifically:
regarding service contract data collection, there are various ways to extract the original data of the service contract (i.e., the service contract data), and these ways can be used to obtain this data, but these ways all have the same starting point: the data is acquired from the service instance of actual operation, so that the consistency of the finally obtained service contract data and the actual operation condition can be ensured. May be extracted from all running service instances or may be extracted from only one or more designated running service instances.
The service contract data of the service contract can be extracted from the service instance in a annotating manner or obtained from the running service instance by using a reflection mechanism of a programming language.
The service contract data may include contract content, summary information, time stamps, instance identifications, service identifications, or whether to process identifications, etc. of the service contract. The collected service contract data can be stored in a certain storage, such as cloud storage, a relational database, a non-relational database and other storage products, and is called from the storage during analysis; or can send to the message queue, draw the service contract data from the message queue while analyzing; or directly transmitted to a place for analyzing service contract data through an RPC mode or an HTTP mode, such as an analysis server or an analysis platform.
Regarding service contract analysis, i.e. analyzing whether a service contract has changed, specific content of the service contract can be analyzed from the service contract data, and whether the service contract has changed can be determined; and stores the analysis results in some storage, such as cloud storage, relational databases, or non-relational databases, and the like. When a change in the service contract is analyzed, the service contract data may be recorded in the result set, and the interested party (the service invoker and the service provider) may also be notified directly, and how to change, for example, the service contract data is sent to the service invoker.
It should be noted that whether or not a service contract is changed may be determined by the service identifier of the service contract, whether or not service contract data such as the identifier and abstract information is processed, and when a plurality of service contract data are processed at the same time, filtering and re-analysis may be performed first.
In addition, for the result of the service contract analysis, the result set can be displayed, namely, the service contract content is read from the result set, and is viewed by other people in a format conforming to the reading habit, so that the detailed content of all versions of the service contract is displayed. The comparison of any two version differences can be displayed, namely, any two service contract data of the service contracts in the comparison result set are displayed, and the comparison result is displayed.
The result set may record information such as specific content of the service contract, an abstract of the contract content, a version corresponding to the contract content, what communication method is adopted between the service provider and the service caller, and a service contract generation time of the version. Version information, contract content, summary information, service identification and time stamp may also be sent to the service invoker when the service contract changes.
Fig. 3 is a schematic diagram of a main flow of extracting service contract data according to a referenceable embodiment of the invention.
As shown in fig. 3, the extraction of service contract data may be implemented in a manner of service contract annotation, specifically:
1. the service contract collector may be used to collect service contract annotations for the running service instance, parse the service contract annotations to generate annotation information:
the service contract collector acquires the service instance in a pushing mode or a pulling mode during the operation of the service instance, analyzes the service contract annotation and generates annotation information;
or, during the deployment of the service instance, acquiring the service instance in a pushing mode or a pulling mode, detecting the code of the service instance from the code version control system by using an application deployment tool, scanning the code of the service instance to find out service contract annotation, and analyzing the service contract annotation by a service contract collector to generate annotation information;
2. the raw data (i.e., service contract data) is extracted based on the annotation information.
Fig. 4 is a schematic diagram of a main flow of extracting service contract data according to another referenceable embodiment of the invention.
As shown in fig. 4, the extraction of service contract data may be implemented using a reflection mechanism, specifically:
the reflection mechanism is utilized to extract the original data (i.e., service contract data) from the running service instance.
It should be noted that the reflection mechanism can only be applied to a scenario where communication is performed by adopting the RPC method.
Fig. 5 is a schematic diagram of the main flow of analyzing service contract data according to one referenceable embodiment of the invention.
As shown in fig. 5, the main flow of analyzing service contract data includes:
step S501: service contract data carrying service identification is found out from the original data:
the original data is all the service contract data.
Step S502: adding unanalyzed service contract data to the recurring collection:
among the service contract data carrying the service identification, the service contract data which is not processed (i.e. has not been analyzed) is searched for based on whether the service identification is processed, and the loop set is added.
Step S503: whether the service contract data in the traversal cycle set exists in the comparison set or not, and if not, executing step S504; if so, step S505 is performed:
the comparison set is used for storing service contract data which has service identification and is not analyzed.
Step S504: and adding the service contract data in the circulation set into the comparison set.
Step S505: comparing the summary information of the service contract data in the cyclic set with the summary information of the service contract data in the cyclic set, and if not, executing step S504; if so, step S506 is performed.
Step S506: ending the analysis of the service contract data:
service contract data in the loop set is not added to the comparison set.
Step S507: comparing the abstract information of the latest service contract data with the abstract information of the service contract data in the comparison set; if the service contract is inconsistent, the service contract is changed; if so, the service contract is unchanged.
Fig. 6 is a schematic diagram of main modules of an apparatus for analyzing a service contract according to an embodiment of the present invention.
As shown in fig. 6, an apparatus 600 for analyzing a service contract according to an embodiment of the present invention includes: an extraction module 601, a query module 602, an analysis module 603 and a recording module 604.
Wherein, the liquid crystal display device comprises a liquid crystal display device,
an extracting module 601, configured to extract service contract data of a service contract from an operating service instance;
a query module 602, configured to query the result set for the latest service contract data of the service contract;
an analysis module 603 for analyzing the service contract data and the latest service contract data to determine whether the service contract has changed;
a recording module 604, configured to record the service contract data in the result set when the service contract changes.
Further, the service contract data may include contract content, summary information, a timestamp, an instance identification, a service identification, or a whether an identification was processed for the service contract.
In an embodiment of the present invention, the analysis module 603 may further be configured to: searching unprocessed service contract data in the service contract data carrying the service identifier based on whether the service identifier is processed or not, and adding the service contract data into a circulation set; traversing whether the service contract data in the circulating set exists in the comparison set; if not, adding the service contract data in the circulation set into the comparison set; if the service contract data in the circulating set is inconsistent with the summary information of the service contract data in the comparing set, adding the service contract data in the circulating set into the comparing set; if the service contract data in the circulation set are consistent, the service contract data in the circulation set are not added into the comparison set; comparing the abstract information of the latest service contract data with the abstract information of the service contract data in the comparison set; if the service contract is inconsistent, the service contract is changed; if so, the service contract is unchanged.
In an embodiment of the present invention, the apparatus may further include: a display module (not shown) for displaying the result set; or comparing any two service contract data of the service contracts in the result set, and displaying the comparison result.
In an embodiment of the present invention, the apparatus may further include: an adding module (not shown in the figure) for adding service contract annotations to the service instances; wherein the attributes of the service contract annotation comprise annotation description of the device, name of the device, request type of the device and return value of the device.
In an embodiment of the present invention, the extraction module 601 may further be configured to: analyzing the service contract annotation of the service instance to obtain annotation information; service contract data is extracted based on the annotation information.
In an embodiment of the present invention, the extracting module 601 may further be configured to: during the operation of the service instance, acquiring the service instance in a push mode or a pull mode, and analyzing the service contract annotation of the service instance to generate annotation information; or acquiring the service instance by adopting a pushing mode or a pulling mode during the deployment of the service instance, detecting the code of the service instance from a code version control system by using an application deployment tool, scanning the code of the service instance to find out the service contract annotation, and analyzing the service contract annotation to generate annotation information.
Furthermore, the pull mode includes: the communication protocol of the service instance is utilized to communicate with the service instance periodically or randomly to obtain the service instance.
In an embodiment of the present invention, the extraction module 601 may further be configured to: service contract data is extracted from the running service instance using a reflection mechanism.
In an embodiment of the present invention, the apparatus may further include: a conversion module (not shown in the figure) is configured to convert the service contract data into a preset format or a preset structure and remove a blank portion.
In an embodiment of the present invention, the recording module 604 may further be configured to: generating version information for the service contract data; and recording the version information, the contract content, the abstract information, the service identification and the timestamp into the result set.
In an embodiment of the present invention, the apparatus may further include: a sending module (not shown in the figure) is configured to send the version information, the contract content, the summary information, the service identifier and the timestamp to a service caller when the service contract changes.
In an embodiment of the present invention, the query module 602 may also be configured to: and inquiring the latest service contract data of the service contract in the result set by utilizing the timestamp.
The device for analyzing the service contract according to the embodiment of the invention can be seen in that the service contract data of the service contract is extracted from the running service instance; inquiring the latest service contract data of the service contract in the result set; analyzing the service contract data and the latest service contract data to determine whether the service contract has changed; when the service contract changes, the technical means of recording the service contract data in the result set overcomes the defect that the maintained service contract document possibly does not accord with the actual running condition; the method has the technical problems of low efficiency, easy error, inaccuracy and untimely notification or omission, and further achieves the purpose of ensuring the consistency of the finally obtained service contract data and the actual running condition; whether the service contract changes or not can be accurately and efficiently determined, and the technical effect of the related party can be timely notified.
Fig. 7 illustrates an exemplary system architecture 700 of a method of analyzing a service contract or an apparatus of analyzing a service contract to which embodiments of the invention may be applied.
As shown in fig. 7, a system architecture 700 may include terminal devices 701, 702, 703, a network 704, and a server 705. The network 704 is the medium used to provide communication links between the terminal devices 701, 702, 703 and the server 705. The network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server 705 via the network 704 using the terminal devices 701, 702, 703 to receive or send messages or the like. Various communication client applications, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc., may be installed on the terminal devices 701, 702, 703.
The terminal devices 701, 702, 703 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 705 may be a server providing various services, such as a background management server providing support for shopping-type websites browsed by the user using the terminal devices 701, 702, 703. The background management server can analyze and other processing on the received data such as the product information inquiry request and the like, and feed back processing results (such as target push information and product information) to the terminal equipment.
It should be noted that, the method for analyzing a service contract provided by the embodiment of the present invention is generally performed by the server 705, and accordingly, the device for analyzing the service contract is generally disposed in the server 705.
It should be understood that the number of terminal devices, networks and servers in fig. 7 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 8, there is illustrated a schematic diagram of a computer system 800 suitable for use in implementing an embodiment of the present invention. The terminal device shown in fig. 8 is only an example, and should not impose any limitation on the functions and the scope of use of the embodiment of the present invention.
As shown in fig. 8, the computer system 800 includes a Central Processing Unit (CPU) 801 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the system 800 are also stored. The CPU 801, ROM 802, and RAM 803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to the bus 804.
The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, mouse, etc.; an output portion 807 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 808 including a hard disk or the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. The drive 810 is also connected to the I/O interface 805 as needed. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as needed so that a computer program read out therefrom is mounted into the storage section 808 as needed.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section 809, and/or installed from the removable media 811. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 801.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules involved in the embodiments of the present invention may be implemented in software or in hardware. The described modules may also be provided in a processor, for example, as: a processor includes an extraction module, a query module, an analysis module, and a recording module. Where the names of the modules do not constitute a limitation of the module itself in some cases, for example, a query module may also be described as "a module that queries the result set for the latest service contract data for the service contract".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to include: step S101: extracting service contract data of a service contract from the running service instance; step S102: inquiring the latest service contract data of the service contract in the result set; step S103: analyzing the service contract data and the latest service contract data to determine whether the service contract has changed; step S104: when the service contract changes, the service contract data is recorded in the result set.
According to the technical scheme of the embodiment of the invention, the service contract data of the service contract is extracted from the running service instance; inquiring the latest service contract data of the service contract in the result set; analyzing the service contract data and the latest service contract data to determine whether the service contract has changed; when the service contract changes, the technical means of recording the service contract data in the result set overcomes the defect that the maintained service contract document possibly does not accord with the actual running condition; the method has the technical problems of low efficiency, easy error, inaccuracy and untimely notification or omission, and further achieves the purpose of ensuring the consistency of the finally obtained service contract data and the actual running condition; whether the service contract changes or not can be accurately and efficiently determined, and the technical effect of the related party can be timely notified.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims (28)

1. A method of analyzing a service contract, comprising:
extracting service contract data of a service contract from the running service instance;
querying the latest service contract data of the service contract in a result set;
analyzing the service contract data and the up-to-date service contract data to determine whether the service contract has changed, comprising: searching unprocessed service contract data in the service contract data carrying the service identifier based on whether the service identifier is processed or not, and adding the service contract data into a circulation set; determining whether the service contract changes by traversing whether service contract data in the cyclic set exists in a comparison set;
and when the service contract is changed, recording the service contract data in the result set.
2. The method of claim 1, wherein the service contract data includes contract content, summary information, a timestamp, an instance identification, a service identification, or a process identification of the service contract.
3. The method of claim 2, wherein determining whether the service contract has changed by traversing whether service contract data in the recurring set exists in the comparison set comprises:
traversing whether the service contract data in the circulating set exists in the comparison set;
if not, adding the service contract data in the circulation set into the comparison set;
if the service contract data in the circulating set is inconsistent with the summary information of the service contract data in the comparing set, adding the service contract data in the circulating set into the comparing set; if the service contract data in the circulation set are consistent, the service contract data in the circulation set are not added into the comparison set;
comparing the abstract information of the latest service contract data with the abstract information of the service contract data in the comparison set; if the service contract is inconsistent, the service contract is changed; if so, the service contract is unchanged.
4. The method according to claim 1, wherein the method further comprises:
displaying the result set; or (b)
And comparing any two service contract data of the service contracts in the result set, and displaying the comparison result.
5. The method of claim 1, further comprising, prior to extracting service contract data from the running service instance:
adding service contract annotations to the service instances; the attributes of the service contract notes comprise annotation description of the method, name of the method, request type of the method and return value of the method.
6. The method of claim 5, wherein extracting service contract data from the running service instance comprises:
analyzing the service contract annotation of the service instance to obtain annotation information;
service contract data is extracted based on the annotation information.
7. The method of claim 6, wherein parsing the service contract annotation for the service instance to obtain annotation information comprises:
during the operation of the service instance, acquiring the service instance in a push mode or a pull mode, and analyzing the service contract annotation of the service instance to generate annotation information; or (b)
And acquiring the service instance by adopting a pushing mode or a pulling mode during the deployment of the service instance, detecting the code of the service instance from a code version control system by using an application deployment tool, scanning the code of the service instance to find out the service contract annotation, and analyzing the service contract annotation to generate annotation information.
8. The method of claim 7, wherein the pulling means comprises: the communication protocol of the service instance is utilized to communicate with the service instance periodically or randomly to obtain the service instance.
9. The method of claim 1, wherein extracting service contract data from the running service instance comprises:
service contract data is extracted from the running service instance using a reflection mechanism.
10. The method of claim 1, wherein analyzing the service contract data and the updated service contract data to determine whether the service contract has changed further comprises:
and converting the service contract data into a preset format or a preset structure and removing blank parts.
11. The method of claim 2, wherein recording the service contract data into the result set comprises:
Generating version information for the service contract data;
and recording the version information, the contract content, the abstract information, the service identification and the timestamp into the result set.
12. The method of claim 11, wherein the method further comprises:
and when the service contract is changed, the version information, the contract content, the abstract information, the service identification and the time stamp are sent to a service calling party.
13. The method of claim 2, wherein querying the result set for the latest service contract data for the service contract comprises:
and inquiring the latest service contract data of the service contract in the result set by utilizing the timestamp.
14. An apparatus for analyzing a service contract, comprising:
the extraction module is used for extracting service contract data of the service contract from the running service instance;
the query module is used for querying the latest service contract data of the service contract in the result set;
an analysis module for analyzing the service contract data and the latest service contract data to determine whether the service contract has changed, comprising: searching unprocessed service contract data in the service contract data carrying the service identifier based on whether the service identifier is processed or not, and adding the service contract data into a circulation set; determining whether the service contract changes by traversing whether service contract data in the cyclic set exists in a comparison set;
And the recording module is used for recording the service contract data in the result set when the service contract changes.
15. The apparatus of claim 14, wherein the service contract data comprises contract content, summary information, a timestamp, an instance identification, a service identification, or a process identification of the service contract.
16. The apparatus of claim 15, wherein the analysis module is further configured to:
traversing whether the service contract data in the circulating set exists in the comparison set;
if not, adding the service contract data in the circulation set into the comparison set;
if the service contract data in the circulating set is inconsistent with the summary information of the service contract data in the comparing set, adding the service contract data in the circulating set into the comparing set; if the service contract data in the circulation set are consistent, the service contract data in the circulation set are not added into the comparison set;
comparing the abstract information of the latest service contract data with the abstract information of the service contract data in the comparison set; if the service contract is inconsistent, the service contract is changed; if so, the service contract is unchanged.
17. The apparatus of claim 14, wherein the apparatus further comprises:
the display module is used for displaying the result set; or comparing any two service contract data of the service contracts in the result set, and displaying the comparison result.
18. The apparatus of claim 14, wherein the apparatus further comprises:
an adding module, configured to add service contract annotations to the service instances; wherein the attributes of the service contract annotation comprise annotation description of the device, name of the device, request type of the device and return value of the device.
19. The apparatus of claim 18, wherein the extraction module is further configured to:
analyzing the service contract annotation of the service instance to obtain annotation information;
service contract data is extracted based on the annotation information.
20. The apparatus of claim 19, wherein the extraction module is further to:
during the operation of the service instance, acquiring the service instance in a push mode or a pull mode, and analyzing the service contract annotation of the service instance to generate annotation information; or (b)
And acquiring the service instance by adopting a pushing mode or a pulling mode during the deployment of the service instance, detecting the code of the service instance from a code version control system by using an application deployment tool, scanning the code of the service instance to find out the service contract annotation, and analyzing the service contract annotation to generate annotation information.
21. The apparatus of claim 20, wherein the pull mode comprises: the communication protocol of the service instance is utilized to communicate with the service instance periodically or randomly to obtain the service instance.
22. The apparatus of claim 14, wherein the extraction module is further configured to:
service contract data is extracted from the running service instance using a reflection mechanism.
23. The apparatus of claim 14, wherein the apparatus further comprises:
and the conversion module is used for converting the service contract data into a preset format or a preset structure and removing blank parts.
24. The apparatus of claim 15, wherein the recording module is further configured to:
generating version information for the service contract data;
and recording the version information, the contract content, the abstract information, the service identification and the timestamp into the result set.
25. The apparatus of claim 24, wherein the apparatus further comprises:
and the sending module is used for sending the version information, the contract content, the abstract information, the service identifier and the timestamp to a service calling party when the service contract is changed.
26. The apparatus of claim 15, wherein the query module is further configured to:
and inquiring the latest service contract data of the service contract in the result set by utilizing the timestamp.
27. An electronic device for analyzing a service contract, comprising:
one or more processors;
storage means for storing one or more programs,
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-13.
28. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-13.
CN201810789229.6A 2018-07-18 2018-07-18 Method and device for analyzing service contract Active CN110740046B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810789229.6A CN110740046B (en) 2018-07-18 2018-07-18 Method and device for analyzing service contract

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810789229.6A CN110740046B (en) 2018-07-18 2018-07-18 Method and device for analyzing service contract

Publications (2)

Publication Number Publication Date
CN110740046A CN110740046A (en) 2020-01-31
CN110740046B true CN110740046B (en) 2023-08-08

Family

ID=69234361

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810789229.6A Active CN110740046B (en) 2018-07-18 2018-07-18 Method and device for analyzing service contract

Country Status (1)

Country Link
CN (1) CN110740046B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113434175B (en) * 2021-06-29 2024-02-27 平安科技(深圳)有限公司 Data processing method, device, storage medium and equipment

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101331478A (en) * 2005-12-15 2008-12-24 微软公司 Conforming web services to an updated contract
CN101364236A (en) * 2008-09-18 2009-02-11 中兴通讯股份有限公司 Data processing apparatus and processing method of WEB page
CN105959138A (en) * 2016-04-29 2016-09-21 深圳前海大数点科技有限公司 Micro-service dynamic disposition system and method based on cloud calculation
CN106506605A (en) * 2016-10-14 2017-03-15 华南理工大学 A kind of SaaS application construction methods based on micro services framework
CN107277086A (en) * 2016-04-06 2017-10-20 阿里巴巴集团控股有限公司 Transaction processing system, method for processing business and service updating method
CN107317830A (en) * 2016-04-26 2017-11-03 中兴通讯股份有限公司 A kind of processing method and processing device of service discovery
CN107911430A (en) * 2017-11-06 2018-04-13 上海电机学院 A kind of micro services infrastructure equipment

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040019669A1 (en) * 2002-07-25 2004-01-29 Sridatta Viswanath Event notification in an administration framework for server systems

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101331478A (en) * 2005-12-15 2008-12-24 微软公司 Conforming web services to an updated contract
CN101364236A (en) * 2008-09-18 2009-02-11 中兴通讯股份有限公司 Data processing apparatus and processing method of WEB page
CN107277086A (en) * 2016-04-06 2017-10-20 阿里巴巴集团控股有限公司 Transaction processing system, method for processing business and service updating method
CN107317830A (en) * 2016-04-26 2017-11-03 中兴通讯股份有限公司 A kind of processing method and processing device of service discovery
CN105959138A (en) * 2016-04-29 2016-09-21 深圳前海大数点科技有限公司 Micro-service dynamic disposition system and method based on cloud calculation
CN106506605A (en) * 2016-10-14 2017-03-15 华南理工大学 A kind of SaaS application construction methods based on micro services framework
CN107911430A (en) * 2017-11-06 2018-04-13 上海电机学院 A kind of micro services infrastructure equipment

Also Published As

Publication number Publication date
CN110740046A (en) 2020-01-31

Similar Documents

Publication Publication Date Title
CN110019350B (en) Data query method and device based on configuration information
EP3251031B1 (en) Techniques for compact data storage of network traffic and efficient search thereof
KR102634058B1 (en) Input and output schema mapping
CN112685433B (en) Metadata updating method and device, electronic equipment and computer-readable storage medium
US11159397B2 (en) Lower-tier application deployment for higher-tier system data monitoring
US9535966B1 (en) Techniques for aggregating data from multiple sources
WO2016095360A1 (en) Method of processing ontology model of internet of things and device
US11755531B1 (en) System and method for storage of data utilizing a persistent queue
CN109783562B (en) Service processing method and device
Kamilaris et al. WOTS2E: A search engine for a Semantic Web of Things
US11841834B2 (en) Method and apparatus for efficient synchronization of search heads in a cluster using digests
US11153071B2 (en) Citation and attribution management methods and systems
CN113268955A (en) Message conversion method and device
CN111427899A (en) Method, device, equipment and computer readable medium for storing file
CN112818026A (en) Data integration method and device
CN114168149A (en) Data conversion method and device
CN110740046B (en) Method and device for analyzing service contract
US10713014B2 (en) Multi-platform interface framework
CN116069725A (en) File migration method, device, apparatus, medium and program product
CN111143310A (en) Log recording method and device and readable storage medium
KR102169930B1 (en) Semantic Information Management Method for a M2M/IoT platform
CN112783842B (en) Log collection method and device
CN113704203A (en) Log file processing method and device
CN112637288A (en) Streaming data distribution method and system
CN113778886B (en) Processing method and device for test cases

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