TWI702540B - Load control method - Google Patents
Load control method Download PDFInfo
- Publication number
- TWI702540B TWI702540B TW108110145A TW108110145A TWI702540B TW I702540 B TWI702540 B TW I702540B TW 108110145 A TW108110145 A TW 108110145A TW 108110145 A TW108110145 A TW 108110145A TW I702540 B TWI702540 B TW I702540B
- Authority
- TW
- Taiwan
- Prior art keywords
- service
- partition
- business
- container
- service container
- Prior art date
Links
Images
Abstract
Description
本揭示文件係有關於一種控制方法,且特別是有關於一種負載的控制方法。 This disclosure relates to a control method, and particularly relates to a load control method.
網路軟體系統中,負載控制技術是被廣泛運用的技術。該技術可以根據實際需求對原有的功能進行水平拆分,將工作負載或任務分配到不同的程序、裝置或節點。 In network software systems, load control technology is a widely used technology. This technology can split the original functions horizontally according to actual needs, and assign workloads or tasks to different programs, devices or nodes.
以負載均衡技術為例,一般採用硬體方式來實現,例如以負載均衡裝置連接於多個伺服器,根據伺服器的資源使用狀況來動態分配任務。另一方面,採用軟體方式來實現負載均衡,例如Nginx,此方式已默認的輪詢和最少連接方式要求所有伺服器是無狀態的。然而,負載均衡裝置的價格昂貴,對業務量相對較低的企業來說,使用負載均衡裝置並非首選。此外,仰賴Nginx達成負載均衡的方式,在企業軟體(例如ERP)必須在設計之初就作到無狀態,否則將增加後續修改及維護成本,且要求各節點部署的內容完全一致。據此,如何有效率且降低成本地實現負載控制是亟需解決的問題。 Take load balancing technology as an example, which is generally implemented by hardware, for example, a load balancing device is connected to multiple servers, and tasks are dynamically allocated according to the resource usage of the servers. On the other hand, a software method is used to achieve load balancing, such as Nginx. This method has the default polling and least connection method requiring all servers to be stateless. However, load balancing devices are expensive, and for enterprises with relatively low business volume, using load balancing devices is not the first choice. In addition, relying on Nginx to achieve load balancing, enterprise software (such as ERP) must be stateless at the beginning of the design, otherwise it will increase subsequent modification and maintenance costs, and require that the content of each node deployment is completely consistent. Accordingly, how to efficiently and reduce the cost to achieve load control is an urgent problem to be solved.
發明內容旨在提供本揭示內容的簡化摘要,以使閱讀者對本揭示內容具備基本的理解。此發明內容並非本揭示內容的完整概述,且其用意並非在指出本發明實施例的重要/關鍵元件或界定本發明的範圍。 The content of the invention aims to provide a simplified summary of the disclosure so that readers have a basic understanding of the disclosure. This summary of the present invention is not a complete summary of the present disclosure, and its intention is not to point out important/key elements of the embodiments of the present invention or to define the scope of the present invention.
根據本揭示文件之一實施例,揭示一種負載控制方法。負載控制方法包含以下步驟:經由客戶端程序發出服務請求;讀取業務領域目錄,以解析資源標示;根據資源標示以在服務容器中搜尋,判斷是否有對應服務;以及當未搜尋到對應服務,則於業務分區容器中尋找對應服務,以讀取對應服務之業務分區並連接到業務分區之對應伺服器,以分散客戶端程序之服務請求及引起之伺服器負載。 According to an embodiment of the present disclosure, a load control method is disclosed. The load control method includes the following steps: sending a service request through the client program; reading the business domain directory to parse the resource label; searching in the service container according to the resource label to determine whether there is a corresponding service; and when the corresponding service is not found, Then search for the corresponding service in the business partition container to read the business partition of the corresponding service and connect to the corresponding server of the business partition to distribute the service request of the client program and the server load caused by it.
為讓本揭示內容之上述和其他目的、特徵、優點與實施例能更明顯易懂,所附符號之說明如下: In order to make the above and other objectives, features, advantages and embodiments of the present disclosure more comprehensible, the description of the attached symbols is as follows:
100‧‧‧帳務資料 100‧‧‧Accounting Information
110‧‧‧業務分區 110‧‧‧Business Division
111‧‧‧連接資訊 111‧‧‧Connection information
113‧‧‧業務分區標識 113‧‧‧Business zone identification
210‧‧‧業務領域目錄 210‧‧‧Business Field Directory
211‧‧‧功能點 211‧‧‧Function points
220‧‧‧服務容器 220‧‧‧Service Container
221‧‧‧資源標示 221‧‧‧Resource Marking
223‧‧‧執行業務分區 223‧‧‧Execute business division
300、400‧‧‧資源存取鏈路 300, 400‧‧‧ Resource Access Link
310、330、340、 310, 330, 340,
410、430、440、 410, 430, 440,
460‧‧‧一般服務容器 460‧‧‧General Service Container
320、420、450‧‧‧業務分區服務容器 320, 420, 450‧‧‧Business partition service container
390、490‧‧‧客戶端程序 390、490‧‧‧Client program
S510~S560‧‧‧步驟 S510~S560‧‧‧Step
以下詳細描述結合隨附圖式閱讀時,將有利於較佳地理解本揭示文件之態樣。應注意,根據說明上實務的需求,圖式中各特徵並不一定按比例繪製。實際上,出於論述清晰之目的,可能任意增加或減小各特徵之尺寸。 When the following detailed description is read in conjunction with the accompanying drawings, it will help to better understand the aspect of the present disclosure. It should be noted that, in accordance with the practical requirements of the description, the features in the diagram are not necessarily drawn to scale. In fact, for the purpose of clarity, the size of each feature may be increased or decreased arbitrarily.
第1圖繪示根據本揭示文件之一些實施例中的帳務資料之服務程序示意圖。 Figure 1 is a schematic diagram of the service procedure of accounting information in some embodiments according to the present disclosure.
第2圖繪示根據本揭示文件一些實施例中的客戶端程序加載業務領域目錄以及服務容器的示意圖。 FIG. 2 shows a schematic diagram of a client program loading a business domain directory and a service container according to some embodiments of the present disclosure.
第3圖繪示在本揭示文件一些實施例中之建立資源存取鏈路之示意圖。 Figure 3 shows a schematic diagram of establishing resource access links in some embodiments of the present disclosure.
第4圖繪示在本揭示文件另一些實施例中之建立資源存取鏈路示意圖。 Figure 4 shows a schematic diagram of establishing resource access links in other embodiments of the present disclosure.
第5圖繪示根據本揭示文件一些實施例中一種負載控制方法之流程示意圖。 FIG. 5 is a schematic flowchart of a load control method in some embodiments according to the present disclosure.
以下揭示內容提供許多不同實施例或實例,以便實施本發明之不同特徵。下文描述元件及排列之特定實例以簡化本發明。當然,該等實例僅為示例性且並不欲為限制性。舉例而言,以下描述中在第二特徵上方或第二特徵上形成第一特徵可包括以直接接觸形成第一特徵及第二特徵的實施例,且亦可包括可在第一特徵與第二特徵之間形成額外特徵使得第一特徵及特徵可不處於直接接觸的實施例。另外,本發明可在各實例中重複元件符號及/或字母。此重複係出於簡明性及清晰之目的,且本身並不指示所論述之各實施例及/或配置之間的關係。 The following disclosure provides many different embodiments or examples in order to implement different features of the present invention. Specific examples of elements and arrangements are described below to simplify the invention. Of course, these examples are only illustrative and not intended to be limiting. For example, in the following description, forming the first feature above or on the second feature may include an embodiment in which the first feature and the second feature are formed by direct contact, and may also include the embodiment where the first feature and the second feature are formed in direct contact. The formation of additional features between the features makes the first feature and the embodiment not in direct contact. In addition, the present invention may repeat element symbols and/or letters in each example. This repetition is for the purpose of conciseness and clarity, and does not in itself indicate the relationship between the various embodiments and/or configurations discussed.
進一步地,為了便於描述,本文可使用空間相對性術語(諸如「之下」、「下方」、「較低」、「上方」、「較高」及類似者)來描述諸圖中所圖示一個元件或特徵與另一元件(或多個元件)或特徵(或多個特徵)之關係。除了諸圖所描繪之定向外,空間相對性術 語意欲包含使用或操作中裝置之不同定向。設備可經其他方式定向(旋轉90度或處於其他定向上)且因此可同樣解讀本文所使用之空間相對性描述詞。 Further, for ease of description, spatially relative terms (such as "below", "below", "lower", "above", "higher" and the like may be used herein to describe the icons in the figures The relationship between one element or feature and another element (or elements) or feature (or features). In addition to the orientation depicted in the pictures, spatial relativity The term is intended to encompass the different orientations of the device in use or operation. The device can be oriented in other ways (rotated by 90 degrees or in other orientations) and therefore can also interpret the spatial relativity descriptors used herein.
請參照第1圖,其繪示根據本揭示文件之一些實施例中的帳務資料之服務程序示意圖。複數個帳務資料可以同時存在目標伺服器(未繪示),第1圖以其中一個帳務資料100的內容來作說明。如第1圖所示,帳務資料100包含業務分區110包含連接資訊111以及業務分區標識113。連接資訊111可以為記錄有關於業務分區的統一資源標示符(Uri,Uniform resource identifier)和有關於連接操作的相關資訊。業務分區標識113可以為用以標識業務資源分類,舉例來說,若為服務提供者,則標識113智能商業事件處理(SBEP)、報表伺服器(Report Server)。在一些實施例中,目標伺服器配置有帳務資料管理工具和/或文本編輯器,管理者可以透過帳務資料管理工具和/或文本編輯器來直接修改對應的帳務資料,例如在要進行負載均衡或業務水平拆分的目標伺服器的帳務資料中增加業務分區(Business Partition)。需注意的是,在本揭示文件中的「帳務資料」之用語,可與「帳套」交換地使用,係指有關於會計或財務等相關資料。
Please refer to FIG. 1, which illustrates a schematic diagram of the service procedure of accounting data in some embodiments of the present disclosure. A plurality of accounting data can be stored in the target server (not shown) at the same time. The content of one
在一實施例中,業務分區標識113包含標識以及通訊方式。業務分區標識經配置用以標識不同的業務資源分類,例如SBEP、Report Server等。通訊方式記錄客戶端程序(例如服務消費者或使用者)可以使用的通
訊技術來連接至服務端伺服器,舉例來說,網際網路位址(IP位址)、端口、安全標識、服務入口等資訊。
In one embodiment, the
對於客戶端程序,管理者可以透過設計工具或編輯工具,在業務領域目錄(例如MONITOR_EVENT)下定義客戶端程序。值得一提的是,在此所述的業務領域目錄可以為電腦作業系統中的資料夾之目錄,或者是虛擬資料夾的層次目錄。在一實施例中,目標伺服器透過接口(例如業務分區功能點(Business Partition Function Point))的方式提供客戶端程序來連接,而使得客戶端程序使用相關的服務。業務分區功能點(或簡稱功能點)包含唯一標識、服務端程序的業務分區標識以及服務端程序的名稱(例如應用程式介面(API)的名稱)。值得一提的是,在一個功能包(Function Package)中包含一或多個功能點,每一個功能點定義至少一功能或服務程序。因此,前述之每一個功能點的唯一標識在同一個功能包中是不可重複的。 For the client program, the manager can define the client program under the business domain directory (such as MONITOR_EVENT) through the design tool or the editing tool. It is worth mentioning that the business domain directory described here can be a directory of folders in a computer operating system, or a hierarchical directory of virtual folders. In one embodiment, the target server provides a client program to connect through an interface (such as a business partition function point), so that the client program uses related services. The service partition function point (or function point for short) includes a unique identifier, a service partition identifier of the server program, and the name of the server program (for example, the name of an application programming interface (API)). It is worth mentioning that one or more function points are included in a function package, and each function point defines at least one function or service program. Therefore, the unique identifier of each function point mentioned above cannot be repeated in the same function package.
在一實施例中,在目標伺服器啟動後,載入如第1圖所示之各個帳務資料100之業務分區110,以讀取各帳務資料100的配置,例如網際網路協定(IP)位址、端口、安全標示、服務入口等資料。目標伺服器將讀取到的資料,儲存於帳務資料模型中,完成目標伺服器的初始化程序。
In one embodiment, after the target server is started, the
在一實施例中,一或多個客戶端裝置通訊連接於目標伺服器。客戶端裝置啟動後,執行登入程序。
在登入的過程中,在目標伺服器上選擇帳務資料模型中的其中一個帳務資料100。
In one embodiment, one or more client devices are communicatively connected to the target server. After the client device is started, the login procedure is executed.
During the login process, one of the
接著,客戶端裝置解析帳務資料100,以建立服務請求程序。舉例來說,客戶端程序在帳務資料100中讀取業務分區110,並且建立業務分區110對應的資源連結資訊,如下表一所示。客戶端程序根據業務分區,讀取對應的資源連接資訊,以使用資源連接資訊所指示的服務請求程序。
Then, the client device parses the
請參照第2圖,其繪示根據本揭示文件一些實施例中的客戶端程序加載業務領域目錄210以及服務容器220的示意圖。如第2圖所示,客戶端程序讀取業務領域目錄210時,讀取業務領域目錄210的至少一功能包(未繪示),並讀取功能包的一或多個功能點211。功能點包含唯一標示以及業務分區標識。客戶端程序之解釋器(未繪示)解析各功能點211的內容。解析出功能點的內容後,將功能點211的相關資訊寫入服務容器220。
Please refer to FIG. 2, which illustrates a schematic diagram of the client program loading the
服務容器220包含資源標示221(Resource Key)以及執行業務分區223(Business Partition)。解釋器讀取功能點211,解析功能點211的內容。舉例來說,當
功能點211的唯一標識為“IPublishService”,則解釋器將“IPublishService”寫入資源標示221。在一實施例中,“IPublishService”代表功能點211是用來提供發布更新服務接口的功能。當功能點211的業務分區標識為“SBEP”,則解釋器將“SBEP”寫入執行業務分區223。
The
在一實施例中,當服務容器中的資源標示221記錄有關於業務分區的功能點之資料時,此服務容器屬於業務分區服務容器。在另一些實施例中,當服務容器中的資源標示221沒有記錄有關於業務分區的功能點之資料時,此服務容器屬於一般服務容器。其中,業務分區服務容器與一般服務容器都包含至少一功能點之資料。
In one embodiment, when the
請參照第3圖,其繪示在本揭示文件一些實施例中之建立資源存取鏈路300之示意圖。在第2圖之服務容器220建立之後,複數個服務容器可以建構為資源存取鏈路。如第3圖所示,客戶端程序390執行調用服務之程序,來取得服務資源。舉例來說,客戶端程序390執行統一的執行程序GetService(“MONITOR_EVENT”,typeof(IPublishService)),其中執行程序GetService()的第一個傳遞參數為業務領域,第二個傳遞參數為服務類型。
Please refer to FIG. 3, which shows a schematic diagram of establishing a
在一實施例中,服務容器可能存在或不存在符合傳遞參數之執行業務分區。如第3圖所示,客戶端程序390首先獲取執行程序的傳遞參數,並根據傳遞參
數在一般服務容器310中進行字典檢索比對。若檢索到對應至業務領域的傳遞參數,則客戶端程序390將對應的服務請求分配到指定的服務容器,即第3圖之業務分區服務容器320。接著,再以業務分區服務容器320之業務分區及資源連結資訊(如上表一),將運算資源或服務請求指示到對應的資源連接。在一實施例中,業務分區服務容器320將運算資源分配到一般服務容器330或一般服務容器340。在另一實施例中,若在一般服務容器310中未檢索到對應至業務領域的傳遞參數,則執行一般服務容器搜尋,並依據搜尋結果回傳服務資料。
In an embodiment, the service container may or may not have an execution service partition that meets the delivery parameters. As shown in Figure 3, the
請參照第4圖,其繪示在本揭示文件另一些實施例中之建立資源存取鏈路400示意圖。第4圖之資源存取鏈路400與第3圖之資源存取鏈路300間的差異為,第4圖之資源存取鏈路400包含一個以上的業務分區服務容器(例如業務分區服務容器420及業務分區服務容器450)。由於服務容器之間存在依存和/或調用順序,因此客戶端程序之服務請求程序可以在一或多個服務容器中分發。舉例來說,發布服務(例如“IPublishService”)被傳送到一般服務容器440,而在發布服務完成後調用日誌服務(ILogService),該服務在一般服務容器460。
Please refer to FIG. 4, which shows a schematic diagram of establishing a
請參照第5圖,其繪示根據本揭示文件一些實施例中一種負載控制方法之流程示意圖。以下說明請一併參照第2圖、第3圖及第5圖。在步驟S510中,客戶端裝置請求服務,例如發出“IPublishService”的服務請
求。在步驟S520中,客戶端程序讀取業務領域目錄210,建構服務容器220以解析出資源標示。在步驟S530中,客戶端程序根據資源標示在一般服務容器310中搜尋,以尋找是否有存在的對應服務。
Please refer to FIG. 5, which shows a schematic flow diagram of a load control method in some embodiments according to the present disclosure. Please refer to Figure 2, Figure 3 and Figure 5 for the following description. In step S510, the client device requests a service, for example, a service request of "IPublishService" is issued
begging. In step S520, the client program reads the
若服務無業務分區標識,則執行步驟S540,在一般服務容器310中尋找對應服務,客戶端程序在軟體系統(例如企業資源規劃系統(ERP))中執行一般服務容器搜尋,並回傳服務資源。
If the service does not have a business partition identifier, step S540 is executed to find the corresponding service in the
若服務有業務分區標識,則執行步驟S550,根據前述表一之業務分區及資源連結資訊,尋找應連接到對應的伺服器。接著,執行步驟S560,客戶端服務連接到對應業務分區與資源連結資訊的伺服器,並回傳服務資源。舉例來說,當業務分區為SBEP,則客戶端程序連接到SBEP伺服器。 If the service has a service partition identifier, step S550 is executed to find the corresponding server that should be connected to according to the service partition and resource link information in Table 1 above. Then, in step S560, the client service connects to the server corresponding to the service partition and resource connection information, and returns the service resource. For example, when the business partition is SBEP, the client program connects to the SBEP server.
綜上所述,本揭示文件揭露之負載控制方法提供簡單的配置手段,不需要購買昂貴的硬體設備(例如F5設備)即可均衡分配網路中的負載。此外,本負載控制方法不需要修改現有的功能代碼,並且對於開發人員來說是容易學習的。只要開發人員理解功能包與功能點的技術,即可以實施。此外,本負載控制方法提供任意粒度(granularity)的設計,支援業務水平拆分,因而可提供高延展性的負載均衡運算。 In summary, the load control method disclosed in the present disclosure provides a simple configuration method, and does not need to purchase expensive hardware equipment (such as F5 equipment) to balance the load in the network. In addition, the load control method does not need to modify the existing function codes, and it is easy for developers to learn. As long as the developer understands the technology of the function package and function point, it can be implemented. In addition, the load control method provides a design of arbitrary granularity, supports business level splitting, and thus can provide highly scalable load balancing operations.
上文概述若干實施例之特徵,使得熟習此項技術者可更好地理解本發明之態樣。熟習此項技術者應 瞭解,可輕易使用本發明作為設計或修改其他製程及結構的基礎,以便實施本文所介紹之實施例的相同目的及/或實現相同優勢。熟習此項技術者亦應認識到,此類等效結構並未脫離本發明之精神及範疇,且可在不脫離本發明之精神及範疇的情況下產生本文的各種變化、替代及更改。 The features of several embodiments are summarized above so that those skilled in the art can better understand the aspects of the present invention. Those familiar with this technique should It is understood that the present invention can be easily used as a basis for designing or modifying other processes and structures, so as to implement the same purpose and/or achieve the same advantages of the embodiments described herein. Those familiar with the art should also realize that such equivalent structures do not depart from the spirit and scope of the present invention, and various changes, substitutions and alterations herein can be made without departing from the spirit and scope of the present invention.
300‧‧‧資源存取鏈路 300‧‧‧Resource Access Link
310‧‧‧一般服務容器 310‧‧‧General Service Container
320‧‧‧業務分區服務容器 320‧‧‧Business partition service container
330‧‧‧一般服務容器 330‧‧‧General Service Container
340‧‧‧一般服務容器 340‧‧‧General Service Container
390‧‧‧客戶端程序 390‧‧‧Client Program
Claims (10)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
TW108110145A TWI702540B (en) | 2019-03-22 | 2019-03-22 | Load control method |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
TW108110145A TWI702540B (en) | 2019-03-22 | 2019-03-22 | Load control method |
Publications (2)
Publication Number | Publication Date |
---|---|
TWI702540B true TWI702540B (en) | 2020-08-21 |
TW202036286A TW202036286A (en) | 2020-10-01 |
Family
ID=73003181
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
TW108110145A TWI702540B (en) | 2019-03-22 | 2019-03-22 | Load control method |
Country Status (1)
Country | Link |
---|---|
TW (1) | TWI702540B (en) |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050192899A1 (en) * | 2004-02-26 | 2005-09-01 | Reardon David C. | Financial transaction system with integrated electronic messaging, control of marketing data, and user defined charges for receiving messages |
TW200644540A (en) * | 2005-01-21 | 2006-12-16 | Raza Microelectronics Inc | System and method for performing local center authorization service in a network |
US20110040892A1 (en) * | 2009-08-11 | 2011-02-17 | Fujitsu Limited | Load balancing apparatus and load balancing method |
CN103414649A (en) * | 2013-07-26 | 2013-11-27 | 中国科学院计算技术研究所 | Method and system for implementing distributed load generators |
TW201613408A (en) * | 2014-09-26 | 2016-04-01 | Apple Inc | Network bandwidth sharing for mobile devices |
TW201643765A (en) * | 2015-02-04 | 2016-12-16 | 英特爾公司 | Technologies for scalable security architecture of virtualized networks |
-
2019
- 2019-03-22 TW TW108110145A patent/TWI702540B/en active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050192899A1 (en) * | 2004-02-26 | 2005-09-01 | Reardon David C. | Financial transaction system with integrated electronic messaging, control of marketing data, and user defined charges for receiving messages |
TW200644540A (en) * | 2005-01-21 | 2006-12-16 | Raza Microelectronics Inc | System and method for performing local center authorization service in a network |
US20110040892A1 (en) * | 2009-08-11 | 2011-02-17 | Fujitsu Limited | Load balancing apparatus and load balancing method |
CN103414649A (en) * | 2013-07-26 | 2013-11-27 | 中国科学院计算技术研究所 | Method and system for implementing distributed load generators |
TW201613408A (en) * | 2014-09-26 | 2016-04-01 | Apple Inc | Network bandwidth sharing for mobile devices |
TW201643765A (en) * | 2015-02-04 | 2016-12-16 | 英特爾公司 | Technologies for scalable security architecture of virtualized networks |
Also Published As
Publication number | Publication date |
---|---|
TW202036286A (en) | 2020-10-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11711420B2 (en) | Automated management of resource attributes across network-based services | |
US20210073051A1 (en) | Late connection binding for bots | |
US9069438B2 (en) | Allocating virtual machines according to user-specific virtual machine metrics | |
CN107003906B (en) | Type-to-type analysis of cloud computing technology components | |
US10715388B2 (en) | Using a container orchestration service for dynamic routing | |
US7730183B2 (en) | System and method for generating virtual networks | |
US9420034B2 (en) | Providing services to multiple tenants of an application | |
US11734053B2 (en) | Attribute-based access control using a dynamic expression engine | |
US7761527B2 (en) | Method and apparatus for discovering network based distributed applications | |
US20130254761A1 (en) | Granular application sessions tagging | |
US10922357B1 (en) | Automatically mapping natural language commands to service APIs | |
US20110166952A1 (en) | Facilitating dynamic construction of clouds | |
JP2013541069A (en) | Method, service registry, and computer program for service deployment from a service registry | |
US11086827B1 (en) | Dataset schema and metadata management service | |
US10182104B1 (en) | Automatic propagation of resource attributes in a provider network according to propagation criteria | |
Blake et al. | Workflow composition of service level agreements for web services | |
CN111752681A (en) | Request processing method, device, server and computer readable storage medium | |
US8984124B2 (en) | System and method for adaptive data monitoring | |
US11100233B2 (en) | Optimizing operating system vulnerability analysis | |
US11546307B2 (en) | Method to implement multi-tenant/shared Redis cluster using envoy | |
TWI702540B (en) | Load control method | |
CN111800511A (en) | Processing method, system, equipment and readable storage medium for synchronous login state | |
CN113722114A (en) | Data service processing method and device, computing equipment and storage medium | |
US20230114321A1 (en) | Cloud Data Ingestion System | |
US11876729B2 (en) | Method and system for a proactive assignment of virtual network functions in local data systems |