A Unified Namespace Determines Your Historian Schema, Not the Other Way Around
A Unified Namespace Determines Your Historian Schema, Not the Other Way Around

A Unified Namespace Determines Your Historian Schema, Not the Other Way Around

IoT
Damaso Sanoja

By Damaso Sanoja

A UNS puts your historian downstream of continuous tag churn. Learn the schema that survives renames, reorgs, and retirements without rewriting history.

Read more

PostgreSQL for Everything

Built on PostgreSQL, Tiger Cloud combines robustness and flexibility to tame your most demanding workloads, from real-time analytics and IoT data to events and vector embeddings.

Start a free trial

Stay updated with new posts and releases.

Receive the latest technical articles and release notes in your inbox.