This story was originally published on HackerNoon at:
https://hackernoon.com/a-unified-namespace-determines-your-historian-schema-not-the-other-way-around.
Design a historian schema for Unified Namespace architectures. Learn why narrow tables, surrogate keys, and relational namespaces outperform wide models.
Check more stories related to programming at:
https://hackernoon.com/c/programming.
You can also check exclusive content about
#unified-namespace,
#uns-data-model-design,
#database-architecture,
#timescaledb-iot-schema,
#isa-95-namespace-architecture,
#surrogate-key-historian-design,
#tag-management,
#good-company, and more.
This story was written by:
@tigerdata. Learn more about this writer by checking
@tigerdata's about page,
and for more stories, please visit
hackernoon.com.
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 narrow hypertable. The result: tag renames, hierarchy changes, and churn happen without rewriting history.