TSC walkthrough. Using EdgeLake in the edge data manager (EDM) role inside a Unified Namespace deployment, unifying MQTT topic hierarchies with the AnyLog metadata layer.
This TSC walkthrough positions EdgeLake as the edge data manager (EDM) role inside a Unified Namespace (UNS) deployment. UNS is the ISA-95-influenced pattern for industrial architectures where every asset publishes into a shared topic hierarchy (typically over MQTT), and consumers subscribe based on topic path.
The problem UNS solves is topic organization; the problem EdgeLake adds is queryability. UNS gives you a well-structured stream, but historical queries and cross-site joins still need a data manager. EdgeLake takes the EDM role: subscribing to relevant UNS topics, materializing the data on-node, and exposing SQL and MCP access so an operator can ask 'average pressure at pump 3 last shift' without touching the broker.
The session covers wiring an EdgeLake operator into the UNS broker, mapping topic paths to the AnyLog metadata layer, and using the resulting fabric to answer historical and cross-plant queries in place. For customers already running UNS on a Sparkplug-B or plain-MQTT stack, EdgeLake plugs in behind the broker without disrupting existing publishers or subscribers.