From dbbb30e30f9a74e7e98ca65c029542202f9104db Mon Sep 17 00:00:00 2001 From: Claudio Maggioni Date: Tue, 16 May 2023 12:41:04 +0200 Subject: [PATCH] hw12 done, please check --- src/sa/model/index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/sa/model/index.md b/src/sa/model/index.md index 787280f..f9e04ea 100644 --- a/src/sa/model/index.md +++ b/src/sa/model/index.md @@ -1913,6 +1913,9 @@ skinparam defaultFontName Courier ![Architectural Decision Record](./decisions/0008-heartbeat-as-monitor.madr) +7. Given the choice of Web connectors between engine components, cascading failure w.r.t. availability is inherent and cannot be increased other than +introducing multiple engine components and implementing an eventual consistency procedure between them. Another way to increase availability is to have multiple deployments of the stateless Java engines, all connected to the same component database, thus leaving it as a single point of failure. Given the hobbyist nature of Smarthut, I plan to accept this inherent flaw for the delivery of the first MVP and solve the problem in a later release, if and when scalability concerns will be made on the SaaS deployment. + 8. As external dependencies are the smart devices owned by the users, the system cannot function de facto without them being available to the Device engine component. However, I plan to implement a "shadow" state for unavailable devices which is regularly maintained as the actual state of working devices, which will be applied once the device comes back online. The user interface will also make the device failure visible and notify