Skip to content

Latest commit

 

History

History
50 lines (34 loc) · 1.47 KB

0001-use-distributed-systems.md

File metadata and controls

50 lines (34 loc) · 1.47 KB
status parent deciders consulted informed nav_order
accepted
Decisions
Joachim, Job, Shahin, Jeroen
Joost
Brian
1

Use distributed system architecture (hardware)

Context and Problem Statement

Which architecture style is the best fit for purpose to support the MonitorMe physical architecture requirements and enabling of the StayHealthy inc. business strategy?

Decision Drivers

  • 24/7 availability
  • On-premise, so no cloud to rely on
  • Easy to install, implement and upgrade
  • No single point of failures within the MonitorMe instance
  • Easily to replace/upgrade without downtime
  • Futureproof, scale out if needed to support additional vital signs monitoring or other requirements that increases load.

Considered Options

  • Distributed systems
  • Centralized system
  • Microservices

Decision Outcome

Chosen option: "Distributed systems", because:

Distributed system enables all requirements and the other options considered did not. Centralized system lacks fault-tolerance and Microservices requires a complex architecture to run on, which is viable in the cloud but not preferable for onpremise systems.

Distributed system

Consequences

We accepted the additional NFR effort that a distributed system requires, such as:

  • Synchronisation / replication
  • Auto discovery
  • Load distribution
  • Auto failover