Proposed Term
Fallacies of Distributed Computing
Context
Source: catalog review of https://lawsofsoftwareengineering.com/.
Why it may qualify as an anchor: Eight named false assumptions (the network is reliable, latency is zero, bandwidth is infinite, the network is secure, topology doesn't change, there is one administrator, transport cost is zero, the network is homogeneous). That makes it a structured, bounded checklist you can invoke to audit a distributed design — not a vague observation.
- Precise: a fixed enumerated list of 8 items
- Rich: each fallacy opens its own design-concern domain
- Consistent: stable, well-documented enumeration
- Attributable: L. Peter Deutsch & James Gosling (Sun Microsystems)
Pre-assessment tier: ★★★ (self-standing) — fills a distributed-systems gap.
Related existing anchors: event-driven-architecture, cqrs.
Pre-submission Checklist
Proposed Term
Fallacies of Distributed Computing
Context
Source: catalog review of https://lawsofsoftwareengineering.com/.
Why it may qualify as an anchor: Eight named false assumptions (the network is reliable, latency is zero, bandwidth is infinite, the network is secure, topology doesn't change, there is one administrator, transport cost is zero, the network is homogeneous). That makes it a structured, bounded checklist you can invoke to audit a distributed design — not a vague observation.
Pre-assessment tier: ★★★ (self-standing) — fills a distributed-systems gap.
Related existing anchors:
event-driven-architecture,cqrs.Pre-submission Checklist