Node-RED: Low-code programming for event-driven applications
11–20 of 93 posts
Re: Node-RED: Low-code programming for event-driven applications
#12Re: Node-RED: Low-code programming for event-driven applications
#13How does this compare to n8n? I read somewhere that node red was more focused on IoT applications, is that correct?
Re: Node-RED: Low-code programming for event-driven applications
#14Re: Node-RED: Low-code programming for event-driven applications
#15Re: Node-RED: Low-code programming for event-driven applications
#16Cannot find if it supports any version control? Does it?
The other huge PITA is that touching a node in the UI causes the json to update even if you didn't do anything, and changes will often cause nodes in the json to reorder. That makes git commits very cluttered.
Merging is also very hit-or-miss and duplicate nodes are common. You can mostly fix this with another plugin that saves flows to individual files instead of one big file (default). As long as you split your flows and subflows up enough, team members will usually not step on each others toes.
I used this at work. Not a fan. If you only touched the system once every 4 months I can see the usefulness- It's easier to see the overall structure than wading through code, particularly if you're a visual person. It makes it relatively easy to pick something up that you have mostly forgotten.
It is a huge PITA if you are trying to build API features quickly with a team. Especially if there's nobody to tell you to use the plugins.
Re: Node-RED: Low-code programming for event-driven applications
#17Cannot find if it supports any version control? Does it?
It does (everything is saved as json), but it's a bit of a hassle. Scripts are saved to a single line, so you really need a plugin that breaks them up. It's really pretty silly that isn't the default. The other huge PITA is that touching a node in the UI causes the json to update even if you didn't do anything, and changes will often cause nodes in the json to reorder. That makes git commits very cluttered. Merging i…
Re: Node-RED: Low-code programming for event-driven applications
#18Cannot find if it supports any version control? Does it?
Re: Node-RED: Low-code programming for event-driven applications
#19https://gladysassistant.com/blog/integrate-node-red-with-gla...
Re: Node-RED: Low-code programming for event-driven applications
#20How does this compare to n8n? I read somewhere that node red was more focused on IoT applications, is that correct?
I've used it for an insane amount of things, starting with home automation and telemetry but also fairly sophisticated uses, including:
- Sniffing for multicast streams on a LAN and exposing IPTV set top boxes as HomeKit devices
- Automating image conversion and video transcoding
- Building an RSS aggregation and transformation pipeline that does translations, scraping, etc.
- Building a simple GUI for managing backup snapshots and batch file copies
- Monitoring Azure deployments (and exposing the data as simple dashboards).
- Doing App store price checks and sending Pushover notifications when an interesting app goes on sale (backed by SQLite).
- An embarrassing number of Slack and Telegram bots for various user groups/events/etc.
As a general rule of thumb, Node-RED can do pretty much any kind of automation you can get a REST API for, and quite often someone out there has already built a module for it.
I think of n8n more along the lines of a graphical workflow/BPM tool for SaaS, but with much less flexibility/ability to go "low level".