This post discusses the limitations of using MQTT for handling transactions in industrial systems despite its strengths in lightweight, event-driven communication. Dylan emphasizes that the Unified Namespace (UNS) is not just an MQTT broker but a broader architectural approach. For reliable transaction delivery, he suggests combining MQTT with direct API calls, blending scalability with reliability instead of relying on a single tool for all tasks.
Which raises the question Dylan asked at the end of his post -
How do you currently handle transactions in your industrial architecture?
Of course MQTT is a bad protocol for transactions integration for IT system. There is a lot of well know patterns and protocols to manage transaction integration (message queue, AMQP, REST) That’s why we use Solace Broker that mix different protocols and patterns in one tool.
Messaging Patterns Overview - Enterprise Integration Patterns There is a lot of good book and resources about this very well know topics in IT. UNS is Event Driven Architecture in the nutshell that integrated OT devices, but for IT solutions, nothing is new. Take care the Hype, UNS is key, Event Driven architecture even more
@youri.regnaud @Richard-SNN @mellerbeck @danielpomeranz