Networking and API Design for System Design
The communication layer of system design. Networking fundamentals, API design (REST, GraphQL, gRPC), API infrastructure, API security, and real-time and asynchronous communication patterns. Built for senior engineers who need to reason about how distributed systems communicate, in interviews and in production.
What you'll learn
Curriculum
5 modules · 32 lessonsNetworking
The network layer beneath every system you design: the OSI model, addressing, transport protocols, HTTP, DNS, data integrity, and proxies.
API Design
Designing the contract: versioning and compatibility, idempotency, data formats, and the major API styles (REST, GraphQL, gRPC) in depth.
API Infrastructure
The layer that fronts your services: API gateways as a single entry point, and rate limiting to protect what sits behind them.
API Security
Securing the API surface at the system design level: authentication versus authorization, sessions versus tokens, JWTs, OAuth2, and SSO.
Communication Patterns
How systems talk when request-response is not enough: real-time transports (long polling, WebSockets, SSE, webhooks, WebRTC) and asynchronous messaging (queues, pub/sub, CDC, delivery semantics, dead letter queues).
About the Author

Sharon Sahadevan
AI Infrastructure Engineer
Building production GPU clusters on Kubernetes. H100s, large-scale model serving, and end-to-end ML infrastructure across Azure and AWS.
10+ years designing cloud-native platforms with deep expertise in Kubernetes orchestration, GitOps (Argo CD), Terraform, and MLOps pipelines for LLM deployment.
Author of KubeNatives, a weekly newsletter read by 3,000+ DevOps and ML engineers for production insights on K8s internals, GPU scheduling, and model-serving patterns.