CN111200651A - Method, system, device and medium for timed calling of microservice - Google Patents
Method, system, device and medium for timed calling of microservice Download PDFInfo
- Publication number
- CN111200651A CN111200651A CN201911412216.8A CN201911412216A CN111200651A CN 111200651 A CN111200651 A CN 111200651A CN 201911412216 A CN201911412216 A CN 201911412216A CN 111200651 A CN111200651 A CN 111200651A
- Authority
- CN
- China
- Prior art keywords
- microservice
- micro
- service
- calling
- pulling
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/2521—Translation architectures other than single NAT servers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
Abstract
The present invention relates to the field of software applications, and in particular, to a method, system, device, and medium for timed invocation of microservices. The method for calling the microservice at fixed time comprises the following steps: receiving a registration request of a microservice; storing the microservice; pulling the micro-service to be called within the current time range; the pulled microservice is invoked. The method and the system can dynamically configure and manage the micro-service, can trigger the calling of the micro-service at regular time, solve the problem in the scene of the regular calling of the micro-service, are the micro-service, and can be seamlessly integrated into a micro-service framework.
Description
Technical Field
The present invention relates to the field of software applications, and in particular, to a method, system, device, and medium for timed invocation of microservices.
Background
Microservice architecture is a popular architecture style of modern software engineering. A large-scale complex software application is composed of one or more micro-services, each micro-service is independently deployed and loosely coupled with each other, and each micro-service is only dedicated to completing one task. The micro service call refers to generating a request of the micro service, sending the request to a corresponding target address of the micro service, and acquiring a corresponding result and data to complete a corresponding task. Under the microservice architecture, a software system implements a wide variety of functions by making one or more calls to one or more microservices.
There are two current ways to invoke microservices. One is direct calling and one is indirect calling.
The process of directly calling the micro-service, namely obtaining the address of the micro-service, generating a request and directly sending the request to the address to obtain the result is also called synchronous calling. The direct calling mode is a general mode of micro-service calling, and micro-service calling without modes generally refers to direct calling. But direct invocation cannot handle the following scenarios: firstly, in an asynchronous calling scenario, the execution time of a certain micro-service called by a main program is long, and even exceeds the timeout time of a general request, so that the micro-service needs to be returned immediately after the micro-service starts to execute (without waiting for a result) to avoid the blocking of the main program. And secondly, calling a scene at fixed time, and calling the micro-service at a specified moment. Both of the above two scenarios need to rely on additional methods and devices, and are implemented in an indirect calling manner.
For the asynchronous call scenario, the message queue service is generally used to implement, such as RabbitMQ, Kafka, and other products. The former micro service executed by the main program can send a message to the message queue when the execution is finished, the message queue contains the execution result, and after receiving the message, the message queue directly pushes the message to the main program to trigger the calling of the next micro service. For the scenario of timed call, a timer is generally used to implement, such as crontab. The user configures a text file according to a certain rule, specifies the time and the mode of micro-service calling, and then calls the micro-service at the specified time by the timer.
With respect to the method and apparatus for implementing a timed call using a timer, the following disadvantages currently exist:
1. the micro-service calling task cannot be dynamically set, the creation, deletion and modification of the timing task only depend on the mode of automatically or semi-automatically modifying the configuration file, and the configuration dynamic state cannot be subjected to addition, deletion, modification and the like by using an interface.
2. The timer does not have high availability capability, because the timer is a stateful service, the high availability cannot be realized by using a multi-copy mode like a stateless service, and the service cannot be realized by a single-copy timer suffering from a host downtime event.
3. The execution control logic of the timer can not be used in combination with other micro-services, and because the timer has no dynamic configuration modification interface, the generation and configuration of the timer can not be combined with business logic to cooperate with other micro-services to complete some complex control logic.
4. The timer is not a micro-service, cannot be added into micro-service arrangement logic, and has certain damage to the whole micro-service architecture.
Disclosure of Invention
The invention aims to provide a method, a system, equipment and a medium for calling a micro service at fixed time, which can dynamically configure and manage the micro service, can trigger the calling of the micro service at fixed time, solves the problem in the scene of calling the micro service at fixed time, is the micro service, and can be seamlessly integrated into a micro service architecture.
The invention discloses a method for calling micro-service at fixed time, which comprises the following steps:
receiving a registration request of a microservice;
storing the microservice;
pulling the micro-service to be called within the current time range;
invoking the pulled microservice.
Optionally, storing the microservice comprises:
storing a configuration file of the micro service, wherein the configuration file of the micro service comprises the calling time of the micro service and the calling address of the micro service.
Optionally, pulling the micro-service to be invoked within the current time range comprises:
pulling the microservice having the invocation time of the microservice within a current time range.
Optionally, invoking the micro-service of pulling comprises:
sending a calling request of the micro service to the calling address of the pulled micro service;
and receiving the calling result of the micro service.
Optionally, storing the microservice further comprises:
generating a unique identifier associated with the microservice;
storing the unique identifier.
Optionally, pulling the micro-service to be invoked within the current time range comprises:
pull the unique identifier associated with the microservice for which the invocation time of the microservice is within a current time range;
storing the unique identifier pulled.
Optionally, invoking the micro-service of pulling comprises:
obtaining the calling address of the associated microservice based on the stored unique identifier;
sending a calling request of the micro service to the calling address of the micro service;
and receiving the calling result of the micro service.
The invention discloses a system for calling micro-service at fixed time, which comprises:
the receiving module is used for receiving a registration request of the microservice;
a storage module storing the microservice;
the pulling module is used for pulling the micro-service to be called within the current time range;
and the calling module is used for calling the pulled micro-service.
The invention discloses a device for calling micro-service regularly, which comprises a memory and a processor, wherein the memory stores computer executable instructions, and the processor is configured to execute the instructions to implement a method for calling micro-service regularly, and the method comprises the following steps:
receiving a registration request of a microservice;
storing the microservice;
pulling the micro-service to be called within the current time range;
invoking the pulled microservice.
The present invention discloses a computer storage medium encoded with a computer program, the computer program comprising instructions executable by one or more computers to implement a method of timed call microservices, the method comprising:
receiving a registration request of a microservice;
storing the microservice;
pulling the micro-service to be called within the current time range;
invoking the pulled microservice.
Compared with the prior art, the invention has the main differences and the effects that:
the invention can dynamically configure and manage the micro-service by storing the micro-service, and can trigger the calling of the micro-service at regular time by pulling the micro-service to be called in the current time range, thereby solving the problem of the micro-service in the scene of calling at regular time.
Drawings
FIG. 1 is a block diagram of the hardware architecture of a server for a method of timed invocation of a microservice according to the present invention;
FIG. 2 is a flow diagram of a method of timed invocation of a microservice according to a first embodiment of the present invention;
fig. 3 is a structural diagram of a system for periodically calling a microservice according to a second embodiment of the present invention.
Detailed Description
In order to make the purpose and technical solution of the embodiments of the present invention clearer, the technical solution of the embodiments of the present invention will be clearly and completely described below with reference to the drawings of the embodiments of the present invention. It is to be understood that the embodiments described are only a few 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 described embodiments of the invention without any inventive step, are within the scope of protection of the invention.
In accordance with an embodiment of the present invention, there is provided an embodiment of a method for timed invocation of a microservice, where the steps illustrated in the flowchart of the figure may be performed in a computer system, such as a set of computer-executable instructions, and where the logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than that illustrated herein.
The method provided by the application mode can be executed in a mobile terminal, a computer terminal or a server. Taking the example of running on a server, fig. 1 is a block diagram of the hardware architecture of the server for the method of timed invocation of microservices according to the invention. As shown in fig. 1, the server 100 may include one or more (only one shown in the figure) processors 101 (the processors 101 may include, but are not limited to, processing devices such as central processing units CPU, image processing units GPU, digital signal processing units DSP, microprocessor MCU, or programmable logic devices FPGA, etc.), input/output interfaces 102 for interacting with a user, a memory 103 for storing data, and a transmission device 104 for communication functions. It will be understood by those skilled in the art that the structure shown in fig. 1 is only an illustration and is not intended to limit the structure of the electronic device. For example, server 100 may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.
The input/output interface 102 may be connected to one or more displays, touch screens, etc. for displaying data transmitted from the server 100, and may also be connected to a keyboard, a stylus, a touch pad, and/or a mouse, etc. for inputting user instructions such as selection, creation, editing, etc.
The memory 103 may be used to store a database, a queue, and software programs and modules of application software, such as program instructions/modules corresponding to the method for invoking the micro-service regularly in the embodiment of the present invention, and the processor 101 executes various functional applications and data processing by running the software programs and modules stored in the memory 103, that is, implementing the method for invoking the micro-service regularly. The memory 103 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, memory 103 may further include memory located remotely from processor 101, which may be connected to server 100 over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission device 104 is used to receive or transmit data via a network, which may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others. The above-described specific example of the network may include the internet provided by the communication provider of the server 100.
FIG. 2 is a flow chart of a method of timed invocation of a microservice according to a first embodiment of the present invention.
As shown in fig. 2, method 200 may include:
The invention can dynamically configure and manage the micro-service by storing the micro-service, and can trigger the calling of the micro-service at regular time by pulling the micro-service to be called in the current time range, thereby solving the problem of the micro-service in the scene of calling at regular time.
Optionally, the registration request of the microservice may include: a micro-service creation request, a micro-service modification request, a micro-service deletion request, and the like. Wherein the created micro service may be stored when a creation request of the micro service is received, the modified micro service may be stored when a modification request of the micro service is received, and the deleted micro service may be stored when a deletion request of the micro service is received.
Alternatively, a registration request for the micro service may be received from the user, and the user may transmit the registration request for the micro service via a User Interface (UI). In addition, the user may also send a view request of the micro service via the UI to view the status and the calling result of the micro service.
Optionally, receiving the registration request of the microservice may include: and receiving a configuration file of the micro service, wherein the configuration file of the micro service comprises the calling time of the micro service, the calling address of the micro service and the like. Wherein the invocation time of the microservice may indicate when the microservice is invoked and the invocation address of the microservice may indicate where to send the invocation request of the microservice.
Optionally, the storage microservice may include: and storing a configuration file of the micro service, wherein the configuration file of the micro service comprises the calling time of the micro service and the calling address of the micro service. The configuration file of the micro service may be stored via an Application Programming Interface (API), and the API may include a RESTful API, so that operations such as adding, deleting, checking, and the like may be performed on the timing task via the Interface, the configuration of the timing task may be dynamically configured and managed, and the timing task may be closed and opened, so that the application may execute more complex control logic in cooperation with other micro services, for example, perform loop call on the micro service by times, and the like.
Optionally, the configuration file for the microservice may be stored in a distributed store. The distributed storage may adopt a master-standby mode to realize high availability, when the master node is down, one slave node may be automatically selected from the plurality of slave nodes to serve as the master node, and when a plurality of copies pull micro-services at the same time as described below, the micro-services may be processed by the same master node, thereby avoiding conflicts. In addition, all system states are stored in the distributed storage, so that stateless services are provided externally, and the services can be deployed on a plurality of hosts in a multi-copy mode, the availability of the whole services cannot be influenced when any host node is down, and the services have horizontal capacity expansion capacity to bear higher concurrent requests.
Optionally, pulling the micro-service to be invoked within the current time range may include: and pulling the micro-service with the calling time of the micro-service within the current time range. Wherein the configuration file or only the calling address of each micro-service in the micro-service sequence with the calling time of the micro-service within the current time range can be pulled from the distributed storage via the main loop, and the main loop can perform the pulling action once at an interval of Δ T, for example, 1 second. Also, the current time range may be T ± Δ T, where T represents the current time, so that any micro-service omission may be avoided.
Optionally, invoking the pulled microservice may include: sending a calling request of the micro service to a calling address of the pulled micro service; and receiving the calling result of the micro service. Since the configuration file or only the calling address of the micro-service is pulled through the main loop, one or more times of calling can be performed on one or more micro-services at regular time by sending the calling request of the micro-service to the calling address and receiving the calling result of the micro-service through the main loop, so that large-scale complex software application can be implemented.
Optionally, the storage microserver may further include: generating a unique identifier associated with the microservice; the unique identifier is stored. Wherein the unique identifier may be stored in the distributed cache in order of the invocation time of the microservice. The main role of the distributed cache is to speed up the operation of the main loop, which only stores the unique identifier of the microservice in chronological order, ensuring that the time for the main loop to pull each microservice sequence from the distributed cache as described below does not exceed 100ms, and thus ensuring that the error of microservice triggering does not exceed 1 second.
Optionally, pulling the micro-service to be invoked within the current time range may include: pulling a unique identifier associated with the microservice having a invocation time of the microservice within a current time range; the pulled unique identifier is stored. Wherein, after pulling, via the main loop, the unique identifier associated with each microservice in the microservice sequence for which the invocation time of the microservice is within the current time range, the pulled unique identifier can be stored in a message queue (e.g., NATS). The main role of the message queue is to asynchronously decouple the main loop and the Worker module as described below. If the main loop is used to directly invoke the microservice as described above, the long microservice invocation may block the main loop, thereby affecting the on-time triggering of subsequent microservices, since the invocation of each microservice is time-consuming differently. After asynchronous decoupling is carried out by using the message queue, the main loop is not responsible for calling specific micro-services any more, and is only responsible for triggering the micro-services on time. Also, the message queue may be a fully running in-memory message queue, with production (e.g., storing the pulled unique identifier in the message queue) and consumption (e.g., reading the stored unique identifier from the message queue) of the entire message all occurring in the memory. These measures ensure that the main loop triggers the microservice on time and finally ensures the accuracy of the microservice (error less than 1 second). Considering that the request time is basically in the order of seconds and the timeout time is generally set to be about 10s, the precision of less than 1 second can be basically considered as the best precision of the timed call micro-service in the micro-service architecture.
Optionally, invoking the pulled microservice may include: obtaining a calling address of the associated microservice based on the stored unique identifier; sending a calling request of the micro service to a calling address of the micro service; and receiving the calling result of the micro service. Where each specific micro-service call may be responsible for being performed via the Worker module, as opposed to directly invoking the micro-service using the main loop as described above.
Optionally, after invoking the pulled micro service, the method may further include: the history of the calls is stored in the form of a log. After receiving the calling result of the micro service, the calling result of the micro service can be stored in a distributed storage in a log mode through a Worker module, so that richer and more detailed capability of regularly calling the micro service execution log output can be provided.
Optionally, the configuration file of the microservice may also include an alarm condition of the microservice. The micro service alarm condition can indicate the state of the micro service in which the alarm is to be performed, so that the capability of customizing the alarm according to the task execution state can be provided.
It will be appreciated that the method of the present invention for timed invocation of a microservice is also a microservice itself, and thus may be seamlessly incorporated into a microservice architecture.
Fig. 3 is a structural diagram of a system for periodically calling a microservice according to a second embodiment of the present invention.
As shown in fig. 3, the system 300 may include:
a receiving module 302, which receives a registration request of a microservice;
a storage module 304 to store the microservice;
the pulling module 306 is used for pulling the micro-service to be called within the current time range;
the call module 308 calls the pulled microservice.
The first embodiment is a method embodiment corresponding to the present embodiment, and the present embodiment can be implemented in cooperation with the first embodiment. The related technical details mentioned in the first embodiment are still valid in this embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related-art details mentioned in the present embodiment can also be applied to the first embodiment.
A third embodiment of the invention is directed to a device for timed invocation of microservices, the device comprising a memory having stored thereon computer-executable instructions and a processor configured to execute the instructions to implement a method for timed invocation of microservices, the method comprising:
receiving a registration request of a microservice;
storing the microservice;
pulling the micro-service to be called within the current time range;
the pulled microservice is invoked.
The first embodiment is a method embodiment corresponding to the present embodiment, and the present embodiment can be implemented in cooperation with the first embodiment. The related technical details mentioned in the first embodiment are still valid in this embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related-art details mentioned in the present embodiment can also be applied to the first embodiment.
A fourth embodiment of the present invention is directed to a computer storage medium encoded with a computer program, the computer program comprising instructions executable by one or more computers to perform a method for invoking microservices at a time, the method comprising:
receiving a registration request of a microservice;
storing the microservice;
pulling the micro-service to be called within the current time range;
the pulled microservice is invoked.
The first embodiment is a method embodiment corresponding to the present embodiment, and the present embodiment can be implemented in cooperation with the first embodiment. The related technical details mentioned in the first embodiment are still valid in this embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related-art details mentioned in the present embodiment can also be applied to the first embodiment.
Each method embodiment of the present invention can be implemented by software, hardware, firmware, or the like. Whether the present invention is implemented as software, hardware, or firmware, the instruction code may be stored in any type of computer-accessible memory (e.g., permanent or modifiable, volatile or non-volatile, solid or non-solid, fixed or removable media, etc.). Also, the Memory may be, for example, Programmable Array Logic (PAL), Random Access Memory (RAM), Programmable Read Only Memory (PROM), Read-Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), a magnetic disk, an optical disk, a Digital Versatile Disk (DVD), or the like.
It should be noted that, each unit/module mentioned in each device embodiment of the present invention is a logical unit/module, and physically, one logical unit may be one physical unit, or may be a part of one physical unit, or may be implemented by a combination of multiple physical units, and the physical implementation manner of these logical units itself is not the most important, and the combination of the functions implemented by these logical units is the key to solve the technical problem provided by the present invention. Furthermore, the above-mentioned embodiments of the apparatus of the present invention do not introduce elements that are less relevant for solving the technical problems of the present invention in order to highlight the innovative part of the present invention, which does not indicate that there are no other elements in the above-mentioned embodiments of the apparatus.
It is to be noted that in the claims and the description of the present patent, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the use of the verb "comprise a" to define an element does not exclude the presence of another, same element in a process, method, article, or apparatus that comprises the element.
While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention.
Claims (10)
1. A method for timed invocation of microservices, the method comprising:
receiving a registration request of a microservice;
storing the microservice;
pulling the micro-service to be called within the current time range;
invoking the pulled microservice.
2. The method of claim 1, wherein storing the microservice comprises:
storing a configuration file of the micro service, wherein the configuration file of the micro service comprises the calling time of the micro service and the calling address of the micro service.
3. The method of claim 2, wherein pulling the microservice to be invoked within a current time range comprises:
pulling the microservice having the invocation time of the microservice within a current time range.
4. The method of claim 3, wherein invoking the micro-service of pulling comprises:
sending a calling request of the micro service to the calling address of the pulled micro service;
and receiving the calling result of the micro service.
5. The method of claim 2, wherein storing the microservice further comprises:
generating a unique identifier associated with the microservice;
storing the unique identifier.
6. The method of claim 5, wherein pulling the microservice to be invoked within a current time range comprises:
pull the unique identifier associated with the microservice for which the invocation time of the microservice is within a current time range;
storing the unique identifier pulled.
7. The method of claim 6, wherein invoking the micro-service of pulling comprises:
obtaining the calling address of the associated microservice based on the stored unique identifier;
sending a calling request of the micro service to the calling address of the micro service;
and receiving the calling result of the micro service.
8. A system for timed invocation of microservices, the system comprising:
the receiving module is used for receiving a registration request of the microservice;
a storage module storing the microservice;
the pulling module is used for pulling the micro-service to be called within the current time range;
and the calling module is used for calling the pulled micro-service.
9. An apparatus for timed invocation of microservices, the apparatus comprising a memory having stored thereon computer-executable instructions and a processor configured to execute the instructions to implement a method for timed invocation of microservices, the method comprising:
receiving a registration request of a microservice;
storing the microservice;
pulling the micro-service to be called within the current time range;
invoking the pulled microservice.
10. A computer storage medium encoded with a computer program, the computer program comprising instructions executable by one or more computers to perform a method of timed invocation of microservices, the method comprising:
receiving a registration request of a microservice;
storing the microservice;
pulling the micro-service to be called within the current time range;
invoking the pulled microservice.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911412216.8A CN111200651A (en) | 2019-12-31 | 2019-12-31 | Method, system, device and medium for timed calling of microservice |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911412216.8A CN111200651A (en) | 2019-12-31 | 2019-12-31 | Method, system, device and medium for timed calling of microservice |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111200651A true CN111200651A (en) | 2020-05-26 |
Family
ID=70746364
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911412216.8A Pending CN111200651A (en) | 2019-12-31 | 2019-12-31 | Method, system, device and medium for timed calling of microservice |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111200651A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112418784A (en) * | 2020-11-11 | 2021-02-26 | 北京京航计算通讯研究所 | Service arranging and executing system and method |
| CN112925584A (en) * | 2021-02-26 | 2021-06-08 | 北京百度网讯科技有限公司 | Scene-based file configuration method, device, storage medium, and program product |
| CN113010284A (en) * | 2021-03-04 | 2021-06-22 | 万翼科技有限公司 | Scheduling method and device of micro-service module, storage medium and electronic device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160112475A1 (en) * | 2014-10-21 | 2016-04-21 | Twilio, Inc. | System and method for providing a micro-services communication platform |
| CN108234666A (en) * | 2018-01-16 | 2018-06-29 | 云宏信息科技股份有限公司 | A kind of micro services calling system, method and computer storage media |
| CN109104491A (en) * | 2018-08-30 | 2018-12-28 | 郑州云海信息技术有限公司 | A kind of micro services call method, device, server and storage medium |
| CN109246251A (en) * | 2018-11-13 | 2019-01-18 | 杭州数梦工场科技有限公司 | A kind of micro services call method, device, system, equipment and readable storage medium storing program for executing |
| CN109474685A (en) * | 2018-11-16 | 2019-03-15 | 中国银行股份有限公司 | Service monitoring method and system under a kind of framework based on micro services |
| US20190104184A1 (en) * | 2017-09-29 | 2019-04-04 | Siemens Aktiengesellschaft | Information processing method, apparatus, and system |
| CN109714319A (en) * | 2018-12-06 | 2019-05-03 | 深圳市中农网有限公司 | Management system, method, apparatus, computer equipment and the storage medium of micro services |
-
2019
- 2019-12-31 CN CN201911412216.8A patent/CN111200651A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160112475A1 (en) * | 2014-10-21 | 2016-04-21 | Twilio, Inc. | System and method for providing a micro-services communication platform |
| US20190104184A1 (en) * | 2017-09-29 | 2019-04-04 | Siemens Aktiengesellschaft | Information processing method, apparatus, and system |
| CN108234666A (en) * | 2018-01-16 | 2018-06-29 | 云宏信息科技股份有限公司 | A kind of micro services calling system, method and computer storage media |
| CN109104491A (en) * | 2018-08-30 | 2018-12-28 | 郑州云海信息技术有限公司 | A kind of micro services call method, device, server and storage medium |
| CN109246251A (en) * | 2018-11-13 | 2019-01-18 | 杭州数梦工场科技有限公司 | A kind of micro services call method, device, system, equipment and readable storage medium storing program for executing |
| CN109474685A (en) * | 2018-11-16 | 2019-03-15 | 中国银行股份有限公司 | Service monitoring method and system under a kind of framework based on micro services |
| CN109714319A (en) * | 2018-12-06 | 2019-05-03 | 深圳市中农网有限公司 | Management system, method, apparatus, computer equipment and the storage medium of micro services |
Non-Patent Citations (2)
| Title |
|---|
| MALTE BARTENWERFER: "Design of a micro-cartridge system for the robotic assembly of exchangeable AFM-probe tips", 《2013 IEEE INTERNATIONAL CONFERENCE ON ROBOTICS AND AUTOMATION》 * |
| 谢伟: "基于微服务架构的开放平台消息***的设计与实现", 《信息科技辑》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112418784A (en) * | 2020-11-11 | 2021-02-26 | 北京京航计算通讯研究所 | Service arranging and executing system and method |
| CN112418784B (en) * | 2020-11-11 | 2021-11-30 | 北京京航计算通讯研究所 | Service arranging and executing system and method |
| CN112925584A (en) * | 2021-02-26 | 2021-06-08 | 北京百度网讯科技有限公司 | Scene-based file configuration method, device, storage medium, and program product |
| CN113010284A (en) * | 2021-03-04 | 2021-06-22 | 万翼科技有限公司 | Scheduling method and device of micro-service module, storage medium and electronic device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111756811B (en) | Method, system, device and medium for actively pushing distributed system | |
| US11403152B2 (en) | Task orchestration method and system | |
| CN111200651A (en) | Method, system, device and medium for timed calling of microservice | |
| CN111277639B (en) | Method and device for maintaining data consistency | |
| WO2019028992A1 (en) | Multi-module version dependency relationship construction method, device, server and storage medium | |
| CN112597249B (en) | Synchronous distribution storage method and system for service data | |
| CN111258723B (en) | Transaction processing method, device, system, medium and equipment of distributed system | |
| CN113407383B (en) | Main and standby system switching method and device, server and main and standby system | |
| CN111338829B (en) | Calling method and device for remote procedure call service | |
| CN109614271A (en) | Control method, device, equipment and the storage medium of multiple company-data consistency | |
| CN111294377B (en) | Dependency network request sending method, terminal device and storage medium | |
| CN111385255B (en) | Asynchronous call implementation method and device, server and server cluster | |
| CN103975301A (en) | Event service for local client applications through local server | |
| CN114328097A (en) | File monitoring method and device, electronic equipment and storage medium | |
| CN112363980B (en) | Data processing method and device of distributed system | |
| CN107577822A (en) | A kind of method of data synchronization, data synchronization unit and mobile terminal | |
| CN111147585A (en) | Equipment upgrading method, device, storage medium and system | |
| CN113852522B (en) | Camera binding and unbinding method based on multiple platforms | |
| CN107301089B (en) | APP deployment and calling method and terminal | |
| CN113760487B (en) | Service processing method and device | |
| CN111400327B (en) | Data synchronization method and device, electronic equipment and storage medium | |
| CN110262912B (en) | Calling method and device for procedure call gRPC | |
| CN113742376A (en) | Data synchronization method, first server and data synchronization system | |
| CN111813501A (en) | Data deleting method, device, equipment and storage medium | |
| CN113835892B (en) | Unified storage device, service management method and module thereof, and readable storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200526 |