Adaptively updating databases of publish and subscribe systems using optimistic updates

Patent metadata

Field	Value
Publication number	US-11526499-B2
Application number	US-201916278186-A
Country	US
Kind code	B2
Filing date	Feb 18, 2019
Priority date	Feb 18, 2019
Publication date	Dec 13, 2022
Grant date	Dec 13, 2022

Abstract

An example system includes a processor to receive updates for a database of a publish and subscribe system. The processor is to generate an optimistic update based on the received updates. The processor is also to adaptively update the database using the optimistic update. In some examples, the processor generates a bulk optimistic update based on the optimistic update and adaptively updates the database using the bulk optimistic update or a read-modify-write sequence.

First claim

What is claimed is:

1. A system for tracking client connectivity in publish and subscribe systems, comprising a processor to:
receive client status updates for a database coupled to a plurality of decoupled servers forming a distributed broker of a publish and subscribe system, wherein each of the decoupled servers sends an update to the database in response to a client connecting or disconnecting, and wherein the plurality of decoupled servers are decoupled with respect to each other;
generate an optimistic update based on the received client status updates, wherein each of the client status updates comprise connectivity information of a client that is to be routed to a server of the plurality of decoupled servers of the publish and subscribe system based on a load balancing scheme in response to a connection request from the client, wherein generating the optimistic update comprises reducing a read-modify-write sequence of a received client status update to a conditional update that uses a find-and-modify operation comprising selecting a record with a particular client ID and particular client status within a client status table of the database and updating the client status field to the particular client status and incrementing a last update field to a new value; and
adaptively update the database using the optimistic update based on an estimated optimistic update failure rate or the read-modify-write sequence based on the estimated optimistic update failure rate.

2. The system of claim 1 , wherein the optimistic update comprises a bulk optimistic update.

3. The system of claim 2 , wherein the processor is to update the database using the bulk optimistic update in response to detecting that the estimated optimistic update failure rate does not exceed a threshold rate.

4. The system of claim 1 , wherein the processor is to update the database using an individual read-modify-write operation in response to detecting the estimated optimistic update failure rate exceeds a threshold rate.

5. The system of claim 1 , wherein the processor is to monitor a rate of optimistic update failures and estimate the estimated optimistic update failure rate.

6. The system of claim 5 , wherein the processor is to estimate the estimated optimistic update failure rate based on a sliding window of a predetermined amount of time.

7. The system of claim 5 , wherein the processor is to execute the optimistic update using the find-and-modify operation.

8. A computer-implemented method, comprising:
receiving, via a processor, client status updates for a database coupled to a plurality of decoupled servers forming a distributed broker of a publish and subscribe system, wherein each of the client status updates comprise connectivity information of a client that is to be routed to a server of the plurality of decoupled servers of the publish and subscribe system based on a load balancing scheme in response to a connection request from the client, wherein each of the decoupled servers sends an update to the database in response to a client connecting or disconnecting, and wherein the plurality of decoupled servers are decoupled with respect to each other;
generating, via the processor, an optimistic update based on the received client status updates, wherein generating the optimistic update comprises reducing a read-modify-write sequence of a received client status update to a conditional update comprising a find-and-modify operation comprising selecting a record with a particular client ID and particular client status within a client status table of the database and updating the client status field to the particular client status and incrementing a last update field to a new value; and
adaptively updating, via the processor, the database using the optimistic update based on an estimated optimistic update failure rate or the read-modify-write sequence based on the estimated optimistic update failure rate.

9. The computer-implemented method of claim 8 , wherein generating the optimistic update comprises generating a bulk optimistic update including the optimistic update.

10. The computer-implemented method of claim 9 , comprising updating the database using the bulk optimistic update in response to detecting that the estimated optimistic update failure rate does not exceed a threshold rate.

11. The computer-implemented method of claim 8 , comprising updating the database using an individual read-modify-write operation in response to detecting the estimated optimistic update failure rate exceeds a threshold rate.

12. The computer-implemented method of claim 8 , comprising monitoring a rate of optimistic update failures and estimating the estimated optimistic update failure rate.

13. The computer-implemented method of claim 12 , wherein estimating the estimated optimistic update failure rate is based a sliding window of a predetermined number of bulk updates or transactions.

14. The computer-implemented method of claim 8 , wherein updating the database using the optimistic update comprises using the find-and-modify operation.

15. A computer program product for tracking client connectivity in publish and subscribe systems, the computer program product comprising a computer-readable storage medium having program code embodied therewith the program code executable by a processor to cause the processor to:
receive client status updates for a database coupled to a plurality of decoupled servers forming a distributed broker of a publish and subscribe system, wherein each of the client status updates comprise connectivity information of a client that is to be routed to a server of the plurality of decoupled servers of the publish and subscribe system based on a load balancing scheme in response to a connection request from the client, wherein each of the decoupled servers sends an update to the database in response to a client connecting or disconnecting, and wherein the plurality of decoupled servers are decoupled with respect to each other;
generate optimistic updates based on the received client status updates, wherein generating the optimistic updates comprises reducing a read-modify-write sequence of a received client status update to a conditional update comprising a find-and-modify operation comprising selecting a record with a particular client ID and particular client status within a client status table of the database and updating the client status field to the particular client status and incrementing a last update field to a new value;
generate a bulk optimistic update based on the optimistic updates; and
adaptively update the database using the bulk optimistic update based on an estimated optimistic update failure rate or the read-modify-write sequence based on the estimated optimistic update failure rate, wherein the processor is to update the database using the bulk optimistic update in response to detecting that the estimated optimistic update failure rate does not exceed a first threshold rate.

16. The computer program product of claim 15 , further comprising program code executable by the processor to update the database using an individual read-modify-write operation in response to detecting the estimated optimistic update failure rate exceeds a second threshold rate.

17. The computer program product of claim 15 , further comprising program code executable by the processor to monitor a rate of optimistic update failures and estimate the estimated optimistic update failure rate.

18. The computer program product of claim 15 , further comprising program code executable by the processor t

Assignees

• IBM

Inventors

• Tock Yoav
• Naaman Nir
• Harpaz Avraham

Classifications

• G06F16/2322 Primary

  using timestamps · CPC title

• G06F16/2386 Primary

  Bulk updating operations (data conversion details G06F16/258) · CPC title