CN111580998A - RPC calling method of multiple tenants in SaaS service mode - Google Patents
RPC calling method of multiple tenants in SaaS service mode Download PDFInfo
- Publication number
- CN111580998A CN111580998A CN202010533970.3A CN202010533970A CN111580998A CN 111580998 A CN111580998 A CN 111580998A CN 202010533970 A CN202010533970 A CN 202010533970A CN 111580998 A CN111580998 A CN 111580998A
- Authority
- CN
- China
- Prior art keywords
- service
- tenant
- rpc
- calling
- saas
- 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 62
- 238000012423 maintenance Methods 0.000 claims abstract description 16
- 238000012545 processing Methods 0.000 claims abstract description 16
- 230000006870 function Effects 0.000 claims description 41
- 238000013507 mapping Methods 0.000 claims description 7
- 230000005540 biological transmission Effects 0.000 claims description 3
- 230000000694 effects Effects 0.000 claims description 3
- 238000011161 development Methods 0.000 abstract description 7
- 101100264195 Caenorhabditis elegans app-1 gene Proteins 0.000 description 3
- 230000004075 alteration Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
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
- 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/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/544—Remote
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/547—Messaging middleware
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/548—Queue
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention relates to a multi-tenant RPC calling method in a SaaS service mode, which is applied to the interior of a software provider and comprises the following steps: the service caller sets tenant information in the context of the service thread; obtaining namespace according to tenant information and application, and combining to obtain an MQ queue name; the service calling party initiates calling; the RabbitMQ middleware carries out routing according to the MQ queue name to find a service provider; the service provider provides service and service processing according to the service content in the MQ queue name; the RabbitMQ middleware carries out routing according to the MQ queue name to find a service calling party; the service calling party acquires and processes the return queue; and the service calling party cleans the information of the tenant and completes RPC calling. The RPC adopts the RabbitMQ as a basic component and takes the RabbitMQ as a central node, thereby realizing the basic RPC requirements of service registration, service discovery, service routing and the like; meanwhile, the RabbitMQ also provides the function of supporting multiple tenants; the RPC requirement under the multi-tenant scene is solved with low development and operation and maintenance cost.
Description
Technical Field
The invention relates to the technical field of remote invocation, in particular to a multi-tenant RPC invocation method in a SaaS service mode.
Background
SaaS, an abbreviated name of Software-as-a-Service, means Software as a Service, that is, providing a Software Service through a network. The SaaS software provider uniformly deploys the application software on a server of a tenant, the tenant can order the required application software service from the software provider through the Internet according to the actual working requirement, pay the cost to the software provider according to the amount and time of the ordered service, and obtain the service provided by the Saas software provider through the Internet.
The tenants are logic concepts in the SaaS, generally correspond to independent enterprise tenants, and are external users of the whole system and the application service function set. The application service and data of each tenant can be isolated logically/physically without influence. For the inside of a SaaS software provider, regarding a certain service function and flow, one function has a complete call chain, and when one SaaS software provider faces multiple tenants to acquire the service function and flow, the prior art generally adopts a vhost function, but the vhost function cannot completely meet the existing requirements, for example: firstly, binding the vhost with the connection, displaying configuration and creating a plurality of connections in an initialization stage, and adjusting configuration and restarting newly added tenants each time; secondly, the creation of the vhost must be displayed at the server, so that the maintenance cost is high; thirdly, versions of individual application tenants may be different, and separate instance deployment is required; finally, part of tenants have the requirement of sub-organization personalized services, and the vhost function cannot meet the requirement of the personalized services.
Therefore, it is necessary to provide a multi-tenant RPC calling method in a SaaS service mode, which meets the multi-dimensional flexible requirements of "service sharing + monopolizing" and "sub-organization/tenant", and also solves the RPC calling requirements in the SaaS service mode under the multi-tenant scenario at low development and operation and maintenance costs.
Disclosure of Invention
The invention aims to provide a multi-tenant RPC calling method in a SaaS service mode, which meets the multi-dimensional flexible requirements of service sharing + monopolizing, sub-organization/tenant and the like, and also solves the RPC calling requirement in a multi-tenant scene of the SaaS service mode with lower development and operation and maintenance costs.
In order to solve the problems in the prior art, the invention provides a multi-tenant RPC calling method in a SaaS service mode,
the RPC calling method is applied to the calling process inside a software provider, the software provider provides one service for one tenant as one service thread, and the completion of one service thread requires the calling of the functions of a plurality of function modules inside the software provider;
the RPC calling method of the multi-tenant in the SaaS service mode comprises the following steps:
setting tenant information in a service thread context by a current service calling party;
the service caller obtains namespace according to tenant information and application, and obtains a complete MQ queue name by combining the namespace and the service content of the tenant;
the service caller initiates calling according to the complete MQ queue name;
the RabbitMQ middleware carries out routing according to the complete MQ queue name to find a service provider;
the service provider monitors the complete MQ queue name, receives a calling request in the running process, and provides service and service processing according to the service content in the complete MQ queue name;
the RabbitMQ middleware carries out routing according to the complete MQ queue name, finds a service calling party, adds the service and service processing provided by the service provider into a return queue and returns the service calling party;
the service caller acquires and completes the processing of the service and the service processing in the return queue;
and the service calling party clears the information of the current tenant and completes one RPC calling.
Optionally, in the RPC calling method for multiple tenants in the SaaS service mode, the service caller is a caller that needs to call a function in the function module currently in the service thread, and the service provider is a provider that provides the function in the function module currently in the service thread.
Optionally, in the RPC calling method for multiple tenants in the SaaS service mode, tenant information and service content of the tenants are acquired from an external gateway of a software provider.
Optionally, in the RPC calling method for multiple tenants in the SaaS service mode, when the service caller initiates calling according to the complete MQ queue name, the method further includes the following steps: and the complete MQ queue name is arranged in a Header of the calling request information for transmission.
Optionally, in the RPC calling method for multiple tenants in the SaaS service mode, after the service provider receives a call request in an operation process, the method further includes the following steps:
and resolving Header information and setting the tenant information in the context of the service thread so as to distinguish the tenant when the service provider is used as a new service caller.
Optionally, in the RPC calling method for multiple tenants in the SaaS service mode, after the service caller initiates a call, the service caller monitors a return queue, and suspends other processing flows to wait for the return queue.
Optionally, in the RPC calling method for multiple tenants in the SaaS service mode, the service caller obtains namespace according to tenant information and application and adopts a centralized routing policy, including the following steps:
establishing a mapping relation between tenant information + application and namespace;
and customizing the tenant side to realize caching and immediate effect.
Optionally, in the RPC calling method for multiple tenants in the SaaS service mode, different mapping relationships are established according to whether the tenant version is personalized.
Optionally, in the RPC calling method for multiple tenants in the SaaS service mode, the RabbitMQ is set based on an AMQP protocol to provide a service registration function, a service discovery function, and a service routing function.
Optionally, in the RPC calling method for multiple tenants in the SaaS service mode, the RabbitMQ includes a complete operation and maintenance tool.
In the RPC calling method of the multi-tenant in the SaaS service mode, the RabbitMQ is adopted for RPC type selection as a basic component, and the RabbitMQ is used as a central node, so that basic RPC requirements of service registration, service discovery, service routing and the like can be met; meanwhile, the RabbitMQ also provides the function of supporting multiple tenants; the invention solves the RPC calling requirement under the multi-tenant scene with lower development and operation and maintenance cost.
Drawings
Fig. 1 is a flowchart of an RPC calling method for multiple tenants in a SaaS service mode according to an embodiment of the present invention.
Detailed Description
The following describes in more detail embodiments of the present invention with reference to the schematic drawings. The advantages and features of the present invention will become more apparent from the following description. It is to be noted that the drawings are in a very simplified form and are not to precise scale, which is merely for the purpose of facilitating and distinctly claiming the embodiments of the present invention.
Hereinafter, if the method includes a series of steps, and the order of such steps presented herein is not necessarily the only order in which such steps may be performed, some of the described steps may be omitted and/or some other steps not described herein may be added to the method.
For the inside of a SaaS software provider, as for a certain service function and flow, one function has a complete call chain, and when one SaaS software provider faces multiple tenants to acquire the service function and flow, the prior art generally adopts a vhost function, but the vhost function cannot completely meet the existing requirements, for example: firstly, binding the vhost with the connection, displaying configuration and creating a plurality of connections in an initialization stage, and adjusting configuration and restarting newly added tenants each time; secondly, the creation of the vhost must be displayed at the server, so that the maintenance cost is high; thirdly, versions of individual application tenants may be different, and separate instance deployment is required; finally, part of tenants have the requirement of sub-organization personalized services, and the vhost function cannot meet the requirement of the personalized services.
Therefore, it is necessary to provide a RPC calling method for multiple tenants in a SaaS service mode, where the RPC calling method is applied in a calling process inside a software provider, the software provider provides a service for one tenant once as a service thread, and the completion of one service thread requires calling functions of multiple function modules inside the software provider;
as shown in fig. 1, fig. 1 is a flowchart of a multi-tenant RPC calling method in a SaaS service mode according to an embodiment of the present invention, where the multi-tenant RPC calling method in the SaaS service mode includes the following steps:
setting tenant information in a service thread context by a current service calling party;
the service caller obtains namespace according to tenant information and application, and obtains a complete MQ queue name by combining the namespace and the service content of the tenant, wherein the application is an application ID (identity) of a service provider;
the service caller initiates calling according to the complete MQ queue name;
the RabbitMQ middleware carries out routing according to the complete MQ queue name to find a service provider;
the service provider monitors the complete MQ queue name, receives a calling request in the running process, and provides service and service processing according to the service content in the complete MQ queue name;
the RabbitMQ middleware carries out routing according to the complete MQ queue name, finds a service calling party, adds the service and service processing provided by the service provider into a return queue and returns the service calling party;
the service caller acquires and completes the processing of the service and the service processing in the return queue;
and the service calling party clears the information of the current tenant and completes one RPC calling.
In the invention, RPC type selection adopts RabbitMQ as a basic component and takes RabbitMQ as a central node, thus realizing the basic RPC requirements of service registration, service discovery, service routing and the like; meanwhile, the RabbitMQ also provides the function of supporting multiple tenants; the invention solves the RPC calling requirement under the multi-tenant scene with lower development and operation and maintenance cost.
Furthermore, the method introduces a namespace concept for the queue in a prefix mode on the basis of a RabbitMQ queue mode so as to distinguish different tenants. The queue adopts a memory mode and is created along with calling, and independent maintenance of operation and maintenance means is not needed. The queue definition mode may be as follows: and $ namespace, app1.func1.queue to achieve the purpose of distinguishing tenants. The prefix is determined by requesting context, and the specific setting mode refers to the description part of the subsequent context setting. The RabbitMQ queue uses the simplest queue mode, mainly avoids the complex routing rule to bring performance pressure to the MQ service end, and simultaneously avoids strong dependence on MQ and architecture level decoupling.
The terms in the present invention will be described in detail herein to clarify the meaning of the terms, SaaS: software as a Service, Software is a Service; tenant: a tenant, corresponding to an enterprise customer in this context; RPC: remote Procedure Call; provider: service provider in RPC; consumer: a service caller in RPC; RabbitMQ: message middleware, based on AMQP protocol settings; MQ: message Queue, the logical structure of the actual storage Message; context: the context is called, and some header information of the current call is generally saved, such as the tenant, the request id, and the like.
In general, in the invention, separate tenant information is created for each customer, and each tenant can enjoy complete software service functions.
Further, in the multi-tenant RPC calling method in the SaaS service mode, the service caller is a caller needing to call the function in the function module currently in the service thread, and the service provider is a provider providing the function in the function module currently in the service thread.
Typically, the tenant information and the service content of the tenant are acquired from an external gateway of a software provider. Each tenant has exclusive ownership of a gateway, and the gateway sets the unique identification of the tenant.
Further, in the RPC calling method for multiple tenants in the SaaS service mode, when the service caller initiates calling according to the complete MQ queue name, the method further includes the following steps: and the complete MQ queue name is arranged in a Header of the calling request information for transmission.
Optionally, in the RPC calling method for multiple tenants in the SaaS service mode, after the service provider receives a call request in an operation process, the method further includes the following steps:
and resolving Header information and setting the tenant information in the context of the service thread so as to distinguish the tenant when the service provider is used as a new service caller.
Specifically, before initiating a call, a service caller (Consumer) application obtains Tenant (Tenant) information of a service thread Context (Context) through RabbitMQ middleware, the Tenant (Tenant) information is used as a value of a queue namespace prefix, the Tenant (Tenant) information is spliced into a complete Message Queue (MQ) name, then call information is initiated through a rabbittemplate. In addition, the gateway application may also be a special Consumer.
Further, the service Provider (Provider) application monitors the corresponding message queue nouns by creating a simplemessagecontainerelistener object of the RabbitMQ, and processes the request of the Consumer; after receiving the request in the running process, the Provider firstly analyzes Header information and sets Tenant (Tenant) information in the Context of the service thread.
Preferably, the deployment of the service Provider (Provider) corresponds to a routing policy, and there are two cases:
application without personalized routing: using a shared instance, listening to a general queue (e.g., app1.func1. queue); application of personalized routing: with an exclusive instance, a particular queue (e.g., cust1.app1.func1.queue) is snooped. To meet the flexible requirement of "service sharing + monopolizing".
Preferably, in the RPC calling method for multiple tenants in the SaaS service mode, after the service caller initiates a call, the service caller monitors a return queue, and suspends other processing flows to wait for the return queue, so that the service caller can synchronize asynchronously.
Preferably, in the RPC calling method for multiple tenants in the SaaS service mode, the service caller obtains namespace according to tenant information and application and adopts a centralized routing policy, including the following steps:
establishing a mapping relation between tenant information + application and namespace;
and customizing the tenant side to realize caching and immediate effect.
Further, different mapping relationships are established according to whether the tenant version is personalized or not. For example: if not, mapping to a general queue, namely namespace is empty; if personalized, map to independent namespace. Therefore, the requirement that part of tenants have sub-organization personalized services is met.
Preferably, the RabbitMQ comprises a complete operation and maintenance tool, so that other operation and maintenance means are not needed for separate maintenance, and the operation and maintenance cost is reduced.
In conclusion, in the multi-tenant RPC calling method in the SaaS service mode, the RBC type selection adopts the RabbitMQ as a basic component, and the RabbitMQ is used as a central node, so that basic RPC requirements of service registration, service discovery, service routing and the like can be met; meanwhile, the RabbitMQ also provides the function of supporting multiple tenants; on the basis, the service routing of multiple tenants is realized through a self-development tenant routing framework, the multi-dimensional flexible requirements of service sharing + monopolizing, sub-organization/tenant and the like are met, and the RPC calling requirement under the multi-tenant scene is solved with low development and operation and maintenance cost.
The above description is only a preferred embodiment of the present invention, and does not limit the present invention in any way. It will be understood by those skilled in the art that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (10)
1.A multi-tenant RPC calling method in a SaaS service mode is characterized in that,
the RPC calling method is applied to the calling process inside a software provider, the software provider provides one service for one tenant as one service thread, and the completion of one service thread requires the calling of the functions of a plurality of function modules inside the software provider;
the RPC calling method of the multi-tenant in the SaaS service mode comprises the following steps:
setting tenant information in a service thread context by a current service calling party;
the service caller obtains namespace according to tenant information and application, and obtains a complete MQ queue name by combining the namespace and the service content of the tenant;
the service caller initiates calling according to the complete MQ queue name;
the RabbitMQ middleware carries out routing according to the complete MQ queue name to find a service provider;
the service provider monitors the complete MQ queue name, receives a calling request in the running process, and provides service and service processing according to the service content in the complete MQ queue name;
the RabbitMQ middleware carries out routing according to the complete MQ queue name, finds a service calling party, adds the service and service processing provided by the service provider into a return queue and returns the service calling party;
the service caller acquires and completes the processing of the service and the service processing in the return queue;
and the service calling party clears the information of the current tenant and completes one RPC calling.
2. The RPC calling method for multi-tenant in SaaS service mode as claimed in claim 1, wherein the service caller is a caller in the service thread that needs to call the function in the function module at present, and the service provider is a provider in the service thread that provides the function in the function module at present.
3. The RPC calling method for multi-tenant in SaaS service mode as claimed in claim 1, wherein the tenant information and service content of the tenant are obtained from an external gateway of a software provider.
4. The RPC calling method for multi-tenant in SaaS service mode as claimed in claim 1, wherein when the service caller initiates a call according to the complete MQ queue name, further comprising the steps of: and the complete MQ queue name is arranged in a Header of the calling request information for transmission.
5. The RPC calling method for multi-tenant in SaaS service mode as claimed in claim 1, wherein the service provider, after receiving a call request in a running process, further comprises the steps of:
and resolving Header information and setting the tenant information in the context of the service thread so as to distinguish the tenant when the service provider is used as a new service caller.
6. The RPC calling method for multi-tenant in SaaS service mode of claim 1, wherein after the service caller initiates a call, the service caller listens to a return queue and suspends other processing flow to wait for the return queue.
7. The RPC calling method of multi-tenant in SaaS service mode as claimed in claim 1, wherein the service caller obtains namespace according to tenant information and application and adopts a centralized routing policy, comprising the following steps:
establishing a mapping relation between tenant information + application and namespace;
and customizing the tenant side to realize caching and immediate effect.
8. The RPC calling method for multi-tenant in SaaS service mode as claimed in claim 7, wherein different mapping relationships are established according to whether the tenant version is personalized or not.
9. The RPC calling method for multi-tenancy in SaaS service mode as claimed in claim 1, wherein the RabbitMQ is set based on AMQP protocol to provide a service registration function, a service discovery function and a service routing function.
10. The RPC calling method for multi-tenancy in SaaS service mode of claim 9, wherein the RabbitMQ comprises a complete operation and maintenance tool.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010533970.3A CN111580998A (en) | 2020-06-12 | 2020-06-12 | RPC calling method of multiple tenants in SaaS service mode |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010533970.3A CN111580998A (en) | 2020-06-12 | 2020-06-12 | RPC calling method of multiple tenants in SaaS service mode |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111580998A true CN111580998A (en) | 2020-08-25 |
Family
ID=72110627
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010533970.3A Pending CN111580998A (en) | 2020-06-12 | 2020-06-12 | RPC calling method of multiple tenants in SaaS service mode |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111580998A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116016041A (en) * | 2023-01-04 | 2023-04-25 | 上海通联金融服务有限公司 | High-performance gateway design method applying self-registration |
| CN116743876A (en) * | 2023-08-14 | 2023-09-12 | 云筑信息科技(成都)有限公司 | Method for realizing multi-tenant scheduling based on xxl-job |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106549997A (en) * | 2015-09-22 | 2017-03-29 | 阿里巴巴集团控股有限公司 | The acquisition methods and device of user context information |
| CN106878473A (en) * | 2017-04-20 | 2017-06-20 | 腾讯科技（深圳）有限公司 | A kind of message treatment method, server cluster and system |
| CN108055298A (en) * | 2017-12-04 | 2018-05-18 | 泰康保险集团股份有限公司 | For the method and device of control message queue |
| CN108737325A (en) * | 2017-04-13 | 2018-11-02 | 华为技术有限公司 | A kind of multi-tenant data partition method, apparatus and system |
| CN108984316A (en) * | 2018-06-15 | 2018-12-11 | 广州视源电子科技股份有限公司 | Method and device for distributed data processing, electronic equipment and computer storage medium |
| CN109565511A (en) * | 2016-09-16 | 2019-04-02 | 甲骨文国际公司 | Tenant and service management for multi-tenant identity and data safety management cloud service |
| US20190349319A1 (en) * | 2018-05-08 | 2019-11-14 | Salesforce.Com, Inc. | Techniques for handling message queues |
| CN110968470A (en) * | 2018-09-28 | 2020-04-07 | 江苏赛融科技股份有限公司 | Operation and maintenance monitoring and aggregation management system |
-
2020
- 2020-06-12 CN CN202010533970.3A patent/CN111580998A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106549997A (en) * | 2015-09-22 | 2017-03-29 | 阿里巴巴集团控股有限公司 | The acquisition methods and device of user context information |
| CN109565511A (en) * | 2016-09-16 | 2019-04-02 | 甲骨文国际公司 | Tenant and service management for multi-tenant identity and data safety management cloud service |
| CN108737325A (en) * | 2017-04-13 | 2018-11-02 | 华为技术有限公司 | A kind of multi-tenant data partition method, apparatus and system |
| CN106878473A (en) * | 2017-04-20 | 2017-06-20 | 腾讯科技（深圳）有限公司 | A kind of message treatment method, server cluster and system |
| CN108055298A (en) * | 2017-12-04 | 2018-05-18 | 泰康保险集团股份有限公司 | For the method and device of control message queue |
| US20190349319A1 (en) * | 2018-05-08 | 2019-11-14 | Salesforce.Com, Inc. | Techniques for handling message queues |
| CN108984316A (en) * | 2018-06-15 | 2018-12-11 | 广州视源电子科技股份有限公司 | Method and device for distributed data processing, electronic equipment and computer storage medium |
| CN110968470A (en) * | 2018-09-28 | 2020-04-07 | 江苏赛融科技股份有限公司 | Operation and maintenance monitoring and aggregation management system |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116016041A (en) * | 2023-01-04 | 2023-04-25 | 上海通联金融服务有限公司 | High-performance gateway design method applying self-registration |
| CN116743876A (en) * | 2023-08-14 | 2023-09-12 | 云筑信息科技(成都)有限公司 | Method for realizing multi-tenant scheduling based on xxl-job |
| CN116743876B (en) * | 2023-08-14 | 2023-12-08 | 云筑信息科技(成都)有限公司 | Method for realizing multi-tenant scheduling based on xxl-job |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104734931B (en) | Link establishing method and device between a kind of virtual network function | |
| CN110262902B (en) | Information processing method and system, medium, and computing device | |
| US6591304B1 (en) | Dynamic, scaleable attribute filtering in a multi-protocol compatible network access environment | |
| WO2021129008A1 (en) | Service invocation method, apparatus and device, and medium | |
| CN110557357A (en) | remote procedure call protocol self-adaption method, related device and server | |
| CN102455936A (en) | Trunk quick allocation method | |
| CN112003961A (en) | Resource exposure method, system, equipment and medium in kubernets | |
| CN111010304A (en) | Method for integrating Dubbo service and Kubernetes system | |
| CN111770122B (en) | Service communication proxy SCP registration method, service calling method and network equipment | |
| CN111580998A (en) | RPC calling method of multiple tenants in SaaS service mode | |
| WO2020108443A1 (en) | Virtualization management method and device | |
| CN116155978A (en) | Multi-registry adaptation method, device, electronic equipment and storage medium | |
| US20060165119A1 (en) | Communicating between communications components having differing protocols absent component modifications | |
| CN112217845B (en) | Data transmission method based on Netconf protocol and related equipment | |
| US8739184B2 (en) | System and method for aggregating data from multiple sources to provide a single CIM object | |
| CN111309691A (en) | Data sharing exchange system and exchange method based on bus architecture | |
| CN110730197A (en) | Service discovery method and system | |
| CN116737662A (en) | Method, device, electronic equipment and storage medium for processing business data | |
| CN109413011A (en) | Public service resource application method, relevant device and system | |
| CN113742100B (en) | Service calling method, system, equipment and medium based on micro-service architecture | |
| CN113342457A (en) | Kubernetes scheduling method based on registration and discovery of Eureka service | |
| CN115883283A (en) | Deployment method and device of containerization VNF | |
| CN114244654A (en) | URL forwarding method, device, equipment and computer storage medium | |
| CN114020371A (en) | Dubbo-based generalization asynchronous calling method and device | |
| EP3040891A1 (en) | Method for providing information to determine a graph associated with a data item |
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 |
Application publication date: 20200825 |
|
| RJ01 | Rejection of invention patent application after publication |