CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
๐ŸŒ™โ˜€๏ธ
Log inStart free
Home/Templates/Gaming

๐ŸŽฎ Gaming ยท Data Flow

Game Leaderboard Data Pipeline

How match results turn into leaderboards and rankings: result events, anti-cheat checks, rating updates and cached leaderboards.

More Gaming templates

Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.

Drawing diagramโ€ฆ

What this diagram shows

  • Results are validated by anti-cheat before counting
  • Skill ratings (Elo/MMR) update after each match
  • Global, regional and friends leaderboards are cached

Prompt used

Data flow for leaderboards: game servers send match result events to Kafka, an anti-cheat service checks for impossible stats and flags suspicious results, valid results update player skill ratings (MMR), scores go into Redis sorted sets for global, regional and friends leaderboards, season-end snapshots are stored in the database for rewards, and the game client reads leaderboards through an API.

Mermaid code
flowchart LR
subgraph EXT ["External entities"]
gs["Game Servers"]
mod["Anti-cheat Moderators"]
cl["Game Clients"]
end
subgraph PROC ["Processes"]
p1("1.0 Ingest match results")
p2("2.0 Check for cheating")
p3("3.0 Update skill ratings (MMR)")
p4("4.0 Serve leaderboards")
p5("5.0 Snapshot season and grant rewards")
end
subgraph STORE ["Data stores"]
d1[("D1 Match Event Stream (Kafka)")]
d2[("D2 Leaderboards (Redis sorted sets)")]
d3[("D3 Season Results")]
end
gs -->|"Match result events"| p1
p1 -->|"Match events"| d1
d1 -->|"Match events"| p2
p2 -->|"Suspicious results"| mod
mod -->|"Review decisions"| p2
p2 -->|"Valid results"| p3
p3 -->|"Global, regional and friends scores"| d2
d2 -->|"Ranked scores"| p4
cl -->|"Leaderboard requests"| p4
p4 -->|"Leaderboard pages"| cl
d2 -->|"Season-end standings"| p5
p5 -->|"Season snapshot"| d3
p5 -->|"Reward grants"| cl

Inside this diagram

A data flow diagram with 8 processes and outside parties, 3 data stores and 13 data flows.

Processes and outside parties

  • Game Servers
  • Anti-cheat Moderators
  • Game Clients
  • 1.0 Ingest match results
  • 2.0 Check for cheating
  • 3.0 Update skill ratings (MMR)
  • 4.0 Serve leaderboards
  • 5.0 Snapshot season and grant rewards

Data stores

  • D1 Match Event Stream (Kafka)
  • D2 Leaderboards (Redis sorted sets)
  • D3 Season Results

Data flows

  • Game Servers โ†’ 1.0 Ingest match results: Match result events
  • 1.0 Ingest match results โ†’ D1 Match Event Stream (Kafka): Match events
  • D1 Match Event Stream (Kafka) โ†’ 2.0 Check for cheating: Match events
  • 2.0 Check for cheating โ†’ Anti-cheat Moderators: Suspicious results
  • Anti-cheat Moderators โ†’ 2.0 Check for cheating: Review decisions
  • 2.0 Check for cheating โ†’ 3.0 Update skill ratings (MMR): Valid results
  • 3.0 Update skill ratings (MMR) โ†’ D2 Leaderboards (Redis sorted sets): Global, regional and friends scores
  • D2 Leaderboards (Redis sorted sets) โ†’ 4.0 Serve leaderboards: Ranked scores
  • Game Clients โ†’ 4.0 Serve leaderboards: Leaderboard requests
  • 4.0 Serve leaderboards โ†’ Game Clients: Leaderboard pages
  • D2 Leaderboards (Redis sorted sets) โ†’ 5.0 Snapshot season and grant rewards: Season-end standings
  • 5.0 Snapshot season and grant rewards โ†’ D3 Season Results: Season snapshot
  • 5.0 Snapshot season and grant rewards โ†’ Game Clients: Reward grants

Boundaries

  • External entities: Game Servers, Anti-cheat Moderators and Game Clients
  • Processes: 1.0 Ingest match results, 2.0 Check for cheating, 3.0 Update skill ratings (MMR), 4.0 Serve leaderboards and 5.0 Snapshot season and grant rewards
  • Data stores: D1 Match Event Stream (Kafka), D2 Leaderboards (Redis sorted sets) and D3 Season Results

Make your own diagram like this

Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.

Related templates

C4 ArchitectureProGaming

Multiplayer Game Backend Architecture

The backend for an online multiplayer game: player accounts, matchmaking, dedicated game servers, leaderboards and in-game purchases.

SequenceGaming

Game Matchmaking Sequence

How a player gets into a match: joining the queue, skill-based matching, server allocation and connecting to the game server.

State MachineGaming

Multiplayer Game Session States

The states of an online match on a game server: lobby, loading, in progress, pauses, reconnects and results.

DeploymentProGaming

Global Game Server Deployment

How an online game runs servers close to players worldwide: regional fleets, a global matchmaker, and central account and store services.

FlowchartGaming

In-App Purchase Flow

How an in-game purchase is completed safely: store purchase, receipt validation on the server, granting items and handling refunds.

Database ERDGaming

Game Player and Inventory Schema

Tables for an online game: players, characters, items, inventories, currencies, purchases and match history.