From c2af2eb7549bff2a992a6274dba43444d4ae3fb4 Mon Sep 17 00:00:00 2001 From: Jeff Eiden Date: Fri, 13 Apr 2018 10:37:46 -0700 Subject: [PATCH] Add architecture diagram --- Design:-Runtime-Editor-Split.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Design:-Runtime-Editor-Split.md b/Design:-Runtime-Editor-Split.md index c88b47d..f17f911 100644 --- a/Design:-Runtime-Editor-Split.md +++ b/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?