Design Decisions for Communication Systems
Talkat KubeCon + CloudNativeCon North America 2019 · on Tuesday, 2019-11-19· at 15:20· Room 15AB - San Diego Convention Center, Mezzanine Level·
summary
Compares low‑level primitives (pipes, FIFOs, shared memory, UNIX domain sockets) and their properties — ordered, buffered, local — to higher‑level designs like RPC, RMI, REST, message brokers and gRPC; notes gRPC supports full duplex streaming, pipelining and propagated deadlines for cascading timeouts; RMI requires a directory service, reference counting/GC and breaks network transparency; brokers add brokered persistence and suit one‑way or multicast workloads but hurt request/response latency; Kubernetes uses REST with resource‑style garbage collection.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:39Programming Languages
- 2:12Communication Systems
- 7:21FIFO (named pipe)
- 8:01Shared Resources
- 10:37Sockets
- 12:10Unix Domain Socket
- 18:46Implications of References
- 20:27D-Bus example
- 22:39RMI
- 26:51Brokered
- 31:55Non-functional
related talks
46mAnalyzing Architecture Tradeoffs
33mFrom Enterprise Architecture to Software Design - Critical Thinking
47mInteraction Protocols: It's all about good manners
01h 01mAn Architect's Approach to API Strategies
01h 03mThe Language of the System
01h 17mWhen Less Is More: Designing & Decoding Complex Distributed Systems
58mElements of Distributed Architectures
54mArchitecture Foundations: Styles & Patterns (2021)