<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sparkplug on blanpa</title><link>https://blanpa.github.io/tags/sparkplug/</link><description>Recent content in Sparkplug on blanpa</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 blanpa</copyright><lastBuildDate>Sat, 04 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blanpa.github.io/tags/sparkplug/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Unified Namespace with Sparkplug B and Node-RED</title><link>https://blanpa.github.io/blog/unified-namespace-sparkplug-node-red/</link><pubDate>Sat, 04 Jul 2026 00:00:00 +0000</pubDate><guid>https://blanpa.github.io/blog/unified-namespace-sparkplug-node-red/</guid><description>&lt;p>&amp;ldquo;Unified Namespace&amp;rdquo; is the most over-hyped and under-explained term in industrial IoT right now. Vendors sell it as a product, consultants sell it as a transformation, and engineers quietly wonder whether it&amp;rsquo;s anything more than &amp;ldquo;an MQTT broker with good topic names.&amp;rdquo; Having built a few, my honest answer is: it&amp;rsquo;s a &lt;em>pattern&lt;/em>, not a product — and a genuinely good one. This post strips away the hype and shows how to build a real Unified Namespace incrementally, using &lt;a href="https://blanpa.github.io/blog/mqtt-vs-sparkplug-vs-nats-vs-opcua/" >Sparkplug B&lt;/a> and Node-RED.&lt;/p></description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://blanpa.github.io/blog/unified-namespace-sparkplug-node-red/featured.webp"/></item></channel></rss>