A Pub/Sub (Publish/Subscribe) system is a fundamental pattern for decoupling services. It allows producers to send messages without knowing who the consumers are, enabling highly flexible and asynchronous architectures. Designing a system like Google Cloud Pub/Sub at scale is an advanced architectural challenge.
1. Core Concepts
graph LR
Producer[Producer Service] -->|Publish Event| Kafka[Kafka / Event Bus]
Kafka -->|Consume| Consumer1[Consumer Group A]
Kafka -->|Consume| Consumer2[Consumer Group B]
Consumer1 --> DB1[(Primary DB)]
Consumer2 --> Cache[(Redis)]
- Topic: A named resource to which messages are sent.
- Subscription: A named resource representing the stream of messages from a topic.
- Publisher: Sends messages to a topic.
- Subscriber: Receives messages from a subscription.
2. Decoupling and Scalability
Unlike a message queue where each message is delivered to only one consumer, a Pub/Sub system delivers a copy of each message to every subscription. This requires the system to maintain a separate "read pointer" for every subscription.
3. High-Level Architecture
- API/Frontend Service: Authenticates requests and routes them to the correct topic/subscription.
- Metadata Service: Manages topic/subscription configurations (stored in Zookeeper or etcd).
- Storage Service: A persistent, distributed log service (like a simplified Kafka or Pulsar).
- Delivery Service: Pushes messages to subscribers (via Webhooks, gRPC streams, or long polling).
4. Message Delivery Semantics
- At-Least-Once Delivery: The default for most systems. The server waits for an from the subscriber. If none is received within a timeout, the message is redelivered.
- Exactly-Once Delivery: Significantly harder to achieve. It requires coordination between the server's state (which message was sent) and the client's state (which message was processed). This is usually implemented using Idempotency Keys and persistent state in the subscriber.
5. Storage and Retention
- Retention: Messages are usually kept for a fixed time (e.g., 7 days) or until acknowledged by all subscriptions.
- Deduplication: The server should maintain a short-term cache of message IDs (using a Bloom Filter) to discard duplicate messages sent by misbehaving producers.
6. The "Backlog" Problem
If a subscriber is much slower than the publisher, the system must buffer millions of messages.
- Solution: Use Backpressure. The delivery service can throttle the flow or "drop" older messages if the subscriber is too far behind (if the business use case allows it).
Summary
Building a Pub/Sub platform is an exercise in Asynchronous Coordination. By leveraging a persistent log backend, decoupled delivery agents, and clear delivery semantics, you can provide a reliable foundation for event-driven systems at any scale.
Engineering Standard: The "Staff" Perspective
In high-throughput distributed systems, the code we write is often the easiest part. The difficulty lies in how that code interacts with other components in the stack.
1. Data Integrity and The "P" in CAP
Whenever you are dealing with state (Databases, Caches, or In-memory stores), you must account for Network Partitions. In a standard Java microservice, we often choose Availability (AP) by using Eventual Consistency patterns. However, for financial ledgers, we must enforce Strong Consistency (CP), which usually involves distributed locks (Redis Redlock or Zookeeper) or a strictly linearizable sequence.
2. The Observability Pillar
Writing logic without observability is like flying a plane without a dashboard. Every production service must implement:
- Tracing (OpenTelemetry): Track a single request across 50 microservices.
- Metrics (Prometheus): Monitor Heap usage, Thread saturation, and P99 latencies.
- Structured Logging (ELK/Splunk): Never log raw strings; use JSON so you can query logs like a database.
3. Production Incident Prevention
To survive a 3:00 AM incident, we use:
- Circuit Breakers: Stop the bleeding if a downstream service is down.
- Bulkheads: Isolate thread pools so one failing endpoint doesn't crash the entire app.
- Retries with Exponential Backoff: Avoid the "Thundering Herd" problem when a service comes back online.
Critical Interview Nuance
When an interviewer asks you about this topic, don't just explain the code. Explain the Trade-offs. A Staff Engineer is someone who knows that every architectural decision is a choice between two "bad" outcomes. You are picking the one that aligns with the business goal.
Performance Checklist for High-Load Systems:
- Minimize Object Creation: Use primitive arrays and reusable buffers.
- Batching: Group 1,000 small writes into 1 large batch to save I/O cycles.
- Async Processing: If the user doesn't need the result immediately, move it to a Message Queue (Kafka/SQS).
Advanced Architectural Blueprint: The Staff Perspective
In modern high-scale engineering, the primary differentiator between a Senior and a Staff Engineer is the ability to see beyond the local code and understand the Global System Impact. This section provides the exhaustive architectural context required to operate this component at a "MANG" (Meta, Amazon, Netflix, Google) scale.
1. High-Availability and Disaster Recovery (DR)
Every component in a production system must be designed for failure. If this component resides in a single availability zone, it is a liability.
- Multi-Region Active-Active: To achieve "Five Nines" (99.999%) availability, we replicate state across geographical regions using asynchronous replication or global consensus (Paxos/Raft).
- Chaos Engineering: We regularly inject "latency spikes" and "node kills" using tools like Chaos Mesh to ensure the system gracefully degrades without a total outage.
2. The Data Integrity Pillar (Consistency Models)
When managing state, we must choose our position on the CAP theorem spectrum.
| Model | latency | Complexity | Use Case |
|---|---|---|---|
| Strong Consistency | High | High | Financial Ledgers, Inventory Management |
| Eventual Consistency | Low | Medium | Social Media Feeds, Like Counts |
| Monotonic Reads | Medium | Medium | User Profile Updates |
3. Observability and "Day 2" Operations
Writing the code is only 10% of the lifecycle. The remaining 90% is spent monitoring and maintaining it.
- Tracing (OpenTelemetry): We use distributed tracing to map the request flow. This is critical when a P99 latency spike occurs in a mesh of 100+ microservices.
- Structured Logging: We avoid unstructured text. Every log line is a JSON object containing
correlationId,tenantId, andlatencyMs. - Custom Metrics: We export business-level metrics (e.g., "Orders processed per second") to Prometheus to set up intelligent alerting with PagerDuty.
4. Production Readiness Checklist for Staff Engineers
- Capacity Planning: Have we performed load testing to find the "Breaking Point" of the service?
- Security Hardening: Is all communication encrypted using mTLS (Mutual TLS)?
- Backpressure Propagation: Does the service correctly return HTTP 429 or 503 when its internal thread pools are saturated?
- Idempotency: Can the same request be retried 10 times without side effects? (Critical for Payment systems).
Critical Interview Reflection
When an interviewer asks "How would you improve this?", they are looking for your ability to identify Bottlenecks. Focus on the network I/O, the database locking strategy, or the memory allocation patterns of the JVM. Explain the trade-offs between "Throughput" and "Latency." A Staff Engineer knows that you can never have both at their theoretical maximums.
Optimization Summary:
- Reduce Context Switching: Use non-blocking I/O (Netty/Project Loom).
- Minimize GC Pressure: Prefer primitive specialized collections over standard Generics.
- Data Sharding: Use Consistent Hashing to avoid "Hot Shards."
Technical Trade-offs: Messaging Systems
| Pattern | Ordering | Durability | Throughput | Complexity |
|---|---|---|---|---|
| Log-based (Kafka) | Strict (per partition) | High | Very High | High |
| Memory-based (Redis Pub/Sub) | None | Low | High | Very Low |
| Push-based (RabbitMQ) | Fair | Medium | Medium | Medium |
Key Takeaways
- Topic: A named resource to which messages are sent.
- Subscription: A named resource representing the stream of messages from a topic.
- Publisher: Sends messages to a topic.
Read Next
Mental Model
Connecting isolated components into a resilient, scalable, and observable distributed web.
- System Design Module 2: The Interview Framework (PEDAL)
- System Design: Designing Idempotent APIs for Reliable Services
- System Design: Designing an Ad Click Aggregator
Verbal Interview Script
Interviewer: "How would you ensure high availability and fault tolerance for this specific architecture?"
Candidate: "To achieve 'Five Nines' (99.999%) availability, we must eliminate all Single Points of Failure (SPOF). I would deploy the API Gateway and stateless microservices across multiple Availability Zones (AZs) behind an active-active load balancer. For the data layer, I would use asynchronous replication to a read-replica in a different region for disaster recovery. Furthermore, it's not enough to just deploy redundantly; we must protect the system from cascading failures. I would implement strict timeouts, retry mechanisms with exponential backoff and jitter, and Circuit Breakers (using a library like Resilience4j) on all synchronous network calls between microservices."