Hall of FameJim Waldo, Geoff Wyant, Ann Wollrath, Sam Kendall199438 min readpaperintermediate
A Note on Distributed Computing
Summary
The paper argues that treating remote objects the same as local ones is fundamentally flawed because distributed systems introduce latency, partial failures, and different memory semantics. It outlines a three‑phase development approach that acknowledges distribution concerns early rather than hiding them.
- Distributed objects must expose latency and failure semantics; hiding location leads to robustness problems.
- Systems like CORBA that aim for location transparency often cannot scale to enterprise‑wide reliability requirements.
- A practical development flow: write abstract interfaces, then concretize object placement, then test under failures and add replication or transactions.
- Assuming a single object model across local and remote contexts is false; designers must consider distribution early.
Engineers building large‑scale distributed services need to recognize the limits of location transparency to avoid reliability pitfalls.
6/10