Skip to content
HeyJared

Hands On System Design Course - Code Everyday

Build a complete, production-ready distributed log processing system from scratch. Each day features practical, hands-on tasks with concrete outputs that incrementally develop your expertise in distributed systems architecture, scalable data processing.

Newsletter · By System Design Course · English · Paid tier available · Official site

Indexed issues, last 90 days
16
Latest publication
Sep 29, 2026
Audience
Checking…
Earliest in this view
Aug 25, 2026

Latest issues

  1. Issue · Sep 29, 2026

    Day 78: Build a Machine Learning Pipeline for Log Classification (opens the original)

    Excerpt · Critical tone

    Read excerpt

    What We’re Building TodayA real-time ML inference pipeline that classifies incoming logs by severity (DEBUG/INFO/WARN/ERROR/FATAL) and category (Security, Performance, Business, Infrastructure)A feature extraction service that transforms raw log strings into numeric vectors using TF-IDF and regex-driven heuristicsA model serving layer backed by a Spring Boot microservice with Redis-cached predictions and Kafka-driven async classificationA feedback loop that persists misclassification si

  2. Issue · Sep 26, 2026

    Week 15: Advanced Operational Features (opens the original)

    Excerpt

    Read excerpt

    OpsForge Platform Operations HubYour log platform can ingest a million events per second and still go dark at 3 AM because nobody was watching the control plane. Datadog unifies health checks, deploy tracking, and cost dashboards for exactly this reason — the data plane does the work; the control plane keeps it alive. Today you wire all seven Week 15 modules into one orchestrator.What You’re Building TodayYou are not building seven separate tools. You are building one operations control plane th

  3. Issue · Sep 24, 2026

    Day 183: Distributed Semaphores — Resource Limiting Across Components (opens the original)

    Excerpt

    Read excerpt

    What We’re Building TodayA distributed semaphore service that limits concurrent access to shared log processing resourcesAn HTTP API backed by SQLite with atomic acquire/release and TTL-based expiryA simulation of 8 competing log processor workers contending for permitsA live web dashboard showing semaphore utilization, waiters, and event streamThe Problem: Too Many Workers, Not Enough ResourcesPicture your log processing cluster running hot. 30 worker processes all try to flush to the same data

  4. Issue · Sep 22, 2026

    Day 77: Adaptive Resource Allocation for Log Processing Pipelines (opens the original)

    Excerpt

    Read excerpt

    What We’re Building TodayA Resource Allocator service that watches Kafka consumer lag, JVM heap pressure, and CPU utilization across the log-consumer fleet and computes a target concurrency level every scrape intervalAn AdaptiveResourceManager inside log-consumer that resizes its internal thread pool and Kafka listener concurrency at runtime, without a restart or redeployA scaling decision audit trail persisted in PostgreSQL, so every scale-up/scale-down event is explainable after the factA cont

  5. Issue · Sep 19, 2026

    Week 8: Distributed Log Search (opens the original)

    Excerpt

    Read excerpt

    Distributed Log Search That Stays Fast as Volume GrowsWhen engineers debug production, they do not want a table scan across terabytes of raw lines—they need sub-second ranked retrieval with filters that match how incidents actually look: service, severity, region, and free-text symptoms. This platform turns continuous log ingest into a partitioned inverted index with scatter-gather query, facets, and a guarded search API.What We BuiltA Spring Boot search service with an in-process inverted index

Publishing over time

Last 90 days. Choose a month to open its work.

Recurring subjects

Named in the text we hold. One piece can cover several.

Audience

No verified audience measurement yet.

About this data

Counts cover the work we have indexed. Tone needs enough text and a confident classification. Excerpts and episode notes are not full articles or transcripts.

Identity or attribution wrong? Suggest a correction.

See coverage about Hands On System Design Course - Code Everyday