Systems and methods for improving data stream continuity with an endpoint mapper updated with predicted addresses of a later-provisioned data-streaming cluster
Abstract
The system may obtain a first data stream generated by a first set of endpoints from a first set of addresses for the first set of endpoints, wherein the mapper maps the first set of addresses to a set of stable addresses. The system may update the mapper to map a set of stable addresses to a set of anticipated addresses by predicting the set of anticipated addresses for a second set of endpoints based on a history of endpoint addresses. The system may provision the second set of endpoints, wherein provisioning the second set of endpoints comprising generating a second set of addresses for the second set of endpoints, wherein the second set of addresses matches with the set of anticipated addresses. The system may obtain a second data stream generated by the second set of endpoints.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A system for improving data stream continuity with an endpoint mapper by updating the endpoint mapper with predicted addresses of a later-provisioned data-streaming cluster, the system comprising:
one or more processors; and one or more machine-readable memory storing program instructions that, when executed by the one or more processors, performs operations comprising:
obtaining, at the endpoint mapper, a first data stream generated by first nodes of a first computing cluster from a first set of node addresses for the first nodes, wherein the endpoint mapper maps the first set of node addresses to a set of stable client-facing addresses;
streaming the first data stream from the set of stable client-facing addresses of the endpoint mapper to a set of client addresses adapted to data format used in the first data stream and a later data stream;
updating the endpoint mapper to map the set of stable client-facing addresses to a set of anticipated addresses by predicting the set of anticipated addresses for second nodes of a second computing cluster that is not yet provisioned based on a history of endpoint addresses;
provisioning the second computing cluster, the provisioning causing a creation of a second set of node addresses for the second nodes, wherein the second set of node addresses matches with the set of anticipated addresses;
obtaining, at the endpoint mapper, a second data stream generated by the second nodes of the provisioned second computing cluster; and
streaming the second data stream from the set of stable client-facing addresses of the endpoint mapper to the set of client addresses.
2 . A method comprising:
obtaining, at a mapper, a first data stream generated by a first set of endpoints from a first set of addresses for the first set of endpoints, wherein the mapper maps the first set of addresses to a set of stable addresses; streaming the first data stream from the set of stable addresses to a set of destination addresses; updating the mapper to map the set of stable addresses to a set of anticipated addresses by predicting the set of anticipated addresses for a second set of endpoints based on a history of endpoint addresses; provisioning the second set of endpoints, wherein provisioning the second set of endpoints comprising generating a second set of addresses for the second set of endpoints, wherein the second set of addresses matches with the set of anticipated addresses; obtaining a second data stream generated by the second set of endpoints; and streaming the second data stream from the set of stable addresses to the set of destination addresses.
3 . The method of claim 2 , wherein updating the mapper comprises updating the mapper at least 10 minutes before the second set of addresses are created.
4 . The method of claim 2 , wherein updating the mapper comprises completing update operations for the mapper before the second set of endpoints outputs the second data stream.
5 . The method of claim 2 , wherein the first set of endpoints are within a first computing environment isolated from a second computing environment, and wherein the second set of endpoints are within the second computing environment.
6 . The method of claim 5 , wherein predicting the set of anticipated addresses comprises:
obtaining an indicator of an environment switch from the first computing environment to the second computing environment; and predicting the set of anticipated addresses based on the indicator.
7 . The method of claim 2 , wherein updating the mapper comprises generating a CNAME to map a dynamically generated address of the second set of addresses to a stable address of the set of stable addresses.
8 . The method of claim 2 , further comprising determining that a temporal proximity threshold is satisfied, wherein the temporal proximity threshold indicates a duration before a time period associated with an endpoint application, wherein:
predicting the set of anticipated addresses comprises predicting the set of anticipated addresses in response to determining that the temporal proximity threshold is satisfied; and provisioning the second set of endpoints comprises provisioning the second set of endpoints to execute the endpoint application.
9 . The method of claim 2 , further comprising determining that a temporal proximity threshold is satisfied, wherein:
the temporal proximity threshold indicates a duration before a time period associated with an endpoint application; predicting the set of anticipated addresses comprises predicting the set of anticipated addresses in response to determining that the temporal proximity threshold is satisfied; and provisioning the second set of endpoints comprises provisioning the second set of endpoints to execute the endpoint application.
10 . The method of claim 2 , wherein:
predicting the set of anticipated addresses comprises obtaining a classless inter-domain routing block indicating an address range associated with the second set of endpoints; and updating the mapper comprises mapping all addresses within the address range to the set of stable addresses.
11 . The method of claim 2 , wherein:
provisioning the second set of endpoints comprises obtaining an endpoint count limit and limiting a count of provisioned endpoints to the endpoint count limit; and predicting the set of anticipated addresses comprises predicting the set of anticipated addresses based on the endpoint count limit.
12 . One or more non-transitory, machine-readable media storing program instructions that, when executed by one or more processors, causes the one or more processors to perform operations comprising:
obtaining, at a mapper, a first data stream generated by a first set of endpoints from a first set of addresses for the first set of endpoints, wherein the mapper maps the first set of addresses to a set of stable addresses; streaming the first data stream from the set of stable addresses to a set of destination addresses; updating the mapper to map the set of stable addresses to a set of anticipated addresses by predicting the set of anticipated addresses for a second set of endpoints; provisioning the second set of endpoints, wherein provisioning the second set of endpoints comprises generating a second set of addresses for the second set of endpoints, wherein the second set of addresses matches with the set of anticipated addresses; obtaining a second data stream generated by the second set of endpoints; and streaming the second data stream from the set of stable addresses to the set of destination addresses.
13 . The one or more non-transitory, machine-readable media of claim 12 , the operations further comprising detecting an indication of a malfunction for an initial endpoint of the first set of endpoints, wherein provisioning the second set of endpoints further comprises provisioning the second set of endpoints in response to the indication of the malfunction.
14 . The one or more non-transitory, machine-readable media of claim 12 , the operations further comprising determining a network traffic prediction indicating an increase in network traffic flowing to an initial endpoint of the first set of endpoints, wherein provisioning the second set of endpoints further comprises provisioning the second set of endpoints based on the network traffic prediction.
15 . The one or more non-transitory, machine-readable media of claim 12 , wherein updating the mapper comprises updating the mapper at least 10 minutes before the second set of addresses are created.
16 . The one or more non-transitory, machine-readable media of claim 12 , wherein updating the mapper comprises completing update operations for the mapper before the second set of endpoints outputs the second data stream.
17 . The one or more non-transitory, machine-readable media of claim 12 , wherein the first set of endpoints are within a first computing environment isolated from a second computing environment, and wherein the second set of endpoints are within the second computing environment.
18 . The one or more non-transitory, machine-readable media of claim 12 , wherein updating the mapper comprises generating a CNAME to map a dynamically generated address of the second set of addresses to a stable address of the set of stable addresses.
19 . The one or more non-transitory, machine-readable media of claim 12 , the operations further comprising determining that a temporal proximity threshold is satisfied, wherein the temporal proximity threshold indicates a duration before a time period associated with an endpoint application, wherein:
predicting the set of anticipated addresses comprises predicting the set of anticipated addresses in response to determining that the temporal proximity threshold is satisfied; and provisioning the second set of endpoints comprises provisioning the second set of endpoints to execute the endpoint application.
20 . The one or more non-transitory, machine-readable media of claim 12 , wherein:
provisioning the second set of endpoints comprises obtaining an endpoint count limit and limiting a count of provisioned endpoints to the endpoint count limit; and predicting the set of anticipated addresses comprises predicting the set of anticipated addresses based on the endpoint count limit.Join the waitlist — get patent alerts
Track US2026046270A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.