US 11,868,824 B2
Single node and multiple node datastore architecture in a network routing environment
Pushpasis Sarkar, Bangalore (IN); Keyur Patel, San Jose, CA (US); Derek Man-Kit Yeung, Fremont, CA (US); Alpesh Patel, San Ramon, CA (US); Lawrence Rolfe Kreeger, Fremont, CA (US); and Nalinaksh Pai, San Ramon, CA (US)
Assigned to ARRCUS INC., San Jose, CA (US)
Filed by Arrcus Inc., San Jose, CA (US)
Filed on Aug. 23, 2019, as Appl. No. 16/549,369.
Claims priority of provisional application 62/722,003, filed on Aug. 23, 2018.
Prior Publication US 2020/0065317 A1, Feb. 27, 2020
Int. Cl. G06F 16/20 (2019.01); G06F 9/54 (2006.01); H04L 45/00 (2022.01); H04L 45/50 (2022.01); H04L 12/44 (2006.01); H04L 12/46 (2006.01); H04L 45/48 (2022.01); G06F 16/27 (2019.01); G06F 16/23 (2019.01); G06F 16/22 (2019.01); G06F 9/455 (2018.01); H04L 12/66 (2006.01); H04L 45/02 (2022.01); G06F 9/48 (2006.01); H04L 45/24 (2022.01); H04L 45/745 (2022.01); H04L 47/125 (2022.01); H04L 9/40 (2022.01); H04L 12/28 (2006.01); H04L 45/586 (2022.01); H04L 67/1097 (2022.01); H04L 67/55 (2022.01); H04L 49/25 (2022.01)
CPC G06F 9/542 (2013.01) [G06F 9/45558 (2013.01); G06F 9/4881 (2013.01); G06F 9/54 (2013.01); G06F 16/2272 (2019.01); G06F 16/2379 (2019.01); G06F 16/27 (2019.01); G06F 16/278 (2019.01); H04L 12/2881 (2013.01); H04L 12/44 (2013.01); H04L 12/462 (2013.01); H04L 12/4633 (2013.01); H04L 12/4641 (2013.01); H04L 12/66 (2013.01); H04L 45/02 (2013.01); H04L 45/08 (2013.01); H04L 45/22 (2013.01); H04L 45/24 (2013.01); H04L 45/26 (2013.01); H04L 45/48 (2013.01); H04L 45/50 (2013.01); H04L 45/586 (2013.01); H04L 45/66 (2013.01); H04L 45/745 (2013.01); H04L 47/125 (2013.01); H04L 63/0272 (2013.01); H04L 67/1097 (2013.01); H04L 67/55 (2022.05); G06F 2009/45595 (2013.01); H04L 49/25 (2013.01); H04L 2012/4629 (2013.01)] 16 Claims
OG exemplary drawing
 
1. A system comprising:
a plurality of instances of a datastore node in a single networking device, wherein the single networking device is a switch or a router, and wherein each of the plurality of instances of the datastore node comprises:
a datastore stored on the single networking device;
a publisher executing on the single networking device, wherein the publisher is independent of the datastore and configured to publish data to the datastore;
a subscriber executing on the single networking device, wherein the subscriber is independent of the datastore and configured to receive information from the datastore; and
a replicator agent and a persistent storage agent each executing on the single networking device and configured to connect to the datastore; and
a single instance of an index server in communication with the plurality of instances of the datastore node;
wherein each of the datastore, the publisher, the subscriber, the replicator agent, and the persistent storage agent are independent components of each of the plurality of instances of the datastore node; and
wherein the single instance of the index server updates a list of publishers and subscribers in response to receiving a notification from the subscriber indicating a desire to subscribe to a certain dataset.