liveBook · Manning

Communication

As explained in Acing the Frontend Interview

Communication is the exchange of data and control signals among components of a distributed system.

Communication is the exchange of data and control signals among distributed-system nodes. It supports replica synchronization, shard reassignment, and coordinated health checks, making reliable messaging central to operational reliability. section 6.6

Assess communication choices through their consistency, latency, and failure-handling trade-offs:

  • Synchronous replication completes a write after all replicas acknowledge it, strengthening consistency while increasing write latency. section 6.6
  • Asynchronous replication acknowledges after the primary processes the write, reducing latency while permitting temporary replica inconsistencies. section 6.6
  • Apply RPC or queues for replication events, reassignments, and health checks; use retries, timeouts, and backpressure to manage unreliable communication. section 6.6
  • Optimize communication for locality and tune batching or compression when transferring large migrations. section 6.6

Interview prompt

When asked to compare synchronous and asynchronous replication, explain first when a write is acknowledged, then connect that decision to consistency, latency, and fault tolerance. Expect follow-up questions about reliable node-to-node messaging, retries, timeouts, and backpressure. section 6.6

Table 6.7 Communication, observability, and monitoring
Topic
Fundamentals
Applied skills
Advanced
Communication
Understand reliable node-to-node messaging. Know synchronous vs. asynchronous replication.
Use RPC/queues for replication events, reassignments, health checks; apply retry, timeout, backpressure.
Optimize topologies for locality, tune batching/compression for large migrations.
Observability
Know that metrics, logs, and traces reveal system state. Understand key metrics: replication lag, shard balance, partition health.
Configure distributed tracing and structured logging to follow requests across replicas and partitions. Identify bottlenecks in cross-node queries.
Build unified observability pipelines for metrics/logs/traces. Enable anomaly detection and predictive analytics for shard rebalancing or replication lag.
Monitoring
Understand the need for continuous health checks and alerting. Recognize common signals: latency, error rates, throughput drops.
Set up dashboards and alerts for replication delays, shard hotspots, partition failures. Use SLAs/SLOs to guide monitoring thresholds.
Automate incident response—trigger self-healing, dynamic scaling, or traffic rerouting when anomalies are detected. Integrate with on-call workflows for rapid resolution.

Use the comparison table to scan communication fundamentals, applied mechanisms, and advanced optimization practices alongside observability and monitoring. section 6.6

How Acing the Frontend Interview covers it

How deep it goes
Moves from replication definitions to RPC, queues, retries, timeouts, backpressure, locality, batching, and compression.
Examples
Uses synchronous and asynchronous replication, RPC, queues, replication events, shard reassignments, health checks, and large migrations.
What it assumes
Assumes distributed-system context while defining synchronous and asynchronous replication and introducing communication mechanisms.
What you can do after
Evaluate replication and messaging choices by comparing consistency, latency, fault tolerance, and failure-handling mechanisms.
How it connects
Connects communication with replication, consistency, latency, fault tolerance, shard reassignment, health checks, and backpressure.

Also explained in

Compare how 9 books explain communication →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Acing the Frontend Interview. The section links point to the parts of the book it draws on.