frodovdr
/
node-red
mirror of https://github.com/node-red/node-red.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Add architecture diagram

Jeff Eiden 2018-04-13 10:37:46 -07:00
parent 2b71cc704a
commit c2af2eb754
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Design:-Runtime-Editor-Split.md

@ -149,5 +149,9 @@ At Particle, we would likely want to run the message processing using _separate_
We currently follow a similar pattern for our [webhooks system](https://docs.particle.io/guide/tools-and-features/webhooks/). Our REST API is a standalone app that allows for CRUD of webhooks. Separately we have a webhooks service that is responsible for actually queuing, sending and receiving the HTTP requests. The API and the webhooks service can communicate with one another, but functionally carry out distinct and separate responsibilities. This has served us very well in managing these two systems as their nature requires optimizing for different things in infrastructure-land (i.e. load-balancing inbound, synchronous requests to an API is quite different to managing queues of work in the background).
This approach of seeing the runtime as 2 separate components seems to align with the architecture diagram proposed in the "Roadmap to 1.0" slide deck:
![](https://i.imgur.com/WjxG0Cm.png)
What would y'all think of this proposal?
</details>