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.
HardTechnical
39 practiced
Design observability for a high-throughput system: sampling for traces, reducing metrics cardinality, log aggregation cost controls, and alerting strategy when tracing every request is too expensive. Reference OpenTelemetry and discuss practical sampling algorithms and aggregation techniques.
HardTechnical
38 practiced
Propose a migration plan to move a large monolith into microservices, with emphasis on network and communication patterns. Outline a stepwise approach (strangler pattern, API gateway, service discovery), how to design inter-service contracts, deal with increased network overhead, and how to validate correctness and performance during migration.
MediumTechnical
33 practiced
Implement a simple circuit breaker class in Python with parameters: failure_threshold (percent), request_volume_threshold, reset_timeout_seconds. The class should wrap a synchronous call and manage OPEN/HALF-OPEN/CLOSED states, using a sliding window for failures. Ensure thread-safety and describe how you'd test it.
HardSystem Design
60 practiced
Architect an event streaming platform capable of ingesting and processing 2 million events per second while offering end-to-end exactly-once semantics for downstream consumers. Discuss partitioning strategy, ordering guarantees, ingestion scaling, retention, deduplication, transactional writes, and the trade-offs of using Kafka-like systems vs cloud-managed streaming services.

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.