CN113742105B - Method, device and medium for adapting micro-service framework - Google Patents
Method, device and medium for adapting micro-service framework Download PDFInfo
- Publication number
- CN113742105B CN113742105B CN202111020193.3A CN202111020193A CN113742105B CN 113742105 B CN113742105 B CN 113742105B CN 202111020193 A CN202111020193 A CN 202111020193A CN 113742105 B CN113742105 B CN 113742105B
- Authority
- CN
- China
- Prior art keywords
- service
- micro
- discovery
- framework
- provider
- 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
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Stored Programmes (AREA)
Abstract
The present disclosure provides a method, device and medium for adapting a micro-service framework, the method comprising: obtaining the realization of service discovery in a micro-service framework; registering the local information to a registry through service discovery; parsing service provider notes, and externally providing all methods of a specified interface in an HTTP form; generating service caller instances for all service callers; responding to the call service, and acquiring the realization of the micro service; obtaining surviving service provider cluster information in a registration center through the realization of service discovery; the spliced HTTP request path accesses the service address for service invocation. The method and the device realize necessary complete interaction of the micro service framework, including service registration, service discovery and service communication, write specific realization of the service discovery and the micro service through different micro service frameworks, and keep unchanged due to the use mode after integration is finished, so that when the micro service framework is switched, only the corresponding program dependence is needed to be replaced, and service codes are not needed to be modified.
Description
Technical Field
The present disclosure relates to the field of computer software technologies, and in particular, to a method, an apparatus, and a medium for adapting a micro-service framework implemented based on Java (computer programming language).
Background
The use of a micro-service framework is a common option in enterprise-level software development, with the aim of splitting the complete system into multiple independently deployable components, each as a separate service, with different service clusters being organized and managed by a registry, with access between services by remote procedure call (RPC, remote Procedure Call) technology.
Referring to fig. 1, the micro service framework mainly comprises the following components: a registry, a service provider, a service caller. The registration center is an independent middleware and is responsible for registering and discovering services. Both the service provider and the service caller are specific service instances, and a service can be used as both the caller and the provider of the service. Each service registers its own access address in the registration center, and different service clusters find other service clusters through the registration center, and when a service caller obtains the access address of a required service provider, the service caller can access the service provider through the RPC.
The micro service framework used in the software development can have the advantages of decoupling function modules, being convenient for team development at the same time, being capable of carrying out capacity expansion/contraction on services in a targeted manner and the like. When implementing the micro service framework using the development language, in order to call and dock the registry between services, the technology selection may use mainstream micro service frameworks, such as SpringCloud (a micro service framework), dubbo (a micro service framework), serviceomb (a micro service framework), and so on.
However, in the development of enterprise-oriented software, situations may be encountered in which a particular micro-service framework needs to be modified due to the custom requirements of the customer. Micro-service frameworks are difficult to alter once selected because each framework provides different application program interfaces (APIs, application Programming Interface) in the program for exposing services, invoking services. Replacement of the micro-service framework from the code level while ensuring that business logic is normal often wastes valuable time and effort on the part of the developer.
Currently, there is no universal solution to this problem, and it is the main stream practice to rewrite all the places involved in the use of the micro-service framework in the business based on the original code logic.
For example, the service code originally uses SpringCloud as a micro-service framework, and when the service code needs to be switched to use Dubbo, the service code is modified in the original code, and after all places where SpringCloud is used are modified to Dubbo, the code engineering is maintained separately. At this point there are two codes using SpringCloud and Dubbo. Only need to decide which one to use at deployment time.
In summary, the current alternatives to the micro-service framework mainly have the following drawbacks:
1. non-universal solution
The rapid development and adaptation cannot be realized, engineers are required to spend time for extra butt joint, the manpower resource cost is increased, and the efficiency is reduced.
2. High maintenance cost
If the subsequent service functions are updated, the newly developed service codes need to be synchronized into a plurality of projects, so that the maintenance cost is increased.
Disclosure of Invention
The main object of the present disclosure is to provide a method, apparatus and medium for adapting a micro-service framework based on Java implementation, so as to improve the above-mentioned drawbacks existing in the prior art.
The technical problems are solved by the following technical scheme:
as an aspect of the present disclosure, there is provided a method of adapting a micro service framework, comprising the steps of:
obtaining the realization of service discovery in the micro-service framework;
registering the local information to a registry through the service discovery;
parsing service provider annotations, all methods of providing specified interfaces externally in the form of HTTP (hypertext transfer protocol);
generating service caller instances for all service callers;
responding to the call service, and acquiring the realization of the micro service;
acquiring the cluster information of the service provider surviving in the registry through the realization of the service discovery; the method comprises the steps of,
the spliced HTTP request path accesses the service address for service invocation.
Optionally, the step of obtaining implementation of service discovery in the micro service framework includes:
an implementation of service discovery in the micro-service framework is obtained using a service discovery provider, which is a container that manages the service discovery.
Optionally, the step of registering the local information to a registry through the service discovery specifically includes:
acquiring an Internet protocol address of a local machine and port information for monitoring during program running;
registering the acquired internet protocol address and the port information with a registry using a service discovery instance.
Optionally, the parsing service provider annotates, and provides all the steps of the method of the specified interface in the form of HTTP, specifically including:
in response to program start, scanning all classes and screening out classes annotated by the service provider;
analyzing annotation information of a service provider to obtain realized interface information;
acquiring all methods of an interface, and splicing the interface name and the method name into a URL (Uniform resource locator) address;
an HTTP interface is created, a request path is set to the URL address, and a currently scanned class is set as a processing module of the HTTP request.
Optionally, the step of generating service caller instances for all service callers includes:
in response to program start, all interfaces annotated by the service invoker are scanned and screened, and dynamic proxy classes are circularly generated for the scanned interfaces as service invoker instances.
Optionally, the step of obtaining the implementation of the micro service includes:
the implementation of the micro-service is obtained by a micro-service provider, which is a container that manages the micro-service.
Optionally, the step of obtaining service provider cluster information surviving in the registry through implementation of the service discovery includes:
obtaining an implementation of the service discovery using a service discovery provider;
all IP (internet protocol) addresses and port information for providing services are acquired by the service discovery function of the service discovery and one of them is selected as a service provider.
Optionally, the step of splicing the HTTP request path to access the service address to make a service call includes:
splicing addresses through interface information and a called method;
and sending the HTTP request to the selected IP address and port to realize remote service call.
As another aspect of the disclosure, an electronic device is provided that includes a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing an adaptation method of a micro-service framework as described above when executing the computer program.
As another aspect of the present disclosure, a computer readable medium is provided having stored thereon computer instructions which, when executed by a processor, implement a method of adapting a micro-service framework as described above.
Other aspects of the present disclosure will be appreciated by those of skill in the art in light of the present disclosure.
The positive progress effect of the present disclosure is:
the adaptation method, the equipment and the medium of the micro service framework effectively realize necessary complete interaction of the micro service framework, including service registration, service discovery and service communication, write service discovery and specific realization of the micro service through different micro service frameworks, and keep unchanged due to the use mode after integration, so that the micro service framework is switched only by replacing corresponding program dependence without modifying service codes, thereby greatly improving efficiency, saving labor cost and reducing maintenance cost.
Drawings
The features and advantages of the present disclosure will be better understood upon reading the detailed description of embodiments of the disclosure in conjunction with the following drawings. In the drawings, the components are not necessarily to scale and components having similar related features or characteristics may have the same or similar reference numerals.
Fig. 1 is a schematic diagram of the main composition structure of a micro-service framework.
FIG. 2 is a schematic diagram of a service discovery and registry interaction scenario.
FIG. 3 is a schematic diagram of a microservice communication interaction scenario.
Fig. 4 is a schematic diagram of a service exposure flow for implementing a micro-service framework by a business system.
Fig. 5 is a main flow diagram of an adaptation method of a micro-service framework according to an embodiment of the present disclosure.
Fig. 6 is a schematic structural diagram of an electronic device implementing a method of adaptation of a micro-service framework according to another embodiment of the present disclosure.
Detailed Description
The present disclosure is further illustrated by way of examples below, but is not thereby limited to the scope of the examples described.
It should be noted that references in the specification to "one embodiment," "an alternative embodiment," "another embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the relevant art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
In the description of the present disclosure, it should be understood that the terms "center," "lateral," "upper," "lower," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," and the like indicate orientations or positional relationships based on the orientations or positional relationships illustrated in the drawings, merely to facilitate description of the present disclosure and simplify description, and do not indicate or imply that the devices or elements being referred to must have a particular orientation, be configured and operated in a particular orientation, and thus should not be construed as limiting the present disclosure. Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present disclosure, unless otherwise indicated, the meaning of "a plurality" is two or more. In addition, the term "include" and any variations thereof are intended to cover a non-exclusive inclusion.
In the description of the present disclosure, it should be noted that, unless explicitly specified and limited otherwise, the terms "mounted," "connected," and "connected" are to be construed broadly, and may be either fixedly connected, detachably connected, or integrally connected, for example; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the terms in the present disclosure may be understood in detail by those of ordinary skill in the art.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
In order to overcome the above-mentioned drawbacks existing at present, the present embodiment provides a method for adapting a micro service framework, which includes the following steps: obtaining the realization of service discovery in a micro-service framework; registering the local information to a registry through service discovery; parsing service provider notes, and externally providing all methods of a specified interface in an HTTP form; generating service caller instances for all service callers; responding to the call service, and acquiring the realization of the micro service; obtaining surviving service provider cluster information in a registration center through the realization of service discovery; and splicing the HTTP request path to access the service address for service call.
In this embodiment, a service discovery interface (SPI, service Provider Interface) technology provided by a Java software development package (JDK, java Development Kit) is used to load micro service (Microservice) implementation and service discovery (ServiceDiscovery) implementation existing in a current program running environment, and a custom Java annotation SoaServiceRegister annotation service provider and soaserviceservice caller are used to achieve the effect of conveniently switching a specific Microservice framework.
Referring to fig. 2, servicediscover is an interface that interacts with a registry, interfaces with the actual registry using different servicediscover instances, and is discovered and loaded by the SPI mechanism by introducing program dependencies.
Referring to fig. 3, microservices are core interfaces for communication between microservices, each RPC call of each service caller is delegated to an implementation of the interface, and a Microservice specific implementation is discovered and loaded by an SPI mechanism by introducing program dependencies.
The SoaServiceRegister annotation modifies a specific class to identify the class as a service provider, which must implement an interface and set interface information in the annotation, meaning that this interface is used as a service, and all methods defined by it can be provided to the outside for invocation.
The SoaServiceClient annotation is modified on the interface as a service caller, and the annotation is required to specify information of the interface realized by the corresponding service provider. The method in the interface decorated by SoaServiceClient corresponds to the interface method realized by the service provider one by one, and the calling relation is represented. And scanning all interfaces added with SoaServiceClient comments when the application program is started, generating a dynamic proxy for the interfaces to be used by the program, and calling the service provided by the corresponding service provider by the bottom layer of the proxy through the Microservice specific implementation.
In this embodiment, the necessary complete interaction of the micro service framework including service registration, service discovery and service communication is effectively implemented, and the service discovery and the specific implementation of the micro service are written through different micro service frameworks, so that after the integration is completed, the usage mode remains unchanged, and therefore, when the micro service framework is switched, only the corresponding program dependence is needed to be replaced, and the service code is not needed to be modified, thereby greatly improving the efficiency, saving the labor cost and reducing the maintenance cost.
Specifically, as an embodiment, referring to fig. 4 and 5, a service exposure flow for implementing a micro service frame by using the service system according to the embodiment is specifically shown in fig. 4, a service call flow is specifically shown in fig. 5, and the adapting method for the micro service frame according to the embodiment mainly includes the following steps:
step 101, obtaining a specific implementation of service discovery (ServiceDiscovery) in the micro-service framework.
In this step, the implementation of service discovery in the micro-service framework is obtained using a service discovery provider (ServiceDiscovery provider), which is a container that manages ServiceDiscovery.
Specifically, the initialization logic is triggered when the servicediscover provider is loaded for the first time, and the servicediscover instance contained in the program running process is scanned out by using the SPI interface ServiceLoader provided by the JDK and stored for acquisition.
Step 102, registering the local information to a registry through service discovery.
Specifically, in this step, registering the service provider information to the registry specifically includes the steps of:
step 1021, acquiring the IP address of the local machine and the port information monitored during program running;
step 1023, registering the acquired IP address and port information to a registry by using a ServiceDiscovery instance. At this time, if the service discovery function of the registry is used, the IP address and port information of the deployment of the present program can be acquired.
Step 103, parsing service provider (SoaServiceRegister) notes, and providing all methods of the appointed interface in the form of HTTP.
Specifically, in this step, the specific step of exposing the HTTP interface includes the steps of:
step 1031, scanning all classes when the program is started, and screening out the class added with the ServiceRegister annotation;
step 1032, analyzing ServiceRegister annotation information to obtain realized interface information;
step 1033, acquiring all methods of the interface, and splicing the interface name and the method name into a URL address;
in step 1034, an HTTP interface is created, and the request path is set to the URL address generated in step 1033 and the currently scanned class is set as the processing module of the HTTP request. After the creation, the HTTP interface generated by the program can be accessed and processed correctly.
Step 104, generating service caller instance for all service callers (SoaServiceClients).
In this step, the service caller instance is generated by scanning and screening all the interfaces annotated with SoaServiceClient when the program is started, and generating dynamic proxy class for the scanned interfaces in a circulating way as the service caller instance.
Step 105, in response to calling the service, a specific implementation of a specific micro service (Microservice) is obtained.
This step is to obtain a Microservice implementation by a Microservice provider (Microservice provider) when any method is invoked using the service caller instance generated in step 104, microse rviceProvider is a container that manages microservices. The initialization logic is triggered when the MicroserviceProvider is initially loaded, and an SPI interface ServiceLoader provided by JDK is used for scanning out Microservice examples contained in the program running process and storing the Microservice examples for acquisition.
And 106, executing a micro service calling method, and acquiring the cluster information of the service provider surviving in the registry through the realization of service discovery.
In this step, a specific implementation of servicediscover is obtained by using a servicediscover provider, and all IP addresses and ports for providing services are obtained through a service discovery function of servicediscover, and one of them is selected as a service provider.
Step 107, the spliced HTTP request path accesses a specific service address to make a service call.
In this step, address concatenation is performed by interface information and the called method according to logic similar to step 1033. And (3) sending the HTTP request to the IP address and the port selected in the step 106, so as to realize remote service call.
In this embodiment, the instance of calling the micro service and the instance related to service registration and service discovery are loaded through the SPI mechanism, so that convenient modification is realized to cope with different requirements.
In the embodiment, the micro-service framework universality adapting method based on Java implementation can enable the service codes to integrate any micro-service framework in the program only by abutting a set of interfaces, thereby realizing quick and efficient use and switching bottom implementation based on the existing codes, improving usability and software development efficiency and reducing maintenance cost.
The adaptation method of the micro-service framework provided by the embodiment mainly has the following beneficial effects:
1. the method for realizing the universality of service registration, service discovery and service communication can be used for effectively interfacing with the micro-service frames of various large main streams;
2. by using the SPI framework, the specific implementation of the program can be switched by introducing dependence;
3. the problem of long development period of the enterprise switching micro service framework is effectively solved;
4. the coding efficiency of the research personnel is effectively improved, the software development period is shortened, and the cost is reduced.
Fig. 6 is a schematic structural diagram of an electronic device according to the present embodiment. The electronic device comprises a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the adaptation method of the micro-service framework as in the above embodiments when executing the program. The electronic device 30 shown in fig. 6 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.
As shown in fig. 6, the electronic device 30 may be embodied in the form of a general purpose computing device, which may be a server device, for example. Components of electronic device 30 may include, but are not limited to: the at least one processor 31, the at least one memory 32, a bus 33 connecting the different system components, including the memory 32 and the processor 31.
The bus 33 includes a data bus, an address bus, and a control bus.
Memory 32 may include volatile memory such as Random Access Memory (RAM) 321 and/or cache memory 322, and may further include Read Only Memory (ROM) 323.
Memory 32 may also include a program/utility 325 having a set (at least one) of program modules 324, such program modules 324 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
The processor 31 executes various functional applications and data processing, such as the adaptation method of the micro-service framework in the above embodiments of the present disclosure, by executing a computer program stored in the memory 32.
The electronic device 30 may also communicate with one or more external devices 34 (e.g., keyboard, pointing device, etc.). Such communication may be through an input/output (I/O) interface 35. Also, model-generating device 30 may also communicate with one or more networks, such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet, via network adapter 36. As shown in fig. 6, network adapter 36 communicates with the other modules of model-generating device 30 via bus 33. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in connection with the model-generating device 30, including, but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, data backup storage systems, and the like.
It should be noted that although several units/modules or sub-units/modules of an electronic device are mentioned in the above detailed description, such a division is merely exemplary and not mandatory. Indeed, the features and functionality of two or more units/modules described above may be embodied in one unit/module in accordance with embodiments of the present disclosure. Conversely, the features and functions of one unit/module described above may be further divided into ones that are embodied by a plurality of units/modules.
The present embodiment also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps in the adaptation method of the micro-service framework in the above embodiments.
More specifically, among others, readable storage media may be employed including, but not limited to: portable disk, hard disk, random access memory, read only memory, erasable programmable read only memory, optical storage device, magnetic storage device, or any suitable combination of the foregoing.
In a possible implementation, the disclosure may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps in an adaptation method implementing the micro-service framework as in the above embodiments, when the program product is executed on the terminal device.
Wherein the program code for carrying out the present disclosure may be written in any combination of one or more programming languages, and the program code may execute entirely on the user device, partly on the user device, as a stand-alone software package, partly on the user device, partly on a remote device or entirely on the remote device.
While specific embodiments of the present disclosure have been described above, it will be appreciated by those skilled in the art that this is by way of example only, and the scope of the disclosure is defined by the appended claims. Various changes and modifications to these embodiments may be made by those skilled in the art without departing from the principles and spirit of the disclosure, but such changes and modifications fall within the scope of the disclosure.
Claims (9)
1. A method of adapting a micro-service framework, comprising the steps of:
obtaining the realization of service discovery in the micro-service framework;
registering the local information to a registry through the service discovery;
parsing service provider notes, and externally providing all methods of a specified interface in an HTTP form;
generating service caller instances for all service callers;
responding to the call service, and acquiring the realization of the micro service;
acquiring the cluster information of the service provider surviving in the registry through the realization of the service discovery; the method comprises the steps of,
splicing HTTP request paths to access service addresses to make service calls;
the step of obtaining the implementation of service discovery in the micro-service framework includes:
an implementation of service discovery in the micro-service framework is obtained using a service discovery provider, which is a container that manages the service discovery.
2. The method for adapting a micro-service framework according to claim 1, wherein the step of registering local information to a registry through the service discovery comprises:
acquiring an Internet protocol address of a local machine and port information for monitoring during program running;
registering the acquired internet protocol address and the port information with a registry using a service discovery instance.
3. The adaptation method of a micro-service framework according to claim 1, wherein the parsing service provider annotates all methods of providing specified interfaces in HTTP form, specifically comprising the steps of:
in response to program start, scanning all classes and screening out classes annotated by the service provider;
analyzing annotation information of a service provider to obtain realized interface information;
acquiring all methods of the interface, and splicing the interface name and the method name into a URL address;
an HTTP interface is created, a request path is set to the URL address, and a currently scanned class is set as a processing module of the HTTP request.
4. The method of adapting a micro-service framework according to claim 1, wherein the step of generating service caller instances for all service callers comprises:
in response to program start, all interfaces annotated by the service invoker are scanned and screened, and dynamic proxy classes are circularly generated for the scanned interfaces as service invoker instances.
5. The method for adapting a micro-service framework according to claim 1, wherein the step of obtaining an implementation of a micro-service comprises:
the implementation of the micro-service is obtained by a micro-service provider, which is a container that manages the micro-service.
6. The method of adapting a micro-service framework according to claim 1, wherein the step of obtaining service provider cluster information surviving in a registry through the implementation of service discovery comprises:
obtaining an implementation of the service discovery using a service discovery provider;
all IP addresses and port information providing services are acquired by the service discovery function of the service discovery, and one of them is selected as a service provider.
7. The method of adapting a micro-service framework according to claim 6, wherein the step of concatenating HTTP request paths to access service addresses for service invocation includes:
splicing addresses through interface information and a called method;
and sending the HTTP request to the selected IP address and port to realize remote service call.
8. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements a method of adapting a micro-service framework according to any of claims 1-7 when executing the computer program.
9. A computer readable medium having stored thereon computer instructions, which when executed by a processor, implement a method of adapting a micro-service framework according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111020193.3A CN113742105B (en) | 2021-09-01 | 2021-09-01 | Method, device and medium for adapting micro-service framework |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111020193.3A CN113742105B (en) | 2021-09-01 | 2021-09-01 | Method, device and medium for adapting micro-service framework |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113742105A CN113742105A (en) | 2021-12-03 |
| CN113742105B true CN113742105B (en) | 2024-03-12 |
Family
ID=78734624
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111020193.3A Active CN113742105B (en) | 2021-09-01 | 2021-09-01 | Method, device and medium for adapting micro-service framework |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113742105B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114201314B (en) * | 2021-12-10 | 2022-10-04 | 优维科技(深圳)有限公司 | Contract-based routing method for realizing service dependency discovery and service access |
| CN114706588B (en) * | 2022-03-24 | 2024-09-24 | 北京商越网络科技有限公司 | Migration method, migration device, migration medium and migration equipment for service architecture |
| CN114900383B (en) * | 2022-03-28 | 2024-04-19 | 青岛海尔科技有限公司 | Interface processing method, device, electronic device and computer readable storage medium |
| CN114756309B (en) * | 2022-06-14 | 2023-04-21 | 苏州万店掌网络科技有限公司 | Service calling method, framework, device and storage medium |
| CN116633993B (en) * | 2023-07-25 | 2023-10-10 | 中邮消费金融有限公司 | Cross-network micro-service calling method, device, equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109729149A (en) * | 2018-12-03 | 2019-05-07 | 国云科技股份有限公司 | An Annotation-Based Microservice Framework Implementation Method |
| CN109889416A (en) * | 2019-02-18 | 2019-06-14 | 西安交通大学 | A smart home system and construction method based on microservice architecture |
| CN110266815A (en) * | 2019-07-10 | 2019-09-20 | 西安纸贵互联网科技有限公司 | Micro services network system based on block chain |
| CN111245901A (en) * | 2019-12-31 | 2020-06-05 | 的卢技术有限公司 | Distributed service registration discovery method and system supporting service parameter issuing |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11531611B2 (en) * | 2019-07-29 | 2022-12-20 | Ncr Corporation | Auditing-as-a-service |
-
2021
- 2021-09-01 CN CN202111020193.3A patent/CN113742105B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109729149A (en) * | 2018-12-03 | 2019-05-07 | 国云科技股份有限公司 | An Annotation-Based Microservice Framework Implementation Method |
| CN109889416A (en) * | 2019-02-18 | 2019-06-14 | 西安交通大学 | A smart home system and construction method based on microservice architecture |
| CN110266815A (en) * | 2019-07-10 | 2019-09-20 | 西安纸贵互联网科技有限公司 | Micro services network system based on block chain |
| CN111245901A (en) * | 2019-12-31 | 2020-06-05 | 的卢技术有限公司 | Distributed service registration discovery method and system supporting service parameter issuing |
Non-Patent Citations (2)
| Title |
|---|
| Kevin Chávez ; Priscila Cedillo ; Mauricio Espinoza ; Victor Saquicela.A Systematic Literature Review on Composition of Microservices through the Use of Semantic Annotations: Solutions and Techniques.A Systematic Literature Review on Composition of Microservices through the Use of Semantic Annotations: Solutions and Techniques.2020,全文. * |
| 微服务通信框架的设计与实现;肖仲垚;中国优秀硕士学位论文全文数据库;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113742105A (en) | 2021-12-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113742105B (en) | Method, device and medium for adapting micro-service framework | |
| US11843661B2 (en) | Web service system and method | |
| CN110365751B (en) | Service processing method, device and equipment of gateway system | |
| US9323647B2 (en) | Request-based activation of debugging and tracing | |
| JP6058628B2 (en) | Multi-node application deployment system | |
| US8307058B2 (en) | Apparatus, method, and computer program product for processing information | |
| US9626223B2 (en) | Provisioning IaaS services | |
| US7926070B2 (en) | Performing requested commands for model-based applications | |
| KR20050016546A (en) | A computing services grid | |
| CN1208482A (en) | distributed processing | |
| CA2568565A1 (en) | System and method for implementing a general application program interface | |
| US20080288622A1 (en) | Managing Server Farms | |
| CN101727475B (en) | Method, device and system for acquiring database access process | |
| US20060020692A1 (en) | System and method for locating web services | |
| CN105721562A (en) | Proxy-based heterogeneous service calling method and collaborative calling system | |
| US11531526B1 (en) | Creating portable serverless applications | |
| US20190317840A1 (en) | Integrating transaction processing system interfaces with event-driven polyglot runtime modules | |
| CN113742100B (en) | Service calling method, system, equipment and medium based on micro-service architecture | |
| CN114371914A (en) | Container IP address configuration method and device, storage medium and electronic equipment | |
| US8239862B2 (en) | Apparatus, method, and computer program product for processing information | |
| US20080216050A1 (en) | Method and System for Accessing a Resource Implemented in a Computer Network | |
| CN113626095A (en) | Switching method and switching system of configuration center, electronic equipment and storage medium | |
| US11494184B1 (en) | Creation of transportability container files for serverless applications | |
| CN118449995B (en) | Extensible simulation service framework system based on micro-service architecture | |
| US11513833B1 (en) | Event listener interface for container-based execution of serverless functions |
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 |