CN113485717A - Efficient cross-language remote call (RFC) method - Google Patents
Efficient cross-language remote call (RFC) method Download PDFInfo
- Publication number
- CN113485717A CN113485717A CN202110532400.7A CN202110532400A CN113485717A CN 113485717 A CN113485717 A CN 113485717A CN 202110532400 A CN202110532400 A CN 202110532400A CN 113485717 A CN113485717 A CN 113485717A
- Authority
- CN
- China
- Prior art keywords
- service
- server
- client
- module
- communication
- 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
- 238000000034 method Methods 0.000 title claims abstract description 32
- 238000004891 communication Methods 0.000 claims abstract description 48
- 238000012545 processing Methods 0.000 claims abstract description 29
- 230000002159 abnormal effect Effects 0.000 claims description 9
- 230000008859 change Effects 0.000 claims description 9
- 230000008569 process Effects 0.000 claims description 8
- 230000006835 compression Effects 0.000 claims description 4
- 238000007906 compression Methods 0.000 claims description 4
- 230000006837 decompression Effects 0.000 claims description 4
- 230000007246 mechanism Effects 0.000 claims description 4
- 238000012544 monitoring process Methods 0.000 claims description 4
- 230000010365 information processing Effects 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 claims description 3
- 230000026676 system process Effects 0.000 claims description 2
- 230000006870 function Effects 0.000 abstract description 9
- 230000005540 biological transmission Effects 0.000 description 5
- 238000011161 development Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 239000000344 soap Substances 0.000 description 4
- 238000006243 chemical reaction Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 239000003795 chemical substances by application Substances 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
-
- 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/133—Protocols for remote procedure calls [RPC]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses an efficient cross-language remote invocation (RFC) method, which comprises the following steps: s1: the client is a remote data service or business service caller, and implements service call through the API logic module of the framework, S2: the server provides a centralized data service or a business service, and returns the processing result to the client, S3: the configuration center contains clients of the entire framework, sending notifications to the list of changes depending on the configuration. The invention encapsulates the load functions of load balance, overtime retransmission, network communication and the like to the frame level, and is fully transparent to the frame user, so that the frame user can realize remote calling in distributed application through simple configuration, and the items applying the frame are formally applied online, thereby solving the problem of stroke field adjustment in actual service and meeting the requirements of the actual service.
Description
Technical Field
The invention relates to the technical field of computers, in particular to an efficient cross-language remote call (RFC) method.
Background
In the current society, as the internet service enters a high-speed development stage, an increasingly huge and complex information system is required to support the internet service, the internet service has several characteristics, firstly, the user group is very large, the number of global netizens has broken through 20 hundred million in the beginning, the access of large user quantity has very high requirements on the pressure of the system, secondly, the change of the internet service is very fast, the information system for supporting the service development needs to be capable of quickly responding to the service change, thirdly, the complexity of the internet service is high, part of the service logic is very complex, the user can relate to a plurality of internal service logics when completing one service operation, and the function calling has a lot of intersections;
in order to support complexity and rapid change of internet services, a service-oriented system architecture needs to be considered from the technical architecture perspective, and logic is associated by defining reasonable interfaces and protocols between services, so as to finally support splitting of complex logic, reuse of support services and expansion of services. Meanwhile, in physical deployment, because the processing capacity of a single server always has a bottleneck and can become a physical single point, application services for processing different logics are distributed to different servers on the basis of a service-oriented system framework, and therefore the single-machine pressure is relieved through transverse expansion to improve the processing capacity of the system;
the prior art has the following defects: the current social internet is fast in development speed, higher in service complexity and larger in service volume, and cannot meet the requirements when only java is used for remote calling.
Disclosure of Invention
The invention provides an efficient cross-language remote call (RFC) method, which aims to solve the problems in the background technology.
In order to achieve the purpose, the invention provides the following technical scheme: an efficient cross-language remote invocation (RFC) method, comprising the steps of:
s1: the client is a remote data service or business service calling party and realizes service calling through an API logic module of the framework;
s2: the server provides centralized data service or business service, receives the message request of the client, performs corresponding business processing and returns the processing result to the client;
s3: the configuration center comprises clients of the whole framework, the list maintenance and management of the servers are realized, all the server lists and the client lists are stored, the conditions of the servers and the clients are detected through timing heartbeat, and the notification is sent to the lists with changes according to the configuration conditions.
In a preferred embodiment, in step S1, the API logic module includes a service call module, an initialization module, a message protocol processing module, a cache module, a communication module, and a watchdog module.
In a preferred embodiment, the communication module is responsible for initializing the communication part, the server communication module mainly starts a port, monitors the port and receives data, the client communication module mainly establishes connection and sends data, a Netty communication framework is adopted, the message protocol processing module analyzes messages according to a communication protocol, different serialization, deserialization, compression and decompression operations are carried out according to service requirements, the cache module stores client self information and server information for the client cache module, the server cache module stores the server information and is mainly used for load use and abnormal condition reinitialization of the load processing module, the Watcher module mainly monitors change of a server node and change of the client node according to a registered monitoring event, the initialization module carries out reinitialization operation for system start or abnormal condition, the method comprises the steps that operations such as cache initialization, communication and server/client information registration are needed, a service calling module is responsible for main service logic calling, after initialization is completed, a client API is called when an application system processes actual services, logic of server application and processing result return is called after the server API receives communication messages, and decoupling is carried out on a client by adopting a dynamic proxy mechanism.
In a preferred embodiment, in step S1, the client may be deployed in multiple servers in the same service, a single server deploys multiple servers, each service may occupy one port, and any one service may occupy one link, so that there may be multiple system objects, and the Apache community provides an object pool management class.
In a preferred embodiment, in step S2, the server belongs to a passive acceptance request message protocol, and in order to avoid port collision between multiple services deployed by a single server, the ports of the server bind adopt a random manner to adopt a Channel Group class, and automatically remove the closed west permanent from the Channel Group, and can uniformly close all Channel server communications in the Channel Group and execute during initialization, create a server communication connection through a ServerBoot strap, and then immediately port, and process coding, decoding, and information processing Handler through an injected Channel Pipeline Factory.
In a preferred embodiment, the packet protocol is read according to bits, and the packet is divided into two parts, namely a packet header and a packet body, where the packet header stores the content of the relevant protocol layer, and the packet body stores specific service information.
The invention has the technical effects and advantages that:
the invention solves the high-performance problem of network communication by adopting a remote calling framework based on NIO and adopting a JavaNIO technology, solves the high-tech management problem of calling information by adopting a Zookeeper under Apache, solves the low coupling problem by adopting a Java dynamic agent, the frame is logically divided, a plurality of common modules are extracted, the static and dynamic logics of the frame are explained through UMI, the whole framework is realized through Java and pressure test is carried out, various technologies and frameworks are applied in the finally realized framework, the problems of high performance, high manageability and the like are solved, load functions such as load balancing, overtime retransmission, network communication and the like are encapsulated to the framework level, is sufficiently transparent to the frame user, so that the frame user can realize remote calling in the distributed application through simple configuration, and the project applying the framework is formally applied online in sequence, so that the problem of a very famous problem of stroke field adjustment in actual business is solved, and the requirement of the actual business is met.
Detailed Description
The technical solutions in the embodiments of the present invention are clearly and completely described below, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The invention provides an efficient cross-language remote invocation (RFC) method, which comprises the following steps:
s1: the client is a remote data service or business service calling party and realizes service calling through an API logic module of the framework;
s2: the server provides centralized data service or business service, receives the message request of the client, performs corresponding business processing and returns the processing result to the client;
s3: the configuration center comprises clients of the whole framework, the list maintenance and management of the servers are realized, all the server lists and the client lists are stored, the conditions of the servers and the clients are detected through timing heartbeat, and the notification is sent to the lists with changes according to the configuration conditions.
Example 1
A frame caller sends a service logic to a client frame layer, the client frame layer packages the request and sends the packaged request to a server frame layer after receiving the specific request, the server frame layer converts the received request and calls the specific server logic to process, the processed result is returned to the client frame layer by communication, the client frame layer returns the result to the frame client caller, in order to package the functions of communication, load, message processing and the like to the frame layer, the frame layer is divided into a client API and a server API, the client API is responsible for receiving the client logic call, establishing the connection with the server API, calling the server API according to a load strategy, the server API is responsible for receiving the client API remote call request, calling the server logic to process, and returning the processed result to the client API o, and the frame solves the functions of abnormal processing, retransmission and the like under the abnormal conditions of communication and the like in the specific calling process And can, to newly-increased some service end nodes or some service end node suddenly under the circumstances that do not work client API can in time monitor, and in time newly-increased or delete the node, can abstract out the functional point of this frame:
1. generating dynamic proxy objects of a client and a server;
2. receiving the calling of the client and the server application through a framework API;
3. the problems of serialization and deserialization of objects and compression and decompression are solved;
4. establishing reliable and efficient communication and completing information transmission;
5. solving load and exception handling logic in the remote calling process;
6. managing all clients and servers, and making corresponding emergency response to the abnormal condition of any node.
Further, in the above technical solution, in the step S1, the API logic module includes a service calling module, an initialization module, a message protocol processing module, a cache module, a communication module, and a dispatcher module, because a same service is provided by a plurality of servers and needs to be provided for a plurality of clients for use, in an actual application project, due to various reasons, each service provider is not normal loop, and when multiple reasons such as hardware failure and version update are encountered, a service end may be suspended, and in this case, the whole framework is required to be able to shield such a situation. And the client does not repeatedly call the server which is tentatively provided with the service, and the invalid call is reduced.
Example 2
The Remote call framework needs to transmit call method, parameter and return value between client and server through a set of reliable and efficient communication Protocol, the Socket data transmission of the network of Socket \ RMI and Hessian \ Web Service, which is commonly used in the inter-system communication technology, is a special I/O, Socket is also a file descriptor, Socket also has a function call Socket similar to an open file, the function returns an integral Socket descriptor, the subsequent operations of connection establishment, data transmission and the like are all realized through the Socket, RMI currently uses Java Remote message exchange Protocol (Java Remote Messaging Protocol for communication, RMI has the advantages of Java 'Write one, Runywhere', the communication Protocol is mainly based on SOAP, the description of Service discovers and obtains the metadata of the Service through UDDI through WSDL, the Hessian Protocol and the Service Protocol are similar to HTTP, and the Web Service packet is also packaged in the HTTP, the Hessian protocol has the same advantages as the SOAP protocol, i.e. the transmission is not restricted by firewalls, and it has the advantage that it uses a binary protocol, therefore, the transmission data volume is much smaller than that of the SOAP protocol, the same object is transmitted, the data volume transmitted by the Hessian protocol is lower than that of the SOAP protocol by one order of magnitude, therefore, the distributed application in the complex network environment can obtain better performance and reliability by using the Hessian protocol, the performance sequence is Socket, RMI, Hessian and Web Server after test comparison, the performance of the Socket is undoubtedly the highest, but the processing of the Socket is a very complex process, the open-source framework Netty from the Jboss open-source great henry successfully solves the problems, and the asynchronous and event-driven characteristics of Netty enable the open-source framework Netty to quickly develop maintainable, high-performance and high-expansion-capability protocol services and client applications thereof.
Further, in the above technical solution, the communication module is responsible for initializing the communication part, the server communication module mainly starts a port, monitors the port, and receives data, the client communication module mainly establishes connection, and sends data, and adopts a Netty communication framework, the message protocol processing module analyzes a message according to a communication protocol, performs different serialization, deserialization, compression, and decompression operations according to service requirements, the cache module stores client self information and server information for the client cache module, the server cache module stores server information, and is mainly used for load use and abnormal condition reinitialization of the load processing module, the watchdog module mainly monitors changes of server nodes and changes of client nodes according to registered monitoring events, the initialization module re-initializes the system for system start or abnormal conditions, the method comprises the steps that operations such as caching, communication and registration of server/client information need to be initialized, a service calling module is responsible for main service logic calling, after initialization is completed, an application system calls a client API when processing actual services, and after the server API receives communication messages, the server API calls a server application and returns logic of processing results.
Further, in the above technical solution, in the step S1, the client may be deployed in multiple servers in the same service, a single server deploys multiple servers, each service may occupy one port, and any service may occupy one link, so that multiple system objects may be provided, the Apache community provides an object pool management class, an actual system load needs to bear greater and greater pressure along with development of a service, and a system architecture design needs to be able to support the pressure, an extension of a general system includes a vertical extension and a horizontal extension, the vertical extension mainly increases hardware processing speed, memory size and the like, but the vertical extension always encounters a bottleneck, and hardware input is very large and index is increased when the vertical extension reaches a certain degree, while requirements for each server by the horizontal extension are not very high, but the service is supported by multiple services that are horizontally extended, the hardware investment of the method is linearly increased, so the framework needs to be capable of supporting horizontal expansion, the server side needs to be expanded according to the actual business situation, the client side does not need to be modified while the server side is expanded, the expansion is transparent to the client side, and the client side needs to sense the increase or decrease of the server under the condition of hot deployment.
Example 3
In order to be able to call a remote method, a layer of communication processing needs to be added before and after the method is called, and the communication processing should be transparent to the client, Stub and skeeleton in the RMI principle, in order to enable Stub to be universal, a dynamic proxy mechanism of Java is considered, the dynamic proxy mechanism of Java is a proxy class dynamically generated by a Java program during running, the proxy class can be dynamically obtained as long as a group of interface and proxy class objects is simply specified, the proxy class is responsible for dispatching all method calls to the proxy objects for reflective execution, and in the process of dispatching execution, developers can also adjust the proxy class objects and functions thereof as required, which is a very flexible and elastic proxy framework.
Further, in the above technical solution, in step S2, the Server belongs to a protocol for passively receiving a request message, and in order to avoid a port conflict between multiple services deployed by a single Server, a port of a Server bind is randomly selected to use a Channel Group class, and the closed west will be automatically removed from the Channel Group, and all Channel Server communications in the Channel Group can be closed uniformly and executed during initialization, a Server communication connection is created through a Server boot strap, a peer end is followed, and a coding, decoding, and information processing Handler is processed through an injected Channel pilot Factory, and for a large traffic, a plurality of Client and a Server need to support service development, so that all information such as Client and Server need to be managed uniformly, all service information and link information can be queried, and managed services can be monitored in time, the service system only needs to care about service level logic, the whole framework needs to contain contents such as communication, monitoring, load balancing, store forwarding, synchronous and asynchronous conversion and the like, the contents are completely transparent to the service system, the actual embedding of the service system requires that the influence on the application is extremely small, the intrusion on the system is extremely small, and the service and the framework are divided into two levels on the logic level.
Further, in the above technical solution, the packet protocol is read according to bits, and the packet is divided into a packet header and a packet body, where the packet header stores the content of the relevant protocol layer, and the packet body stores specific service information.
Example 4
In a large-scale distributed system, dozens or even hundreds of nodes are formed, a client can call a plurality of service ends, the same service end can be called by a plurality of client ends, any node can change at any time, the client end needs to know a list of the service ends when starting, and each client end needs to sense in time when the service end changes, the client end needs to clearly determine a specific address of service when starting or calling the service, and the two modes are that one mode is that each client end stores a list of the service ends, and the second mode is that the list of the service ends is stored in a public place for the client end to obtain; the first mode is a very heavy workload for maintaining the information by the client under the condition of a large number of services, and the adjustment of a list maintained by the client due to the change adjustment of some service nodes requires the adjustment of the information by each client, which is a very troublesome matter, the second mode solves the defect of the first method in principle, and in combination with the description, I prefer the second mode to build a configuration center to store the information of the client and the server and monitor the states of all nodes, meanwhile, the conversion of events interested by the client and the server can be monitored and self measures can be taken in time, the open source project Zookeeper of Apache can be used comprehensively, and the configuration management and naming service functions of the Zookeeper can be fully utilized except the cluster of the Zookeeper.
The points to be finally explained are: first, in the description of the present application, it should be noted that, unless otherwise specified and limited, the terms "mounted," "connected," and "connected" should be understood broadly, and may be a mechanical connection or an electrical connection, or a communication between two elements, and may be a direct connection, and "upper," "lower," "left," and "right" are only used to indicate a relative positional relationship, and when the absolute position of the object to be described is changed, the relative positional relationship may be changed;
secondly, the method comprises the following steps: in the disclosed embodiment of the invention, only the structures related to the disclosed embodiment are related, other structures can refer to common design, and the same embodiment and different embodiments of the invention can be combined with each other under the condition of no conflict;
and finally: the above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that are within the spirit and principle of the present invention are intended to be included in the scope of the present invention.
Claims (6)
1. An efficient cross-language remote invocation (RFC) method, characterized by: the cross-language remote invocation (RFC) method comprises the following steps:
s1: the client is a remote data service or business service calling party and realizes service calling through an API logic module of the framework;
s2: the server provides centralized data service or business service, receives the message request of the client, performs corresponding business processing and returns the processing result to the client;
s3: the configuration center comprises clients of the whole framework, the list maintenance and management of the servers are realized, all the server lists and the client lists are stored, the conditions of the servers and the clients are detected through timing heartbeat, and the notification is sent to the lists with changes according to the configuration conditions.
2. An efficient cross-language remote invocation (RFC) method according to claim 1, wherein: in step S1, the API logic module includes a service call module, an initialization module, a message protocol processing module, a cache module, a communication module, and a watchdog module.
3. An efficient cross-language remote invocation (RFC) method according to claim 2, wherein: the communication module is responsible for initializing a communication part, the server communication module mainly starts a port, monitors the port and receives data, the client communication module mainly establishes connection and sends data, a Netty communication framework is adopted, the message protocol processing module analyzes a message according to a communication protocol and performs different serialization, deserialization, compression and decompression operations according to business requirements, the cache module stores client self information and server information for the client cache module, the server cache module stores the server information and is mainly used for a load processing module to use when in loading and reinitialize abnormal conditions, the Watcher module mainly monitors change of a server node and change of the client node according to registered monitoring events, the initialization module performs reinitialization operation when in system starting or abnormal conditions, and needs to initialize cache, monitor, and receive data, The method comprises the steps of communication, registration of server/client information and the like, wherein a service calling module is responsible for main service logic calling, after initialization is completed, when an application system processes actual services, a client API is called, after the server API receives communication messages, the server application is called, and the logic of processing results is returned, and decoupling is carried out on the client by adopting a dynamic proxy mechanism.
4. An efficient cross-language remote invocation (RFC) method according to claim 1, wherein: in step S1, the client may be deployed in multiple servers in the same service, a single server deploys multiple servers, each service may occupy one port, and any one service may occupy one link, so that there may be multiple system objects, and the Apache community provides an object pool management class.
5. An efficient cross-language remote invocation (RFC) method according to claim 1, wherein: in step S2, the server belongs to a protocol of passively receiving a request message, and in order to avoid port collision between multiple services deployed by a single server, the ports of the server bind are randomly selected to adopt a Channel Group class, and the closed west permanent is automatically removed from the Channel Group, and all Channel server communications in the Channel Group can be closed in a unified manner and executed during initialization, a server communication connection is created through a ServerBoot strap, and a bend immediate port is used to process encoding, decoding, and information processing Handler through an injected Channel Pipeline Factory.
6. An efficient cross-language remote invocation (RFC) method according to claim 5, wherein: the message protocol is read according to bits, and the message is divided into a message header and a message body, wherein the message header stores the content of a related protocol layer, and the message body stores specific service information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110532400.7A CN113485717A (en) | 2021-05-17 | 2021-05-17 | Efficient cross-language remote call (RFC) method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110532400.7A CN113485717A (en) | 2021-05-17 | 2021-05-17 | Efficient cross-language remote call (RFC) method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113485717A true CN113485717A (en) | 2021-10-08 |
Family
ID=77933539
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110532400.7A Pending CN113485717A (en) | 2021-05-17 | 2021-05-17 | Efficient cross-language remote call (RFC) method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113485717A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160164953A1 (en) * | 2014-12-05 | 2016-06-09 | Vmware, Inc. | Runtime generation of application programming interfaces for remote procedure call services |
| CN106506509A (en) * | 2016-11-15 | 2017-03-15 | 深圳市彬讯科技有限公司 | Can carry out servicing the lightweight RPC framework implementation methods that administers with language call |
| CN108234670A (en) * | 2018-01-31 | 2018-06-29 | 北京中安智达科技有限公司 | A kind of distributed remote call method based on zookeeper and netty |
| CN112035276A (en) * | 2020-08-06 | 2020-12-04 | 上海视云网络科技有限公司 | Java-based cross-platform extensible Remote Procedure Call (RPC) framework design method |
| CN112114979A (en) * | 2020-08-31 | 2020-12-22 | 厦门安胜网络科技有限公司 | Remote procedure call method and device |
| CN112367376A (en) * | 2020-10-28 | 2021-02-12 | 常州微亿智造科技有限公司 | Method for realizing mutual communication framework between micro services under industrial Internet of things |
-
2021
- 2021-05-17 CN CN202110532400.7A patent/CN113485717A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160164953A1 (en) * | 2014-12-05 | 2016-06-09 | Vmware, Inc. | Runtime generation of application programming interfaces for remote procedure call services |
| CN106506509A (en) * | 2016-11-15 | 2017-03-15 | 深圳市彬讯科技有限公司 | Can carry out servicing the lightweight RPC framework implementation methods that administers with language call |
| CN108234670A (en) * | 2018-01-31 | 2018-06-29 | 北京中安智达科技有限公司 | A kind of distributed remote call method based on zookeeper and netty |
| CN112035276A (en) * | 2020-08-06 | 2020-12-04 | 上海视云网络科技有限公司 | Java-based cross-platform extensible Remote Procedure Call (RPC) framework design method |
| CN112114979A (en) * | 2020-08-31 | 2020-12-22 | 厦门安胜网络科技有限公司 | Remote procedure call method and device |
| CN112367376A (en) * | 2020-10-28 | 2021-02-12 | 常州微亿智造科技有限公司 | Method for realizing mutual communication framework between micro services under industrial Internet of things |
Non-Patent Citations (2)
| Title |
|---|
| 张鹏飞;: "分布式服务框架的设计与实现", 现代计算机(专业版), no. 10, 5 April 2018 (2018-04-05) * |
| 陈世宜;叶德建;: "基于SOA架构的新型云平台服务管理中间件", 微型电脑应用, no. 07, 20 July 2016 (2016-07-20) * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111309374B (en) | Micro-service system and service calling method in micro-service system | |
| Baumer et al. | Grasshopper—A universal agent platform based on OMG MASIF and FIPA standards | |
| US8806506B2 (en) | System and method for processing messages using a common interface platform supporting multiple pluggable data formats in a service-oriented pipeline architecture | |
| US9258379B2 (en) | Session initiation protocol adapter system and method providing stateless node mapping to a stateful server node hosting a communication session for an actor | |
| Grace et al. | A reflective framework for discovery and interaction in heterogeneous mobile environments | |
| CN106663033B (en) | System and method for supporting a wraparound domain and proxy model and updating service information for cross-domain messaging in a transactional middleware machine environment | |
| WO2020207091A1 (en) | Management client, and device monitoring system and method | |
| CN111163166B (en) | Enterprise service bus system | |
| CN112035276B (en) | Cross-platform extensible RPC framework design method based on java | |
| US8135785B2 (en) | System and method for processing messages using pluggable protocol processors in a service-oriented pipeline architecture | |
| CN113596110A (en) | Heterogeneous cloud-oriented cloud native micro-service platform | |
| CN113852939B (en) | Cloud-protogenesis-oriented user plane function micro-service system | |
| CN113556359B (en) | Communication protocol conversion method, device, system and gateway device | |
| US20190104084A1 (en) | Managing access to logical objects in software defined networks | |
| CN116680035A (en) | GPU (graphics processing unit) method and device for realizing remote scheduling of kubernetes container | |
| US8316083B2 (en) | System and method for client interoperability | |
| US8806512B2 (en) | Collocation in a Java virtual machine of JSLEE, SIP servlets, and Java EE | |
| CN113254227B (en) | Method and system for remote method call across data centers | |
| CN115834668B (en) | Cluster node control method, device, equipment, storage medium and program product | |
| Butterfield | Fog computing with Go: A comparative study | |
| CN113485717A (en) | Efficient cross-language remote call (RFC) method | |
| CN112165529A (en) | Method, device, equipment and medium for low-cost cross-network data exchange | |
| McEwan et al. | Mobility in JCSP: New Mobile Channel and Mobile Process Models | |
| CN114500646B (en) | Decentralizing ESB cloud platform system and service calling method thereof | |
| Rossi | An event mechanism for Linux |
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 |