Clarifications Node Red

OL Connect Automate
1

We understand that Upland is going to create an OL Connect Node-RED stack (OLCNRS) and have been discovering and testing it.

We are interested in getting answers on the following if possible:
Will we be able to synchronize Node-RED flows running on multiple servers?
Will we be able to edit Node-RED flows in the Cloud through a browser?
Will we be able to generate alerts when Node-RED is down?
Will we be able to control location of data processing stays on local servers or cloud?
Will there be support for stock Node-RED?
Will there be support for Node.js?
Will there be training on Node-Red?
Will there be training on Node.js?
What will the cost structure be for new clients and current OL Care clients using current worflow software?

We understand that the current state of the new software is in it’s early stages but any info is welcomed.

Thanks

2

  • Will we be able to synchronize Node-RED flows running on multiple servers?
    We are planning to integrate versioning, so that allows you to centralize flows on a version control server and ensure the same versions (or different versions) run on each NR server.

  • Will we be able to edit Node-RED flows in the Cloud through a browser?
    NR flows are always editable through a browser. Our implementation won’t change that.

  • Will we be able to generate alerts when Node-RED is down?
    That would require an external monitoring service. Those already exist, we do not have immediate plans to develop one of our own.

  • Will we be able to control location of data processing stays on local servers or cloud?
    Data processing occurs on the system where NR is running.

  • Will there be support for stock Node-RED?
    OLCNRS is stock Node-RED, with OL Connect-specific functionality added

  • Will there be support for Node.js?
    Node-RED is based on NodeJS. Without it, there is no Node-RED. So yes, NodeJS is supported

  • Will there be training on Node-Red?
    Yes

  • Will there be training on Node.js?
    No

  • What will the cost structure be for new clients and current OL Care clients using current worflow software?
    Undecided yet, but will remain very similar to our current structure.

3

You could actually have a Workflow server pinging the NR server to check on it.

4

@hamelj: In the long term perspective where OLCNRS eventually replaces Workflow, then we don’t want to suggest implementing a dependency on Workflow. Might just as well use a second NR instance running in a different container to monitor the first one. But that’s not a proper solution either: what if the monitoring server is down?

Every Cloud provider offers monitoring services for a nominal fee. That’s what i would recommend if the the application is running on the Cloud. For on-premise instances, there are a number of commercial products that can already do this.

1 Like
5

A good example is https://www.pingdom.com/