Distributed Discord bot platform
Three repos and one system, designed and built solo. A multi-node shard control plane, written instead of using discord.js ShardingManager, with a 28-message master/worker WebSocket protocol, term/epoch fencing-token leases, identify pacing driven by the gateway's own maxConcurrency, least-loaded placement scored on capacity, CPU and event-loop lag, and two-phase live guild migration. Underneath it, a pluggable persistence layer whose Postgres backend hash-partitions guild data 32 ways and enforces single-writer ownership with a compare-and-swap, so a deposed node's writes fail at the database. Alongside it, an orchestration service that turns any public repo or image into a running container across seven language runtimes, with per-container shell, file browser and live logs in the browser.