43 lines
817 B
Markdown
43 lines
817 B
Markdown
|
# Concept — Frontend Responsibility Model
|
||
|
|
|
||
|
|
Status: hypothesis
|
||
|
|
|
||
|
|
## Proposition
|
||
|
|
|
||
|
|
Frontend architectures can be usefully analyzed through nine responsibilities:
|
||
|
|
|
||
|
|
1. Address
|
||
|
|
2. Authority
|
||
|
|
3. Projection
|
||
|
|
4. Affordance
|
||
|
|
5. Mutation
|
||
|
|
6. Synchronization
|
||
|
|
7. Reconciliation
|
||
|
|
8. Composition
|
||
|
|
9. Execution
|
||
|
|
|
||
|
|
These are dimensions of responsibility, not mandatory modules.
|
||
|
|
|
||
|
|
## Value
|
||
|
|
|
||
|
|
The model appears broad enough to describe:
|
||
|
|
|
||
|
|
- document-oriented web applications,
|
||
|
|
- SPAs,
|
||
|
|
- server-rendered systems,
|
||
|
|
- islands,
|
||
|
|
- server components,
|
||
|
|
- microfrontends,
|
||
|
|
- offline-first applications,
|
||
|
|
- local-first applications,
|
||
|
|
- collaborative replicated applications.
|
||
|
|
|
||
|
|
## Research burden
|
||
|
|
|
||
|
|
The model must be challenged for:
|
||
|
|
|
||
|
|
- redundancy,
|
||
|
|
- missing responsibilities,
|
||
|
|
- ambiguous boundaries,
|
||
|
|
- inability to distinguish materially different architectures.
|