System and method for packet transmission using segment routing
View Patent ↗Embodiments enable clients to have read-write access to a stream where all other clients are aware of all changes being made to the stream. A pravega node can track the data that has been written to the stream. The clients can dynamically read the stream. A client among the clients can update the stream by sending a request to the pravega node that includes the update and a total length of the stream that was written to the stream at the time of the last read update by the client. If the total length of the stream received from the client matches the actual length of the stream maintained by the pravega node, the pravega node will update the stream. If not, a failure message can be sent to the client and the client can process more reads to the stream before making another attempt to update the stream.
1. A method comprising:
accessing a shared state stream by a set of client applications;
reading data from the shared state stream by the set of client applications;
determining an update to the shared state stream by an update client application among the set of client applications, wherein determining the update includes monitoring a rate of data input into the shared state stream and determining the Service Level Objective (SLO) of the shared state stream;
determining a stream length of the shared state stream by the update client application based on the reading;
sending the update and the stream length by the update client application to a pravega node;
receiving the update and the stream length by the pravega node;
determining an actual stream length by the pravega node;
in response to the stream length matching the actual stream length, modifying the shared state stream based on the update;
in response to the stream length not matching the actual stream length, sending a fail message to the update client application by the pravega node;
in response to receiving the fail message, reading data from the shared state stream by the update client application;
updating the stream length based on the reading; and
sending the update and the stream length by the update client application to the pravega node.
2. The method of claim 1 , wherein modifying the stream includes appending the update to an end of the shared state stream and modifying a set of metadata associated with the shared state stream to reference the update.
3. The method of claim 1 , further comprising:
in response to modifying the shared state stream based on the update, reading the modified shared state stream by the set of client applications.
4. The method of claim 1 , wherein the client applications among the set of client applications include a common pravega client library.
5. A system comprising:
at least one storage device and at least one hardware processor configured to:
access a shared state stream by a set of client applications;
read data from the shared state stream by the set of client applications;
determine an update to the shared state stream by an update client application among the set of client applications, wherein determining the update includes monitoring a rate of data input into the shared state stream and determining the Service Level Objective (SLO) of the shared state stream;
determine a stream length of the shared state stream by the update client application based on the reading;
send the update and the stream length by the update client application to a pravega node;
receive the update and the stream length by the pravega node;
determine an actual stream length by the pravega node;
in response to the stream length matching the actual stream length, modify the shared state stream based on the update;
in response to the stream length not matching the actual stream length, send a fail message to the update client application by the pravega node;
in response to receiving the fail message, read data from the shared state stream by the update client application;
update the stream length based on the reading; and
send the update and the stream length by the update client application to the pravega node.
6. The system of claim 5 , wherein modifying the shared state stream includes appending the update to an end of the shared state stream and modifying a set of metadata associated with the shared state stream to reference the update.
7. The system of claim 5 , further configured to:
in response to modifying the shared state stream based on the update, read the modified shared state stream by the set of client applications.
8. The system of claim 5 , wherein the client applications among the set of client applications include a common pravega client library.
9. A non-transitory computer readable medium with program instructions stored thereon, when executed by a processor, cause the processor to perform the following acts:
accessing a shared state stream by a set of client applications;
reading data from the shared state stream by the set of client applications;
determining an update to the shared state stream by an update client application among the set of client applications, wherein determining the update includes monitoring a rate of data input into the shared state stream and determining the Service Level Objective (SLO) of the shared state stream;
determining a stream length of the shared state stream by the update client application based on the reading;
sending the update and the stream length by the update client application to a pravega node;
receiving the update and the stream length by the pravega node;
determining an actual stream length by the pravega node;
in response to the stream length matching the actual stream length, modifying the shared state stream based on the update;
in response to the stream length not matching the actual stream length, sending a fail message to the update client application by the pravega node;
in response to receiving the fail message, reading data from the shared state stream by the update client application;
updating the stream length based on the reading; and
sending the update and the stream length by the update client application to the pravega node.
10. The non-transitory computer readable medium of claim 9 , wherein modifying the shared state stream includes appending the update to an end of the shared state stream and modifying a set of metadata associated with the shared state stream to reference the update.
11. The non-transitory computer readable medium of claim 9 , with program instructions stored thereon to further perform the following acts:
in response to modifying the shared state stream based on the update, reading the modified shared state stream by the set of client applications.
12. The non-transitory computer readable medium of claim 9 , wherein the client applications among the set of client applications include a common pravega client library.