Search

• IndexHiveMQ Blog — MQTT in depth

  HiveMQ's technical blog: MQTT features, Sparkplug, broker operations, and IIoT architecture at scale.

• OriginalMQTT QoS, retained messages, and sessions, explained

  The three MQTT features that decide whether your telemetry is lossy, stale, or exactly-once — and when each setting is correct.

• IndexMQTT: the standard for IoT messaging

  The MQTT organization homepage: protocol resources, version history, and links to brokers, clients, and the OASIS standard.

• TermQoS (MQTT)

  MQTT delivery guarantees: 0, 1, or 2. — MQTT quality of service: QoS 0 (at most once), QoS 1 (at least once, may duplicate), QoS 2 (exactly once). Negotiated per hop and capped by the subscription — publishing high to a low-QoS subscriber still delivers at most once.

• TermMQTT

  Lightweight pub/sub transport for telemetry and events. — A lightweight publish/subscribe messaging protocol (OASIS standard): clients publish to topic strings on a broker, subscribers receive matching messages. Features QoS levels, retained messages, persistent sessions, and Las…

• OriginalOPC UA, MQTT, and Sparkplug B: how they fit together

  Three technologies that get compared as rivals but usually work as layers. What each one owns, and how to stop choosing between them.

• TopicMQTT

  MQTT messaging for telemetry, UNS architectures, and device connectivity.

• IndexEclipse Sparkplug — specification and resources

  The Eclipse Sparkplug project: specification, TCK, compatible products, and working-group resources for MQTT-based OT interoperability.

• IndexOptoBlog — edge & IIoT practices

  Opto 22's OptoBlog: edge devices, Node-RED, MQTT/Sparkplug, and practical IIoT project writeups.

• OriginalSparkplug B in one page

  The topic namespace, birth certificates, and state awareness that turn MQTT from a transport into a plug-and-play OT data fabric.

• TermTopic namespace

  Governed MQTT topic hierarchy. — The governed topic hierarchy of an MQTT deployment or UNS — naming conventions, schema rules, and lifecycle management that keep one broker understandable at enterprise scale.

• OriginalEdge gateway patterns for brownfield connectivity

  Protocol conversion, buffering, and context at the edge — the four gateway patterns that connect legacy equipment to modern platforms.

• OriginalThe unified namespace, explained

  One broker, one topic tree, every producer and consumer decoupled. What a UNS is, what it demands, and where it goes wrong.

• TermKepware

  Multi-protocol connectivity server, now part of Velotic. — Industrial connectivity software exposing hundreds of device and PLC protocols through OPC UA, MQTT, and other northbound interfaces. Originally by PTC, now part of Velotic alongside Proficy and ThingWorx.

• IndexKepware industrial connectivity (Velotic)

  Kepware (now part of Velotic): industrial connectivity software exposing hundreds of device protocols via OPC UA, MQTT, and more.

• TermSparkplug B

  MQTT namespace + payload + state spec for OT. — The Eclipse specification turning MQTT into a plug-and-play OT fabric: a fixed topic namespace (group/message-type/edge-node/device), protobuf payloads, and birth/death session semantics giving state awareness without polling.

• TopicSparkplug B

  Sparkplug B: MQTT namespace and payload spec for plug-and-play IIoT.

• TermStore and forward

  Buffering through outages, replaying on recovery. — Buffering data locally through connectivity outages and replaying it in order on recovery. Implemented in edge gateways, MQTT persistent sessions, and historian collectors; sized by the longest plausible outage.

• TermUnified namespace

  One broker hierarchy as the enterprise integration point. — Unified namespace: an architecture with a single MQTT broker hierarchy as the enterprise integration point — producers publish once, consumers subscribe independently. Requires governed topics (usually Sparkplug for OT)…

19 matches