HyperLogLog at Scale

Mental Model

Connecting isolated components into a resilient, scalable, and observable distributed web.

Counting unique users (cardinality) for billions of events is a classic trade-off problem. Do you want 100% accuracy (massive memory) or high speed with 99% accuracy (tiny memory)?

1. The Cardinality Problem

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)]

To track unique users, you'd usually use a . But storing 1 billion unique in a would take gigabytes of RAM.

2. The Solution: Probabilistic Counting

HyperLogLog (HLL) estimates cardinality using the properties of random binary strings. It counts the number of leading zeros in the hash of every input.

3. Real-world Efficiency

Redis's implementation of HLL uses a maximum of 12KB of memory to estimate cardinality for billions of unique items with an error rate of ~0.81%.

4. Why leading zeros work

If hashes are uniformly distributed, seeing a hash with many leading zeros is rare.
The maximum observed zero-prefix length correlates with set cardinality.
HLL improves accuracy by splitting observations across many registers and combining them with harmonic-mean style estimation.

5. Operational use cases

HLL is ideal for:

• daily/monthly active users
• unique visitors by campaign
• unique IP estimation for abuse detection
• approximate unique keys in streaming pipelines

It is not ideal when exact billing/audit correctness is required.

6. Mergeability advantage

A major benefit is composability:

• compute HLL sketches per shard/region/window
• merge sketches centrally
• estimate global cardinality without raw event transfer

This is powerful for large analytics systems where raw data movement is expensive.

7. Accuracy expectations

Typical Redis HLL error is ~0.81% with fixed memory footprint.
For many product analytics questions, this is a strong trade-off:

• tiny memory
• stable throughput
• bounded relative error

For compliance-grade numbers, use exact dedupe pipelines instead.

8. Common pitfalls

• low-quality hash function causing bias
• using HLL for tiny cardinalities where exact set is cheap
• mixing incompatible sketch formats
• treating estimate as exact count in financial reporting

Always document "approximate" in downstream dashboards.

9. Design pattern in streaming stacks

Practical pattern:

1. event consumers hash entity IDs
2. update per-tenant/per-window HLL sketch
3. periodically snapshot sketch to object storage
4. merge for global views in batch layer

This supports near-real-time unique metrics at low infrastructure cost.

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:

1. Minimize Object Creation: Use primitive arrays and reusable buffers.
2. Batching: Group 1,000 small writes into 1 large batch to save I/O cycles.
3. 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.

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, and latencyMs.
• 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:

1. Reduce Context Switching: Use non-blocking I/O (Netty/Project Loom).
2. Minimize GC Pressure: Prefer primitive specialized collections over standard Generics.
3. Data Sharding: Use Consistent Hashing to avoid "Hot Shards."

Technical Trade-offs: Messaging Systems

Key Takeaways

• daily/monthly active users
• unique visitors by campaign
• unique IP estimation for abuse detection

Read Next

• System Design: Designing a Real-time Bidding (RTB) Ad System
• What is Load Balancing? A Simple Guide for Backend Engineers
• Project Case Study: Designing Stripe’s Ledger System

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."