TW201435609A - Method for asynchronously monitoring data change among multiple devices - Google Patents
Method for asynchronously monitoring data change among multiple devices Download PDFInfo
- Publication number
- TW201435609A TW201435609A TW102108404A TW102108404A TW201435609A TW 201435609 A TW201435609 A TW 201435609A TW 102108404 A TW102108404 A TW 102108404A TW 102108404 A TW102108404 A TW 102108404A TW 201435609 A TW201435609 A TW 201435609A
- Authority
- TW
- Taiwan
- Prior art keywords
- data
- change
- message queue
- client
- database
- Prior art date
Links
Landscapes
- Computer And Data Communications (AREA)
Abstract
Description
本發明係之多設備間資料異動非同步監控的方法，更一種用以非同步機制監控資料異動的技術，以在大量客戶端終端設備詢問請求資料是否異動，伺服器透過此非同步監控技術，能減低伺服器往資料庫查詢之工作負荷量，增加系統整體效能與穩定度。 The invention relates to a method for data movement and non-synchronization monitoring between multiple devices, and a technology for monitoring data movement by using a non-synchronous mechanism, so as to ask a large number of client terminal devices for request information to be changed, and the server transmits the asynchronous monitoring technology. It can reduce the workload of the server to query the database, and increase the overall efficiency and stability of the system.
一般而言，多個客戶端(Client)連線至一伺服器(Server)中，對伺服器發出請求，查詢其後端資料庫資料，多屬主從式架構，例如個人電腦中之瀏覽器，以網址連線至web伺服器，建立連線後，客戶端送出請求，伺服器根據客戶端請求之資料，至後端資料庫查詢並回應其結果，然後釋放其連線，客戶端即能在瀏覽器上看到網頁結果。但如果客戶端有N個，如第1圖所示，同時連線至伺服器送出請求時，則伺服器之應用程式10將同時執行對後端資料庫存取N次，並回應客戶端。依此架構下，勢必加重伺服器與後端資料庫之工作負荷，影響程度，輕則拖慢回應速度，重則使系統崩潰無法運作。 Generally speaking, multiple clients (Clients) are connected to a server (Server) to make a request to the server to query the data of the back-end database, which is mostly a master-slave architecture, such as a browser in a personal computer. After the connection is made to the web server by the website, after the connection is established, the client sends the request, and the server queries and responds to the result according to the data requested by the client, and then releases the connection, and the client can See web results on your browser. However, if there are N clients, as shown in Figure 1, when connecting to the server to send a request, the server application 10 will simultaneously execute the back-end data inventory N times and respond to the client. Under this framework, it is bound to increase the workload of the server and the back-end database, affecting the degree, and slow down the response speed, but the system crashes and cannot work.
有鑒於上述傳統主從式架構之缺點，本發明之目的在於提供 一種非同步監控資料異動的方法，使大量客戶端同時進行請求時，不會增加伺服器及後端資料庫之工作負荷量，限制對資料庫之存取連線數，伺服器不會因為客戶端連線數多而降低效能，後端資料庫亦因存取量限制而能穩定運作。 In view of the above disadvantages of the conventional master-slave architecture, the object of the present invention is to provide A method for asynchronously monitoring data changes, so that when a large number of clients make a request at the same time, the workload of the server and the back-end database is not increased, and the number of accesses to the database is limited, and the server is not used by the client. The number of end connections is large and the performance is reduced. The backend database is also stable due to access restrictions.
本發明之多設備間資料異動非同步監控的方法，係由資料讀取執行模組、多執行緒、訊息佇列及計時模組所組成，放置於該架構的應用伺服器中，該架構另包括客戶端終端設備、後端資料庫及外部異動資料源。 The method for data transmission and non-synchronization monitoring between multiple devices of the present invention is composed of a data reading execution module, a multi-thread, a message queue and a timing module, and is placed in an application server of the architecture, and the architecture is another Including client terminal equipment, back-end database and external transaction data sources.
本發明之多設備間資料異動非同步監控的方法，多設備即指客戶端終端設備，例如智慧型手機、平板電腦、智慧型電視等設備，當客戶自行於外部異動資料源更新資料，即寫入資料庫中，如何讓客戶其他設備知道資料異動與否，更進一步進行終端設備資料同步，為本發明之重要探討。 The method for monitoring data irregularity and non-synchronization between multiple devices of the present invention, the multi-device refers to a client terminal device, such as a smart phone, a tablet computer, a smart TV, etc., when the customer updates the data by itself, the external data source is written. In the database, how to let other equipment of the customer know whether the data is changed or not, and further synchronize the data of the terminal equipment, which is an important discussion of the invention.
其中，應用伺服器以非同步方法監控資料異動並回應客戶端，包括以下步驟：1)外部資料異動源隨時將異動資料寫入一資料庫中；2)客戶端終端設備與應用伺服器建立連線。例如智慧型手機資料推送(Push)功能，手機打開此功能後，隨時會與伺服器連線；3)伺服器之資料讀取執行模組接收終端設備請求之資料，放入訊息佇列中；4)多執行緒分別取出訊息佇列資料，先進先出，後進後出，並至後端資料庫中查詢資料異動與否；5)經資料庫查詢有異動，立即回應客戶端，並釋放其連線；6)若無異動，經計時模組設定的時間，若逾時，則回應客戶端無異動，並釋放該連線；若無逾時，則再次放入訊息佇列中，等待某執行緒取出執行。 The application server monitors the data transaction in an asynchronous manner and responds to the client, including the following steps: 1) the external data transaction source writes the transaction data to a database at any time; 2) the client terminal device establishes a connection with the application server. line. For example, the smart phone data push (Push) function, the mobile phone will open the function, it will be connected with the server at any time; 3) the server data read execution module receives the information requested by the terminal device, and puts it into the message queue; 4) Multiple threads respectively take out the message queue data, first-in, first-out, backward-in and out-out, and query the data in the back-end database for change or not; 5) respond to the database and respond to the client, and immediately release the client and release it. 6) If there is no change, if the time set by the timing module expires, the client will respond without change and release the connection; if there is no timeout, it will be placed in the message queue again, waiting for a certain The thread is taken out and executed.
週期主動連線無線基地台之行為，則拒絕該行動裝置之註冊登入。其中，更新媒體存取控制位址資訊暨連線時間儲存器中該行動裝置之連線時間，係將媒體存取控制位址資訊暨連線時間儲存器中儲存的時間更新為該行動裝置連線時間。 The active connection of the wireless base station during the cycle rejects the registration of the mobile device. The updating the media access control address information and the connection time of the mobile device in the connection time storage device updates the time stored in the media access control address information and the connection time storage to the mobile device connection Line time.
本發明之多設備間資料異動非同步監控的方法，係將多執行緒之個數固定，假設設定為L個執行緒，最大同時存取後端資料庫即為L個，亦即，不同於習知技術，伺服器存取資料庫次數，係根據客戶端終端設備數量成倍數成長，因此本發明在大量客戶端終端設備同時且多次對伺服器提出查詢資料異動與否之請求時，亦不會增加伺服器及後端資料庫之工作負荷量。 The method for data asynchronous monitoring between multiple devices of the present invention fixes the number of multiple threads, and assumes that it is set to L threads, and the maximum simultaneous access to the back-end database is L, that is, different from According to the prior art, the number of times the server accesses the database is multiplied according to the number of client terminal devices. Therefore, the present invention also applies a large number of client terminal devices to the server at the same time and repeatedly requests the server to change the data. Does not increase the workload of the server and back-end database.
一種多設備間資料異動非同步監控的方法，其非同步監控的方法之步驟如下：a.當一客戶端終端設備於資料更新時間，向一應用伺服器請求資料；b.該應用伺服器之一資料讀取執行模組接收該客戶端終端設備請求之資料，將資料放置於一訊息佇列中；以及c.一多執行緒各別且依序抓取該訊息佇列中之資料，並至一資料庫查詢是否異動，若有異動則立即回應該客戶端設備，並釋放其連線；若無異動，則再依一計時模組所設定之時間，超過時間，立即回應該客戶端設備，未超過時間，則將資料放該回訊息佇列中，等待下一執行緒再取出執行。 A method for asynchronous monitoring of data between multiple devices, the steps of the method for asynchronous monitoring are as follows: a. when a client terminal device requests data from an application server at a data update time; b. the application server a data reading execution module receives the data requested by the client terminal device, and places the data in a message queue; and c. a plurality of threads separately and sequentially captures the data in the message queue, and Check whether the database is changed. If there is any change, immediately return the client device and release the connection; if there is no change, then according to the time set by the timer module, exceed the time, immediately respond to the client device. If the time is not exceeded, put the data back into the message queue, wait for the next thread and then take it out.
其中，該資料係為一系列之同步資料命令訊息，更包含查詢資料異同之命令、新增事件之命令、刪除事件之命令、修改事件之命令， 其事件包括客戶端郵件、聯絡人以及行事曆。 The data is a series of synchronous data command messages, including commands for querying similarities and differences, commands for adding new events, commands for deleting events, and commands for modifying events. Events include client mail, contacts, and calendars.
其中，該方法設於一個人資訊管理系統。 Among them, the method is set in a person information management system.
其中，該應用伺服器更包括：該資料讀取執行模組執行該步驟b之接收客戶端設備之資料並放置於該訊息佇列的工作；以及該多執行緒執行該步驟c之抓取該訊息佇列中之資料，並連至該資料庫查詢，有異動則回應該客戶端設備，並釋放該連線；無異動，再根據該計時模組設定之時間，超過時間亦立即回應該客戶端設備，釋放該連線，未超過時間則再放回該訊息佇列中，等待下一次執行緒取出執行。 The application server further includes: the data reading execution module performs the step of receiving the data of the client device in the step b and placing the information in the queue of the message; and the multi-thread performs the step c to capture the The information in the message list is linked to the database for enquiry. If there is any change, the client device will be returned and the connection will be released. No change will be made. According to the time set by the timing module, the customer will be returned immediately after the time expires. The end device releases the connection. If the time is not exceeded, it is placed back in the message queue, waiting for the next thread to be taken out.
本發明所提供之多設備間資料異動非同步監控的方法，與其他習用技術相互比較時，更具備下列優點： The method for monitoring the asynchronous change of data between multiple devices provided by the invention has the following advantages when compared with other conventional technologies:
1.本發明因多執行緒設定為固定個數，亦即限制住最大同時存取後端資料庫數目，故能保證應用伺服器之高效能，與資料庫之穩定度。 1. The present invention is configured to set a fixed number of threads, that is, to limit the maximum number of simultaneous accesses to the back-end database, thereby ensuring the high performance of the application server and the stability of the database.
2.本發明資料讀取執行模組先將客戶端請求資料放置於訊息、佇列中，而訊息佇列之數量設定係根據隨機記憶體(RAM)大小，現今隨機記憶體成本低廉，一般安裝容量小為8GB，大至2TB，故應用伺服器能接收比傳統主從式架構更大量之客戶端請求；想反地，傳統主從式架構如要接收大量客戶端請求，因一連線產生一執行程序(process)處理，中央處理器產生的執行程序有限，勢必需增加伺服器數目，而本發明只需增加隨機記憶體容量，降低了營運成本。 2. The data reading execution module of the present invention first places the client request data in the message and the queue, and the number of the message queue is set according to the size of the random memory (RAM). Nowadays, the random memory is low in cost and generally installed. The capacity is as small as 8GB and as large as 2TB, so the application server can receive a larger number of client requests than the traditional master-slave architecture; contrary to the traditional master-slave architecture, if a large number of client requests are received, a connection is generated. As a result of processing, the central processor generates a limited number of execution programs, and it is necessary to increase the number of servers. However, the present invention only needs to increase the random memory capacity and reduce the operating cost.
上列詳細說明係針對本發明之一可行實施例之具體說明，惟該實施例並非用以限制本發明之專利範圍，凡未脫離本發明技藝精神所為 之等效實施或變更，均應包含於本案之專利範圍中。 The detailed description above is a detailed description of one of the possible embodiments of the present invention, which is not intended to limit the scope of the invention, which is not Equivalent implementations or changes shall be included in the scope of the patent in this case.
綜上所述，本案不但在空間型態上確屬創新，並能較習用物品增進上述多項功效，應已充分符合新穎性及進步性之法定發明專利要件，爰依法提出申請，懇請 貴局核准本件發明專利申請案，以勵發明，至感德便。 In summary, this case is not only innovative in terms of space type, but also can enhance the above-mentioned multiple functions compared with the customary items. It should fully meet the statutory invention patent requirements of novelty and progressiveness, and apply for it according to law. This invention patent application, in order to invent invention, to the sense of virtue.
1‧‧‧應用伺服器 1‧‧‧Application Server
2‧‧‧客戶端終端設備 2‧‧‧Client terminal equipment
3‧‧‧資料庫 3‧‧‧Database
4‧‧‧外部資料異動源 4‧‧‧External data sources
10‧‧‧應用程式 10‧‧‧Application
11‧‧‧資料讀取執行模組 11‧‧‧Data reading execution module
12‧‧‧訊息佇列 12‧‧‧Message queue
13‧‧‧多執行緒 13‧‧‧Multiple threads
14‧‧‧計時模組 14‧‧‧Time module
S31~S37‧‧‧步驟流程 S31~S37‧‧‧Step procedure
S1~S6‧‧‧步驟流程 S1~S6‧‧‧Step process
第1圖為習知主從式架構之資料異動同步監控方法的網路架構圖。 The first figure shows the network architecture diagram of the data synchronization synchronization monitoring method of the conventional master-slave architecture.
第2圖為本發明之多設備間資料異動非同步監控的方法之系統架構圖。 FIG. 2 is a system architecture diagram of a method for data asynchronous monitoring between multiple devices according to the present invention.
第3圖為本發明實施例所繪示之終端設備、應用伺服器與資料庫收發訊息步驟示意圖。 FIG. 3 is a schematic diagram of steps of transmitting and receiving messages by a terminal device, an application server, and a database according to an embodiment of the present invention.
第4圖為本發明多設備間資料異動非同步監控的方法之實施例運作流程圖。 FIG. 4 is a flow chart showing an operation of an embodiment of a method for data asynchronous monitoring between multiple devices according to the present invention.
為利 貴審查委員了解本發明之技術特徵、內容與優點及其所能達到之功效，茲將本發明配合附圖，並以實施例之表達形式詳細說明如下，而其中所使用之圖式，其主旨僅為示意及輔助說明書之用，未必為本發明實施後之真實比例與精準配置，故不應就所附之圖式的比例與配置關係解讀、侷限本發明於實際實施上的權利範圍，合先敘明。 The technical features, contents, and advantages of the present invention, as well as the advantages thereof, can be understood by the reviewing committee, and the present invention will be described in detail with reference to the accompanying drawings. The subject matter is only for the purpose of illustration and description. It is not intended to be a true proportion and precise configuration after the implementation of the present invention. Therefore, the scope and configuration relationship of the attached drawings should not be interpreted or limited. First described.
請參閱第2圖，用以顯示本發明之多設備間資料異動非同步 監控的方法的系統架構圖。如圖所示，該架構包括至少一應用伺服器1、多個用戶端終端設備2、後端資料庫3以及外部資料異動源4。該外部資料異動源4透過網路系統與後端資料庫3連結存取，其中，本實施例之非同步監控資料異動應用在個人資訊管理系統時，該外部資料異動源4也許為電腦之瀏覽器，透過瀏覽器更改其聯絡人、行事曆資料，使得後端資料庫之個人資料產生異動，故稱外部資料異動源4。 Please refer to FIG. 2 for showing the data transfer non-synchronization between multiple devices of the present invention. System architecture diagram of the method of monitoring. As shown, the architecture includes at least one application server 1, a plurality of client terminal devices 2, a backend database 3, and an external data transaction source 4. The external data source 4 is connected to the back-end database 3 through the network system. When the asynchronous monitoring data of the embodiment is applied to the personal information management system, the external data source 4 may be a computer browsing. The device changes its contact and calendar information through the browser, so that the personal data of the back-end database changes, so it is called the external data source.
續上之應用例，該客戶端設備可能不只一種，可能還包含智慧型手機、平板電腦等，此類之設備即如第2圖之終端設備2，當外部資料動源4改變資料庫3之資料，應用伺服器1如何即時且穩定地讓大量終端設備2知道資料異動，乃至更進一步進行資料同步，為本發明之探討重點。 In the application example, the client device may be more than one type, and may also include a smart phone, a tablet computer, etc., such a device is like the terminal device 2 in FIG. 2, when the external data source 4 changes the database 3 The information, how the application server 1 immediately and stably let a large number of terminal devices 2 know about data changes, and even further data synchronization, is the focus of the present invention.
該應用伺服器1係包括資料讀取執行模組11、訊息佇列12、多執行緒13以及計時模組14。客戶端終端設備2根據自行設定之時間，透過有線或無線網路系統與應用伺服器1建立連線，並發出請求，詢問資料異動與否，應用伺服器1之資料讀取執行模組11先將請求資料放入訊息佇列12之中，假設多執行緒設定為L個，依訊息佇列先進先取出、後進後取出之原則，依序取出請求資料至後端資料庫3詢問資料異動與否，假設資料有異動，立即回覆客戶端終端設備2，並釋放該連線；相反地，資料並無異動，再根據計時模組設定之逾時時間決定，逾時則回覆客戶端終端設備2，並釋放該連線，無逾時則放回訊息佇列12中，等待某一支執行緒13取出，再次執行詢問資料庫3，依此類推。 The application server 1 includes a data reading execution module 11, a message queue 12, a multi-thread 13, and a timing module 14. The client terminal device 2 establishes a connection with the application server 1 through a wired or wireless network system according to the time set by itself, and issues a request to request data change or not. The data reading execution module 11 of the application server 1 first Put the request data into the message queue 12, assuming that the multi-thread is set to L, according to the principle that the message is first taken out first, then taken in and then taken out, the request data is sequentially taken out to the back-end database 3 to ask for data change and No, if there is any change in the data, immediately reply to the client terminal device 2 and release the connection; on the contrary, the data is not changed, and then the timeout period determined by the timing module is determined, and the client terminal device 2 is replied to the timeout. And release the connection. If there is no timeout, put back the message queue 12, wait for a certain thread 13 to take out, execute the query database 3 again, and so on.
請參閱第3圖，其用以顯示第2圖之終端設備與應用伺服器，以及資料庫之間的運作關係。 Please refer to FIG. 3, which is used to display the operational relationship between the terminal device and the application server in FIG. 2, and the database.
首先，於步驟S31中，終端設備2與應用伺服器1建立連線。 First, in step S31, the terminal device 2 establishes a connection with the application server 1.
於步驟S32中，資料讀取執行模組11將請求資料放入訊息佇列12中。 In step S32, the material reading execution module 11 puts the request data into the message queue 12.
於步驟S33中，多執行緒13檢查訊息佇列12是否有值？ In step S33, the multi-thread 13 checks whether the message queue 12 has a value?
於步驟S34中，假設訊息佇列有值，多執行緒13依序取出執行。 In step S34, assuming that the message queue has a value, the multi-thread 13 sequentially fetches the execution.
於步驟S35中，多執行緒13根據取出訊息佇列12之資料，連線至後端資料庫3，詢問資料是否異動？ In step S35, the multi-thread 13 connects to the back-end database 3 according to the data of the message queue 12, and asks whether the data changes.
於步驟S361中，資料庫3回應資料有異動，立即回應該終端設備，並釋放該連線。 In step S361, the database 3 responds to the change of the data, immediately responds to the terminal device, and releases the connection.
於步驟S362中，資料庫3回應資料無異動，且超過計時模組14所設定時間，立即回應該終端設備，並釋放該連線。 In step S362, the database 3 responds to the data without any change, and exceeds the time set by the timing module 14, immediately responds to the terminal device, and releases the connection.
於步驟S37中，資料庫3回應資料無異動，且還沒超過計時模組14所設定時間，放回訊息佇列中。 In step S37, the database 3 responds to the data without any change, and has not exceeded the time set by the timing module 14, and puts it back into the message queue.
請參閱第4圖，其用以顯示第2圖之一實施例運作流程圖，亦以顯示第3圖之步驟S33至步驟S37間循環之流程。 Please refer to FIG. 4, which is a flowchart showing the operation of an embodiment of FIG. 2, and also shows the flow of the loop between step S33 and step S37 of FIG.
於步驟S1中，判斷訊息佇列是否有資料，若有資料，則繼續進行步驟S2，否則回到步驟S1。 In step S1, it is determined whether there is data in the message queue. If there is data, proceed to step S2, otherwise return to step S1.
於步驟S2中，每一執行緒分別且依序地取出訊息佇列之資料。 In step S2, each thread separately and sequentially extracts the data of the message queue.
於步驟S3中，至資料庫查詢資料是否異動？資料有異動，則繼續進行步驟S6，否則進行步驟S4。 In step S3, does the data query to the database change? If there is any change in the data, proceed to step S6, otherwise proceed to step S4.
於步驟S4中，超過計時模組設定之時間，則繼續進行步驟S6，否則進行步驟S5。 In step S4, if the time set by the timing module is exceeded, step S6 is continued, otherwise step S5 is performed.
於步驟S5中，回到步驟S1。 In step S5, the process returns to step S1.
於步驟S6中，回應客戶端終端設備，並釋放該連線。 In step S6, the client terminal device is responded to and the connection is released.
1‧‧‧應用伺服器 1‧‧‧Application Server
2‧‧‧客戶端終端設備 2‧‧‧Client terminal equipment
3‧‧‧資料庫 3‧‧‧Database
4‧‧‧外部資料異動源 4‧‧‧External data sources
11‧‧‧資料讀取執行模組 11‧‧‧Data reading execution module
12‧‧‧訊息佇列 12‧‧‧Message queue
13‧‧‧多執行緒 13‧‧‧Multiple threads
14‧‧‧計時模組 14‧‧‧Time module
Claims (4)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| TW102108404A TW201435609A (en) | 2013-03-11 | 2013-03-11 | Method for asynchronously monitoring data change among multiple devices |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| TW102108404A TW201435609A (en) | 2013-03-11 | 2013-03-11 | Method for asynchronously monitoring data change among multiple devices |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| TW201435609A true TW201435609A (en) | 2014-09-16 |
| TWI515575B TWI515575B (en) | 2016-01-01 |
Family
ID=51943360
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| TW102108404A TW201435609A (en) | 2013-03-11 | 2013-03-11 | Method for asynchronously monitoring data change among multiple devices |
Country Status (1)
| Country | Link |
|---|---|
| TW (1) | TW201435609A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI754561B (en) * | 2021-03-12 | 2022-02-01 | 中華電信股份有限公司 | Instant messaging system and method thereof and computer readable medium |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107292741B (en) * | 2017-07-24 | 2023-09-01 | ***股份有限公司 | Resource allocation method and device |
-
2013
- 2013-03-11 TW TW102108404A patent/TW201435609A/en not_active IP Right Cessation
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI754561B (en) * | 2021-03-12 | 2022-02-01 | 中華電信股份有限公司 | Instant messaging system and method thereof and computer readable medium |
Also Published As
| Publication number | Publication date |
|---|---|
| TWI515575B (en) | 2016-01-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109492040B (en) | System suitable for processing mass short message data in data center | |
| CN103390041B (en) | A kind of method and system that data, services is provided based on middleware | |
| WO2015192661A1 (en) | Method, device, and system for data synchronization in distributed storage system | |
| US20100106914A1 (en) | Consistency models in a distributed store | |
| CN107181787A (en) | A kind of request processing method and device | |
| US11650985B2 (en) | Caching techniques for a database change stream | |
| CN109743137B (en) | Distributed delay message queue processing system supporting updating | |
| CN103209223A (en) | Distributed application conversation information sharing method and system and application server | |
| CN105045607A (en) | Method for achieving uniform interface of multiple big data calculation frames | |
| CN102449602A (en) | System and method for reducing startup cost of a software application | |
| US11216346B2 (en) | Coordinated replication of heterogeneous database stores | |
| JP5686034B2 (en) | Cluster system, synchronization control method, server device, and synchronization control program | |
| CN110222119B (en) | Data conversion synchronization method, equipment and storage medium for heterogeneous database | |
| EP3722973A1 (en) | Data processing method and device for distributed database, storage medium, and electronic device | |
| EP4213038A1 (en) | Data processing method and apparatus based on distributed storage, device, and medium | |
| CN109614270A (en) | Data read-write method, device, equipment and storage medium based on Hbase | |
| CN112732756B (en) | Data query method, device, equipment and storage medium | |
| CN107800767A (en) | A kind of access response management method, server and computer-readable recording medium | |
| WO2020224098A1 (en) | Cloud access method and apparatus based on global server load balance, and storage medium | |
| WO2022218248A1 (en) | User portrait data processing method, apparatus, electronic device, and readable storage medium | |
| CN110489696A (en) | Buffering updating method, device and electronic equipment, storage medium | |
| TW201435609A (en) | Method for asynchronously monitoring data change among multiple devices | |
| CN107025257A (en) | A kind of transaction methods and device | |
| CN110866011A (en) | Data table synchronization method and device, computer equipment and storage medium | |
| CN108874472A (en) | A kind of the optimization display methods and system of user's head portrait |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| MM4A | Annulment or lapse of patent due to non-payment of fees |