Back to Course
Chapter 05 • 10

Gauntlet 04: Pub/Sub Broker with Topic Wildcards Basics

12 Lessons • Hands-on practice

01

Gauntlet 04: Pub/Sub Broker with Topic Wildcards

Enterprise message brokers like MQTT and RabbitMQ route events using hierarchical topic trees. Subscribers match routing patterns using single-level wildcards (+) and multi-level catch-all wildcards (#), decoupling producers from specific consumer topologies.

Start
02

Gauntlet 05: Cron Expression Evaluator

Cron expressions evaluate recurring schedules across five fields: minute, hour, day-of-month, month, and day-of-week. Evaluating schedules requires parsing wildcard asterisks (*), discrete comma lists, contiguous hyphen ranges (1-5), and periodic step intervals (*/15).

Start
03

Gauntlet 06: Deterministic JSON Schema Validator

Dynamic API payloads must be strictly validated before touching application logic. A deterministic JSON Schema validator evaluates untrusted dictionaries against structural specifications: verifying data types, checking required keys, inspecting array items, and enforcing numerical boundary limits.

Start
04

Gauntlet 07: Connection Pooler with Health Check

Establishing new database connections on every request consumes TCP handshakes, TLS negotiation, and backend authentication overhead. A thread-safe connection pool manages reusable persistent connections, performs proactive health checks, and transparently replaces dead sockets.

Start
05

Gauntlet 08: B-Tree Index with Range Scans

Hash maps provide O(1) point lookups but fail completely at range queries (WHERE age BETWEEN 20 AND 30). A B-Tree index maintains keys in sorted order, providing O(log N) point searches and O(log N + K) contiguous range scans across key sequences.

Start
06

Gauntlet 09: Prometheus Metrics Collector

Cloud-native observability relies on Prometheus scraping metrics over HTTP /metrics endpoints. The Prometheus text exposition format serializes counters and gauges with multi-dimensional label dimensions and standard metric metadata (# TYPE, # HELP).

Start
07

Gauntlet 10: Leaky Bucket Traffic Shaper

Token and leaky bucket algorithms smooth out bursty network traffic into a steady, predictable output rate. Arriving tokens or request units accumulate up to a maximum bucket capacity, steadily leaking at a configured rate per second to protect downstream APIs from load spikes.

Start
08

Gauntlet 11: Distributed Consensus via Bully Algorithm

Distributed clusters must elect a single coordinator node to avoid split-brain disasters. In Garcia-Molina's Bully Algorithm, when a leader failure is detected, nodes query higher-numbered peers. If no higher peer responds, the inquiring node declares itself coordinator and broadcasts victory.

Start
09

Gauntlet 12: Reverse Proxy Gateway

API gateways like Kong and Envoy shield internal microservices behind a unified public domain. A reverse proxy matches incoming URL prefixes, rewrites path paths for upstream services, enriches headers with tracing IDs and client IPs, and forwards responses transparently.

Start
10

Gauntlet 13: Circuit Breaker with Canary Probing

When a third-party payment gateway or database goes down, hammer-polling it with retries exhausts client threads and slows server crash recovery. A circuit breaker fails fast in the OPEN state, transitions to HALF-OPEN after a backoff cooldown, and uses canary requests to probe service recovery.

Start
11

Gauntlet 14: Dynamic Bytecode JIT Dispatcher

Interpreters waste significant CPU clock cycles on instruction fetch loops, opcode decoding, and operand stack churn. A dynamic JIT specialization dispatcher monitors hot execution paths and dynamically compiles repeated bytecode sequences into native execution kernels, bypassing the virtual machine loop entirely.

Start
12

Gauntlet 15: The Ultimate Production Micro-Engine Final Release

In modern high-performance infrastructure, a production engine is never just business logic. It integrates a write-ahead log for durability, a state machine with snapshots, a rate limiter for fault tolerance, and atomic transaction semantics. When these components mesh deterministically, your engine survives crashes with zero data loss.

Start