Very interesting question towards the end for MQTT Wishlist - DHCP like concept for topic names the client can publish to. Maybe there’s a good business case to implement a Topic Registration service. I don’t believe any changes needed to MQTT itself as such
big fan of I4.0 solutions and learnt a lot from this channel to set the OT data ingestion strategy for Snowflake and I will always remain a lifelong student of Arlen from AWS days into Snowflake now.
Great conversation! My best takeaway is Arlen's vision at 1:26:35 - All equipment should already speak Sparkplug. When a new factory is set up, the machines would automatically start talking Sparkplug upon connection. This would eliminate the need for engineers to spend time connecting protocols to machines. Additionally, it would allow for faster recovery times in case of a system failure.
This was a joy to listen to, extremely interesting. The history of the MQTT described by Arlen was the best part for me, was just absolute gold. This kind of information is rare. Thanks a lot 4.0 Solutions and Walker.
Hi Walker, Zach and team. Great video with valuable and rare insight. I appreciate having something productive to listen while working. PS: I read the description on the video and clicked on the discord server link. A message stating this link is invalid appeared.
I actually disagree with Aron regarding sparkplug implementation and JSON. All well and good to have SB C, SBD etc. but don’t forget what makes MQTT great - simplicity and flexibility for the developer how you want to use it. Guaranteeing the compatibility with any broker is also a key. Please don’t over complicate MQTT. Sparkplug as is, is okay. But more happy with vanilla MQTT. Interoperability is the key for successful digital transformation. If there are 10 different types of MQTT, well, there is no one standard anymore.
@@goldensunalways2228 It's a little bit of an in joke. There was a bit going on publicly between Walker and myself recently. But these two questions were ones I raised in the discord, so it is nice that I am not just recognized as a troll.
@@Lachlan.Wright Let me try to put things in my perspective , Its nice to see @Walker treating you so well and ensuring a detailed discussion is being conducted just to ensure you and the community benefits, he could have ignore you royally too... in my opinion Walker was always right when he said by default is report by exception which actually IS a subset of *UNSOLICITED* outputs ... sent without being asked to reduce latency in a way due to the basic protocol rules!!! Correct me here , OPC DA/UA is poll response to start with and can not take IN *UNSOLICITED* DATA. Under( As SUBSET of) *UNSOLICITED* outputs ONE can implement range BASED or further details like why ( change in value based on band width logic etc) and when to send the data , you can not achieve this if a very high speed Data needs to be transmitted and one can wait for the logic to complete before sending those values , just as an example Microprocessor based Numerical relays are used in Power systems to detect which breaker tripped first and caused the tripping in the other circuit and due to what analogue reasons wherein you can have 100s of breaker tripping at the same time ( human recognizing of time) and you need granularity of millisecond to microsecond of which circuit actually caused the series of breaker to trip almost at the same time !!! Multiple values are send as a bust and then evaluated which microsecond one value misbehaved just for a fraction of a second causing the entire system to shut down.. Not easy to achieve what walker has been able to achieve building up this committee, at the end of day every one earns some money , you too, and no one stops you to build your own group !! Who knows you may build a better one benefiting the masses and satisfying trolls much better than @Walker does , i enjoy every bit of it even if i sometimes dont like it or laugh at the way he deals with people !! He is like Mike Tyson for me !!! One of the best !!
Technology embodied by experts focusing on real use-cases and impactful developments, I love that !
Very interesting question towards the end for MQTT Wishlist - DHCP like concept for topic names the client can publish to.
Maybe there’s a good business case to implement a Topic Registration service. I don’t believe any changes needed to MQTT itself as such
big fan of I4.0 solutions and learnt a lot from this channel to set the OT data ingestion strategy for Snowflake and I will always remain a lifelong student of Arlen from AWS days into Snowflake now.
Great conversation and awesome to see a couple of experts discussing new functionalities that could enhance MQTT Sparkplug.
He’ll yeah Arlen Nipper is the man!!
Great conversation! My best takeaway is Arlen's vision at 1:26:35 - All equipment should already speak Sparkplug. When a new factory is set up, the machines would automatically start talking Sparkplug upon connection. This would eliminate the need for engineers to spend time connecting protocols to machines. Additionally, it would allow for faster recovery times in case of a system failure.
This was a joy to listen to, extremely interesting. The history of the MQTT described by Arlen was the best part for me, was just absolute gold. This kind of information is rare. Thanks a lot 4.0 Solutions and Walker.
🙏
Fantastic conversation.loved every minute with Arlen. It’s rare.
Glad you enjoyed it!
Hi Walker, Zach and team. Great video with valuable and rare insight. I appreciate having something productive to listen while working.
PS: I read the description on the video and clicked on the discord server link. A message stating this link is invalid appeared.
Nice one , Good Job Walker !!
The longer videos are always the best. Thanks!
Great conversation
Great content 🎉
Thank you 🙌
I actually disagree with Aron regarding sparkplug implementation and JSON. All well and good to have SB C, SBD etc. but don’t forget what makes MQTT great - simplicity and flexibility for the developer how you want to use it. Guaranteeing the compatibility with any broker is also a key. Please don’t over complicate MQTT. Sparkplug as is, is okay. But more happy with vanilla MQTT.
Interoperability is the key for successful digital transformation. If there are 10 different types of MQTT, well, there is no one standard anymore.
To some extent, I also disagree with Walker here about limitations of MQTT. Once it is over complicated, it will be harder to adopt.
Problem with standards is, there are too many of them 😂
AND not OR™
27:18 What a great question! 😀 Haha! ❤
57:58 Another great question. Gee this Lachlan guy is pretty great.
Loved this one Btw! One of your best postcards!
@@Lachlan.Wright ????
@@goldensunalways2228 It's a little bit of an in joke. There was a bit going on publicly between Walker and myself recently. But these two questions were ones I raised in the discord, so it is nice that I am not just recognized as a troll.
@@Lachlan.Wright Let me try to put things in my perspective , Its nice to see @Walker treating you so well and ensuring a detailed discussion is being conducted just to ensure you and the community benefits, he could have ignore you royally too...
in my opinion Walker was always right when he said by default is report by exception which actually IS a subset of *UNSOLICITED* outputs ... sent without being asked to reduce latency in a way due to the basic protocol rules!!!
Correct me here , OPC DA/UA is poll response to start with and can not take IN *UNSOLICITED* DATA. Under( As SUBSET of) *UNSOLICITED* outputs ONE can implement range BASED or further details like why ( change in value based on band width logic etc) and when to send the data , you can not achieve this if a very high speed Data needs to be transmitted and one can wait for the logic to complete before sending those values , just as an example Microprocessor based Numerical relays are used in Power systems to detect which breaker tripped first and caused the tripping in the other circuit and due to what analogue reasons wherein you can have 100s of breaker tripping at the same time ( human recognizing of time) and you need granularity of millisecond to microsecond of which circuit actually caused the series of breaker to trip almost at the same time !!! Multiple values are send as a bust and then evaluated which microsecond one value misbehaved just for a fraction of a second causing the entire system to shut down..
Not easy to achieve what walker has been able to achieve building up this committee, at the end of day every one earns some money , you too, and no one stops you to build your own group !! Who knows you may build a better one benefiting the masses and satisfying trolls much better than @Walker does , i enjoy every bit of it even if i sometimes dont like it or laugh at the way he deals with people !! He is like Mike Tyson for me !!! One of the best !!