Implement and Tune HyperLogLog for Trace-Stream Cardinality in Go
Overview
What this challenge is about.
Implement HyperLogLog from scratch in Go, run accuracy sweeps, and recommend a register count under memory budget. Earn a verifiable certificate.
The Brief
What you'll do, and what you'll demonstrate.
Choose and justify a HyperLogLog register count that achieves under 2 percent 95th-percentile error on per-minute distinct trace counts within a 256 kilobyte-per-minute memory budget.
Earning criteria — what you'll demonstrate
- Implement a probabilistic cardinality sketch from its primary-source specification
- Quantify the accuracy-versus-memory trade-off of a randomized algorithm empirically
- Reconcile measured error with a theoretical error bound honestly
- Translate an algorithmic analysis into an actionable infrastructure recommendation
- Reason about fixed memory budgets in a high-throughput ingestion system
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Aligned coursework coming soon.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Backend Engineer, Data Infrastructure
This challenge mirrors real ingestion-team work: implementing a memory-bounded sketch in Go, benchmarking it on production-shaped traces, and shipping a configuration recommendation that survives a fixed RAM budget at high event volume.
This challenge sharpens
- sketching
- go
- benchmarking
Algorithms Engineer
You translate a primary-source algorithm into working code and validate measured behavior against a theoretical bound, the core loop of building and trusting randomized data structures in production systems.
This challenge sharpens
- randomized-algorithms
- algorithm-analysis
- data-structures
Observability Platform Engineer
Estimating distinct trace counts under tight memory limits is everyday observability work; you practice reasoning about accuracy-versus-cost trade-offs and communicating a defensible configuration to a platform team.
This challenge sharpens
- sketching
- benchmarking
- algorithm-analysis