Most teams design the historian first and connect it to a Unified Namespace later. This article argues the reverse: the UNS owns identity, so it should dictate the historian schema. That means storing tag identity in a relational namespace table with surrogate keys and keeping history in a narr...
Source: [HackerNoon](https://hackernoon.com/a-unified-namespace-determines-your-historian-schema-not-the-other-way-around?source=rss)