Skip to content

Latest commit

 

History

History
51 lines (34 loc) · 1.44 KB

0000-use-event-driven-architecture.md

File metadata and controls

51 lines (34 loc) · 1.44 KB
Raw
status parent deciders consulted informed nav_order
accepted
Decisions
Joachim, Job, Shahin, Jeroen
Joost
Brian
0

Use Event-Driven architecture

Context and Problem Statement

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

Decision Drivers

  • Architecture driving characteristics used for decision are:
    • Concurrency
    • Availability
    • Data integrity
  • Relevant style characteristics for our solution are:
    • Evolvability; to support further growth in additional vital signs
    • Fault-tolerance; to support failover/high availability
    • Performance; to support concurrency

Considered Options

  • Microservices
  • Space-based
  • Event-driven

Decision Outcome

Chosen option: "Event-driven", because:

All relevant style characteristics scored the best for event-driven. Besides the scoring we also believe this architecture will enable:

  • The support of Stayhealthy inc. new line of business and adapt quickly to the market
  • Lower risk of adding additional features to the software

Architecture style decision

Consequences

  • To support all features and requirements we also need to choose a appropiate hardware architecture and valid the NFR's.