|
|
|
|
|
by bearjaws
332 days ago
|
|
1. Workflow builder is cumbersome at scale, it's often hard for anyone to jump in to understand what is going on exactly. Especially if you cannot avoid using a JS node to perform a more tricky manipulation. 2. Often times you end up writing code to help support node-red, you must avoid this at all costs because you end up shifting more and more into code bases, making node-red pointless. 2. Lots of sub menu "advanced" functions that you will need to use for any complex flow. 3. Observability is poor out of the box, especially if you use a service like datadog or NewRelic, we ended up using a catch all error handler that just shipped events to NewRelic. 4. Poor out of box defaults for security, mainly authentication 5. Conflict resolution sucks, you have to JSON stable stringify the changes to ensure you can deal with conflicts and conduct proper code reviews. |
|
That's all useful feedback to us. There's always a balance to be had between putting lots of code in Function nodes and the visual complexity of doing the equivalent in pure nodes. Part of that is understanding where users are falling back to JS in a Function node - and what could the core nodes provide to avoid that necessity.
Code reviews are a common piece of feedback and something we need to help with.
In the day job (FlowFuse CTO) we're looking at how to improve the overall developer UX of Node-RED - both within node-red, but also how you manage it within a team and at scale.
If you had any more feedback on your experiences, would love to hear it.