Single-table DynamoDB design for a real-time game (rooms, rounds, leaderboards)

<p>Two new games live at <a href="https://play.pickuma.com" rel="noopener noreferrer">play.pickuma.com</a>: a single-button time-sense test called <strong><a

<blockquote> <p>Submission for the [DEV Weekend Challenge — Passion Edition].<br /> (<a

<h2> How I Built a Real-Time Quiz Platform with Next.js, WebSockets, and Learning Science </h2> <p>A good live quiz has two jobs.</p> <p>First, it should make a room feel awake.

<p>In the late 90s, my brother, my cousin, and I would crowd around a single PC and play Atomic Bomberman for hours. Arrow keys and WASD, elbows bumping, trash talk flying. It was

<h2> 1. Intro — The Problem We Actually Had </h2> <p>Building real-time systems is often presented as a distributed systems problem.</p> <p>Kafka, stream processors, event buses,

<h2> The Problem We Were Actually Solving </h2> <p>Our feature team owned the high-score leaderboard that surfaced the top 100 players every second. The stack was simple: Postgres

<p>A few months ago I shipped <a href="https://l2calendar.com" rel="noopener noreferrer">L2 Calendar</a>, a tracker for Lineage 2 private server openings. Players kept asking the

<div class="highlight js-code-highlight"> <pre class="highlight markdown"><code><span class="p">[</span><span class="nv">BingWow</span><span class="p">](</span><span