A high-throughput, eventually consistent gossip protocol implementation. Designed to pass the Maelstrom distributed systems test suite with strict latency and validity guarantees.

Design & Architecture

This node implements a fan-out architecture optimized for high-latency, partition-prone networks.

• Temporal Batching: Implements a Nagle-like aggregation strategy. Messages are buffered and flushed via a 15ms ticker, reducing RPC overhead and network IOPS by ~90% compared to naive forwarding.
• Asynchronous Pipelining: Decouples message ingestion from propagation. Inbound broadcasts are immediately committed to local state (sync.RWMutex), while outbound propagation is handled by dedicated, non-blocking neighbor workers.
• Backpressure & Flow Control: Utilizes per-neighbor semaphores (buffered channels, cap=10) to limit inflight RPCs. This prevents head-of-line blocking and manages resource saturation during partition recovery.
• Reliability: Ensures at-least-once delivery via explicit RPC acknowledgments. Failed or timed-out batches are automatically re-queued for retry.

Benchmarks

Performance was evaluated using a 25-node cluster arranged in a 4-ary tree topology, simulating widespread network latency.

Test Configuration:

• Nodes: 25
• Topology: Tree4
• Network Latency: 100ms (simulated)
• Throughput: 100 messages/sec
• Duration: 20s

Results:

Maelstrom Serve

\ \

Usage

Build

go build -o node main.go

Reproduction Requires the Maelstrom binary.

./maelstrom test -w broadcast \
    --bin ./node \
    --node-count 25 \
    --topology tree4 \
    --time-limit 20 \
    --rate 100 \
    --latency 100

The Problem

Traditional CMSes are bloated and slow. Static site generators lack dynamic features.

The Solution

A hybrid approach that pre-renders content at build time but hydrates interactive islands on the client.

Results

• 95+ Lighthouse scores
• Sub-second page loads
• SEO-optimized out of the box

What It Does

An open-source design system with accessible components and beautiful defaults. Designed for rapid prototyping.

Why I Built It

I needed a consistent set of UI primitives that worked across multiple projects without the overhead of a full component library.

Highlights

• 40+ components with full a11y support
• Dark mode built-in
• Copy-paste friendly code snippets