Skip to content

Make matchmaking-service multi-instance safe #16

Description

@TexablePlum

The scanning matchmaking scheduler would double-match players if two instances ran, and presence
tracking is in-memory. Leader election for the scan loop (ShedLock is sufficient) plus atomic
queue operations in Redis.

Metadata

Metadata

Assignees

No one assigned

    Labels

    scalingMulti-instance and scale-out readiness

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions