Begin beacon design - Githubissues

randomchain / developing-beacon-paper

1 stars 0 forks source link

Begin beacon design #6

Closed mathiassmichno closed 6 years ago

mathiassmichno commented 6 years ago

Architectural first

Things to keep in mind:

Architectural patterns we might use
Fault tolerant / failover
Low coupling (independent components)
Highly modular
Focus on data exchange between components
- Is the tech important? Probably not. Should just be abstract idea of inter-component communication.
Security concerns / outright analysis (hit the ground running in regards to sec. anal.)

NB: Big task, requires sub tasks

mathiassmichno commented 6 years ago

Round 1: (fight)

Service Oriented Architecture (SOA)
One Beacon consists of an aggregation of services
- N input collectors
- Input processor
- Computator
- M publishers (commitment and output)

mathiassmichno commented 6 years ago

Allocation of requirements to components in the software. From Swebok: "As an example, requirements for a particular breaking performance for a car (braking distance, safety in poor driving conditions, smoothness of application, pedal pressure required, and so on) may be allocated to the braking hardware (mechanical and hydraulic assemblies) and an antilock braking system (ABS)"