Blueprint Canvas

Global Trivia Game

1M target users, 50k peak concurrent users, and US + EU traffic.. Live answer events need low-latency writes while score settlement and schema lineage need relational facts.

Architecture

Entities

User

Aurora DSQL

Owned relationally for support and account lifecycle queries.

GameSession

Aurora DSQL

Stored as relational facts with versioned launch settings.

AnswerEvent

DynamoDB

Stored as high-frequency DynamoDB workload events keyed by run, game, shard, and region.

Score

Hybrid

DynamoDB receives event stream; Aurora stores settled score lineage and schema versions.

LeaderboardEntry

DynamoDB

Leaderboard reads use region and bucket dimensions to avoid one hot global key.

Region

Aurora DSQL

Used to make regional data-domain decisions explicit.

SchemaVersion

Aurora DSQL

Links recommendation versions to generated SQL and DynamoDB design.

SimulationRun

Hybrid

Aurora stores run summaries while DynamoDB stores event timelines.

Generated flow

AP-01

Update score

Settle a score after answer validation and keep replayable history.

AP-02

Read regional leaderboard

Read a top-N leaderboard by region and rolling time window.

AP-03

Read global leaderboard

Read the global top leaderboard across regions.

AP-04

Join live session

Load session state and register a player into a live game.

AP-05

Read user profile

Load support and profile facts for a player.

AP-06

Replay session history

Replay disputed answer events for a player or game round.

AP-07

Submit answer event

Append a player answer during a live quiz round.

Database Mapping

Aurora DSQL

Project metadata and B2B workspace records
Access pattern registry and recommendation versions
Schema versions, simulation summaries, reports

DynamoDB

Answer events and representative workload telemetry
Leaderboard read/write samples and hot-key metrics
Run timeline, event replay, risk-indexed samples

Access Patterns

Each row is persisted and feeds the recommendation version.

Pattern	Latency	Database	Peak QPS
Update score Use DynamoDB for events and Aurora for authoritative settlement lineage. Impact: QPS 8,000 -> 8,000; hot risk high; shards 20.	90 ms	Hybrid	8,000
Read regional leaderboard Bucket regional leaderboard keys and publish async projections. Impact: QPS 4,500 -> 4,500; hot risk moderate; shards 12.	60 ms	DynamoDB	4,500
Read global leaderboard Avoid writing every update into LEADERBOARD#GLOBAL. Impact: QPS 3,000 -> 3,000; hot risk moderate; shards 8.	80 ms	DynamoDB	3,000
Join live session Keep live session facts queryable while avoiding synchronous global writes. Impact: QPS 2,500 -> 2,500; hot risk moderate; shards 7.	70 ms	Hybrid	2,500
Read user profile SQL-addressable user facts help support, audit, and B2B reporting. Impact: QPS 900 -> 900; hot risk moderate; shards 4.	120 ms	Aurora DSQL	900
Replay session history DynamoDB replays event timelines while Aurora stores settled score facts. Impact: QPS 700 -> 700; hot risk moderate; shards 4.	150 ms	Hybrid	700
Submit answer event A single GAME#gameId key becomes critical during finals; shard answer writes. Impact: QPS 13,000 -> 13,000; hot risk critical; shards 33.	50 ms	DynamoDB	13,000