Skip to content

Define shard-ready Nakama account routing and database operations #83

Open
Open
Define shard-ready Nakama account routing and database operations#83
Labels
area:devopsCI, deployment, build, and infrastructure workflowarea:nakamaNakama runtime, storage, auth, social, or backend modulesdocumentationImprovements or additions to documentationpriority:p2Important but not blocking current milestonesize:mMedium task
Milestone
Foundation
@JOY

Description

@JOY
JOY (JOY)
opened on May 18, 2026

Project: Second Spawn
Area: Nakama
Milestone: Foundation
Priority: P2
Size: M
Review Gate: Local Review
Verification: Docs Lint

Goal

Document how SECOND SPAWN can scale Nakama OSS by explicit shards without pretending multiple OSS nodes against one logical database are a cluster.

Scope

  • Define global account, wallet, entitlement, home shard, and current shard mapping.
  • Define one logical database per Nakama OSS shard, even if databases share one physical Postgres server or cluster.
  • Identify which state is global and which state is shard-local.
  • List migration and player-transfer constraints for later.

Acceptance Criteria

  • Architecture docs show the shard model clearly.
  • The plan rejects multiple Nakama OSS instances sharing one logical database.
  • Follow-up implementation tasks are listed if needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:devopsCI, deployment, build, and infrastructure workflowarea:nakamaNakama runtime, storage, auth, social, or backend modulesdocumentationImprovements or additions to documentationpriority:p2Important but not blocking current milestonesize:mMedium task

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Second Spawn

    Status

    Backlog

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions