Database Offload with Node-to-Node Communication

Patent metadata

Field	Value
Publication number	US-2025392640-A1
Application number	US-202418749340-A
Country	US
Kind code	A1
Filing date	Jun 20, 2024
Priority date	Jun 20, 2024
Publication date	Dec 25, 2025
Grant date	—

Abstract

An example embodiment may involve conducting, by an application node, an operation with a database node, wherein the application node and the database node are both within a computational instance of nodes; transmitting, by the application node and to each of a plurality of destination application nodes, a message relating to the operation, wherein the plurality of destination application nodes are also within the computational instance of nodes; and updating, by each of the plurality of destination application nodes, respective local storage of data relating to the operation.

First claim

What is claimed is:

1 . A method comprising:
conducting, by an application node, an operation with a database node, wherein the application node and the database node are both within a computational instance of nodes; transmitting, by the application node and to each of a plurality of destination application nodes, a message relating to the operation, wherein the plurality of destination application nodes are also within the computational instance of nodes; and updating, by each of the plurality of destination application nodes, respective local storage of data relating to the operation.

2 . The method of claim 1 , wherein the operation is a read of the data from the database node, and wherein the message contains a representation of the data.

3 . The method of claim 2 , wherein reception of the message containing the representation of the data causes the plurality of destination application nodes to use their respective local storage of the data for a period of time rather than read the data from the database node.

4 . The method of claim 1 , wherein the operation is a write of the data to the database node, and wherein the message contains a flush instruction.

5 . The method of claim 4 , wherein reception of the message containing the flush instruction causes the plurality of destination application nodes to delete their respective local storage of the data.

6 . The method of claim 1 , wherein the operation is a write of the data to the database node, and wherein the message contains a representation of the data.

7 . The method of claim 6 , wherein reception of the message containing the representation of the data causes the plurality of destination application nodes to use their respective local storage of the data for a period of time rather than read the data from the database node.

8 . The method of claim 1 , wherein the application node is in communication with each of the plurality of destination application nodes by way of respective WebSockets connections.

9 . The method of claim 1 , wherein transmitting the message relating to the operation comprises:
transmitting, by the application node and to a load balancer, respective copies of the message for each of the plurality of destination application nodes; and transmitting, by the load balancer and to each of the plurality of destination application nodes, the respective copies of the message.

10 . The method of claim 1 , wherein the application node comprises:
one or more applications; a messaging interface through which the one or more applications can communicate with the plurality of destination application nodes; a transport module including channels between the application node and each of the plurality of destination application nodes; and an outbound message processing module including outbound worker threads that route messages from the messaging interface to the plurality of destination application nodes.

11 . The method of claim 10 , wherein the application node also comprises:
an inbound message processing module including inbound worker threads that route messages from the plurality of destination application nodes to the one or more applications.

12 . The method of claim 1 , wherein the application node and the plurality of destination application nodes also communicate with one another by way of a cache stored in the database node that maintains information that is synchronized between the application node and the plurality of destination application nodes.

13 . A non-transitory computer-readable medium, having stored thereon program instructions that, upon execution by a computing system, cause the computing system to perform steps comprising:
conducting, by an application node, an operation with a database node, wherein the application node and the database node are both within a computational instance of nodes; transmitting, by the application node and to each of a plurality of destination application nodes, a message relating to the operation, wherein the plurality of destination application nodes are also within the computational instance of nodes; and updating, by each of the plurality of destination application nodes, respective local storage of data relating to the operation.

14 . The non-transitory computer-readable medium of claim 13 , wherein the operation is a read of the data from the database node, wherein the message contains a representation of the data, and wherein reception of the message containing the representation of the data causes the plurality of destination application nodes to use their respective local storage of the data for a period of time rather than read the data from the database node.

15 . The non-transitory computer-readable medium of claim 13 , wherein the operation is a write of the data to the database node, wherein the message contains a flush instruction, and wherein reception of the message containing the flush instruction causes the plurality of destination application nodes to delete their respective local storage of the data.

16 . The non-transitory computer-readable medium of claim 13 , wherein transmitting the message relating to the operation comprises:
transmitting, by the application node and to a load balancer, respective copies of the message for each of the plurality of destination application nodes; and transmitting, by the load balancer and to each of the plurality of destination application nodes, the respective copies of the message.

17 . The non-transitory computer-readable medium of claim 13 , wherein the application node comprises:
one or more applications; a messaging interface through which the one or more applications can communicate with the plurality of destination application nodes; a transport module including channels between the application node and each of the plurality of destination application nodes; and an outbound message processing module including outbound worker threads that route messages from the messaging interface to the plurality of destination application nodes.

18 . The non-transitory computer-readable medium of claim 17 , wherein the application node also comprises:
an inbound message processing module including inbound worker threads that route messages from the plurality of destination application nodes to the one or more applications.

19 . The non-transitory computer-readable medium of claim 13 , wherein the application node and the plurality of destination application nodes also communicate with one another by way of a cache stored in the database node that maintains information that is synchronized between the application node and the plurality of destination application nodes.

20 . A system comprising:
one or more processors; and memory, containing program instructions that, upon execution by the one or more processors, cause the system to perform steps comprising:
conducting, by an application node, an operation with a database node, wherein the application node and the database node are both within a computational instance of nodes;
transmitting, by the application node and to each of a plurality of destination application nodes, a message relating to the operation, wherein the plurality of destination application nodes are also within the computational instance of nodes; and
updating, by each of the plurality of destination application nodes, respective local storage of data relating to the operation.

Assignees

• Servicenow Inc

Inventors

• Barron-Kraus Kyle
• Fiorelli Benedetto
• Misra Vinamra
• Maturi Shasank
• Jain Kavish
• Milton André Michel

Classifications

• H04L67/568

  Storing data temporarily at an intermediate stage, e.g. caching · CPC title

• H04L67/1097 Primary

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

• G06F16/27 Primary

  Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title