...

Each payload follows a consistent format that includes:

• Metrics – The actual data points being transmitted

...

• Timestamps – For precise data tracking

...

• Metadata – Additional details about the device or data source.

This structured payload eliminates the ambiguity seen in traditional MQTT deployments, where payloads can vary significantly between devices.

...

To maintain system awareness, Sparkplug introduces birth and death certificates.

• Birth Certificate (NBIRTH): Sent by an Edge Node when it comes online.
  • This message announces the node’s presence, publishes its available metrics, and signals to the system that the device is active.
• Death Certificate (NDEATH): Sent by the MQTT Broker if an Edge Node unexpectedly disconnects.
  • This ensures the system is immediately aware when a device goes offline.

Real-Time State Awareness

Sparkplug’s state management goes beyond simple message delivery. By requiring devices to maintain active connections with the broker, Sparkplug ensures that system state is always known.

When devices disconnect, the broker automatically alerts Host Applications by publishing a death certificate — preventing stale or inaccurate data from being mistaken as live.

Unified Namespace for Simplified Data Management

Sparkplug’s structured topics and payloads enable a unified namespace, where all devices adhere to the same data model. This simplifies the integration of new devices, reduces configuration overhead, and ensures data is always delivered in a predictable format — critical for scaling IIoT ecosystems.

Which One to Use?

Plain MQTT is ideal for lightweight IoT deployments where flexibility is key, and devices produce minimal data points.

...