I saw Node Red production ready since 2019. A framework that merges OT and IT development practices, OT because we can debug code and deploy code in a live production environment, is similar to use automation framework like TIA Portal or CODESYS, using some IEC 61131-3 language, but we do this using low code and a web based interface, regarding data extraction and transformations. In the other hand we can find some IT practice present, like git control, and the ability to program functions using JavaScript. So, for me, this is the framework where OT guys and IT guys can easily collaborate together and leverage the huge community that increases each day. My suggestion is change the title of the video to " Node Red - production ready, no matter what they say!"😂
As of now there's only 1 thing I hate about Node-Red. And that is it's total crashing when a certain error is found in a file. I would love for every flow to have it's own process and be independant of others. So that if a flow fails, not the whole 'Node-Red infrastructure' crashes as well.
me too so i deploy multiple instances like port 1880 1881 1882 and so on ( avoid 1883 ) and now i can control which is primary simple and never crash flow
This was a good full podcast. I 100% prefer these types of videos/clips that contain actual information/content rather than some of the more fratboy sh!t talking videos.
Node Red is a great piece of software... but the fact that it runs with node.js and Javascript makes me not want to use it because I really dislike Javascript, and I never want to write custom code for it. If all you need is a data ingestion pipeline from PLC to a database with some ETL in the middle the it's a good fit.
It lives on the edge. Simple, flexible and super scalable. My #1 go-to software for IIoT.
I saw Node Red production ready since 2019. A framework that merges OT and IT development practices, OT because we can debug code and deploy code in a live production environment, is similar to use automation framework like TIA Portal or CODESYS, using some IEC 61131-3 language, but we do this using low code and a web based interface, regarding data extraction and transformations. In the other hand we can find some IT practice present, like git control, and the ability to program functions using JavaScript. So, for me, this is the framework where OT guys and IT guys can easily collaborate together and leverage the huge community that increases each day. My suggestion is change the title of the video to " Node Red - production ready, no matter what they say!"😂
Great Podcast / Video! Node-RED is Love and production ready!
i was waiting for this
As of now there's only 1 thing I hate about Node-Red. And that is it's total crashing when a certain error is found in a file. I would love for every flow to have it's own process and be independant of others. So that if a flow fails, not the whole 'Node-Red infrastructure' crashes as well.
me too so i deploy multiple instances like port 1880 1881 1882 and so on ( avoid 1883 )
and now i can control which is primary simple and never crash flow
Node Red is a great glue and of course comes on a lot of controllers (Opto 22 groov line) and edge devices (RPi, Tulip Edge IO, etc.)
I would be curious to see an open source stack for the SMB space. I think that’s the edge of the edge.
This was a good full podcast.
I 100% prefer these types of videos/clips that contain actual information/content rather than some of the more fratboy sh!t talking videos.
Thank you for the feedback!
@@4.0Solutions Cool! please don't take it the wrong way. In general - love your stuff!
Node Red is a great piece of software... but the fact that it runs with node.js and Javascript makes me not want to use it because I really dislike Javascript, and I never want to write custom code for it. If all you need is a data ingestion pipeline from PLC to a database with some ETL in the middle the it's a good fit.