InterviewStack.io LogoInterviewStack.io

Network Architecture and Communication Patterns Questions

Design and analysis of network architectures and service communication patterns for reliable, performant, and secure distributed systems. Topics include network topology and capacity planning, load balancing strategies, content delivery networks, caching and edge delivery, application programming interface gateway design, service to service communication patterns including synchronous and asynchronous messaging, message queues, publish subscribe, request routing, retries and backoff, timeouts, idempotency, circuit breakers, bulkheads, and service mesh considerations. Also covers latency optimization, failure modes and resilience, observability and monitoring, network security principles such as encryption and segmentation, and how architectural choices affect scalability and operational complexity.

HardSystem Design
42 practiced
Design a CDN solution for low-latency live video streaming with support for 100,000 concurrent viewers. Discuss chunking/segment strategy, edge caching, origin scaling, adaptive bitrate streaming (ABR), latency vs buffer trade-offs, edge transcoding, and how to handle viewer spikes and regional failover.
MediumSystem Design
42 practiced
Design a scalable publish/subscribe notification service that supports 1,000,000 subscribers and 50,000 messages/sec. Consider fanout strategies, push vs pull delivery, ordering guarantees, retention, filtering, partitioning, and how to handle slow or unreachable subscribers. Which technologies would you choose and why?
HardTechnical
40 practiced
Timeouts are misconfigured across a distributed call chain, causing cascading failures. Explain how to design end-to-end timeout budgets: how to set per-hop deadlines, how to propagate time left to downstream services, and techniques to prevent cascading timeouts and wasted work (e.g., client-side cancellation, early exit).
HardTechnical
55 practiced
Design a zero-trust network architecture for a microservices environment. Cover service identity, mTLS, short-lived certificates, network segmentation (network policies), role-based access control for service APIs, secrets management, and certificate rotation. Explain how these choices affect developer experience and operational complexity.
EasyTechnical
37 practiced
What is mutual TLS (mTLS) and why is it important for service-to-service authentication in a microservices architecture or service mesh? Explain the differences from one-way TLS, certificate provisioning/rotation concerns, and how mTLS helps with zero-trust networking.

Unlock Full Question Bank

Get access to hundreds of Network Architecture and Communication Patterns interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.