maggicl/soft-arch
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

hw12 done, please check

Browse source
This commit is contained in:
Claudio Maggioni 2023-05-16 12:41:04 +02:00
parent 629fd1eb28
commit dbbb30e30f
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
src/sa/model/index.md
View file

@ -1913,6 +1913,9 @@ skinparam defaultFontName Courier
![Architectural Decision Record](./decisions/0008-heartbeat-as-monitor.madr) ![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 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 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 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