Edge database management of the network data plane

An apparatus comprising:

• a processor;
• and
• non-transitory computer readable media comprising instructions executable by the processor to:
• obtain, via a database, a network configuration;
• spawn a container according to the network configuration, wherein the container is configured, based on the network configuration, to be coupled to a network overlay via a network interface;
• receive, via the network interface, incoming data associated with the container, the incoming data having attached one or more attached network data attributes;
• identify, via the database, the attached one or more network data attributes attached to the incoming data as one or more network data attributes of a network data model;
• attach one or more network data attributes associated with outgoing data, wherein outgoing data is transmitted by the container and the one or more network data attributes attached to the outgoing data are based, at least in part, on the container;
• prioritize forwarding of the incoming data based, at least in part, on the one or more attached network data attributes;
• and
• transmit, via the network interface, a memory pointer associated with a memory address of the outgoing data,
• wherein the database comprises a multi-dimensional data store configured to define the network data model, wherein the network data model is configured to support one or more network data attributes.

A method comprising:

• defining, at an edge database, a network data model configured to support one or more network data attributes;
• providing, via the edge database, a network configuration;
• obtaining, via an orchestrator, the network configuration from the edge database;
• spawning, via the orchestrator, a container according to the network configuration, wherein spawning the container further comprises coupling the container, based on the network configuration, to a network overlay via a network interface;
• receiving, via the network interface, incoming data associated with the container, the incoming data having attached one or more attached network data attributes;
• identifying, via the database, the attached one or more network data attributes attached to the incoming data as one or more network data attributes of the network data model;
• attaching, via the orchestrator, one or more network data attributes associated with outgoing data, wherein outgoing data is transmitted by the container and the one or more network data attributes attached to the outgoing data are based, at least in part, on the container;
• prioritizing forwarding of the incoming data based, at least in part, on the one or more attached network data attributes;
• and
• transmitting, via the network interface, a memory pointer associated with a memory location of the outgoing data.