Understand current node-red architecture

[h-parekh]

What

Understand the current node-red architecture and the engine's code structure

Why

• To be able to identify pieces of code that can be run without the need of a server or UI

How

• Reach out to the node-red slack community for existing documentation
• Clone node-red:master and use a logging tool

Deliverables

• [x] Links to existing architecture documentation
• [x] Identify existing efforts in the community that may lend our needs

[h-parekh]

In it's current form at v0.19.x, node-red is a monolith of the editor, runtime, nodes and utilities running in the same package.

For the upcoming 0.20.0 release the design document indicates that all the components are being split into seprate modules but being kept in the same monorepo.

The 'Headless' and 'Distributed' use cases seem to fit our currently identified needs of having a runtime without an editor and vice versa.

Timeline

trello project and discourse thread indicate early January 2019 for the final release of v0.20.0. A second beta 0.20.0-beta.2 has already been released. Note: The best way to stay up to date is to subscibe to the news events on the discourse forum.

I see a beta 3 coming up in the changelog, so there's atleast one more beta coming out before the final release of 0.20.0

Next steps

I'm recommending we hold on until the final 0.20.0 release is out and then rehash our share-red repo with the new version.