RPC is Evil
summary
Argues against using RPC-style communication in distributed systems, examining the problems RPC introduces for reliability and coupling and advocating alternative approaches such as message-based or asynchronous communication patterns. Discusses practical consequences for Microsoft/.NET platform architects and how to design services to avoid RPC pitfalls.
AI-written summary · about
chapters (6)
- 0:00Start
- 10:15The Command-Response Protocol
- 16:50Interface Definition Language
- 30:59Temporal Coupling
- 45:48A Critique of the Remote Procedure Call
- 46:10A Note on Distributed Computing
related talks
36m40 Years of Pretending
43mWhat you need to know about the comeback of RPC
19mUnlocking New API Opportunities: PaaS to RPC Migration
15mRemote Procedure Call as a Managed System Service
31mRPC Frameworks Overview
24mDatacenter RPCs can be General and Fast
01h 01mAn Architect's Approach to API Strategies
50mCommunication in a Distributed World
