Lobby API

A simple matching server API.

Development

yarn
yarn deploy

Environment

• STAGE
• REDIS_HOST
• REDIS_PASSWORD
• WS_ENDPOINT
• CALLBACK_URL_PREFIX
• JWT_SECRET_KEY
• CONFIG_BUCKET
• APPS_OBJECT_KEY
• SLACK_WEBHOOK_URL
• SLACK_CHANNEL
• SLACK_LOG_LEVEL
• CONSOLE_LOG_LEVEL

envrc example

# Staging settings
export STAGE="${STAGE:-"dev"}"

# Infrastructure settings
export REDIS_HOST="redis-host"
export REDIS_PASSWORD="redis-password"

# Messaging settings
export WS_ENDPOINT="web.socket.endpoint/example"
export CALLBACK_URL_PREFIX="https://callback-url.api.tld/lobby/invoked"

# Authentication settings
export JWT_SECRET_KEY="jwt-secret-key-which-is-same-with-auth-api"

# Configuration settings
export CONFIG_BUCKET="lobby-config-bucket-example"
export APPS_OBJECT_KEY="lobby-apps-object-example"

# Logger settings
# export SLACK_WEBHOOK_URL="https://hooks.slack.com/services/TXXXXXXXX/BXXXXXXXXXXXX/XXXXXXXXXXXXXXXXXXXXXXXX"
# export SLACK_CHANNEL="CXXXXXXXXX"
# export SLACK_LOG_LEVEL="warn"
# export CONSOLE_LOG_LEVEL="trace"

Quick start

To authenticate, we should deploy auth-api first.

1. Get authorization token from auth-api using application(game-id).
2. Connect to lobby-api with authorization.
3. Send match message.
4. After matched, it received matched messsage like this.
5. Or, its connection is dropped.

For example, application is very-complex-id-like-uuid then,

# Step 1. Get authorization token.
$ curl -XPOST https://auth.api.url/simple -d '{"name":"lacti","email":"lactrious@gmail.com","application":"very-complex-id-like-uuid"}'
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYW1lIjoibGFjdGkiLCJlbWFpbCI6ImxhY3RyaW91c0BnbWFpbC5jb20iLCJhcHBsaWNhdGlvbiI6InZlcnktY29tcGxleC1pZC1saWtlLXV1aWQiLCJpYXQiOjE2MjEwNjUzNTQsImV4cCI6MTYyMTA2ODk1NH0.SECRET_ENCODED

# Step 2. Connect lobby-api with authorization query parameter.
$ yarn wscat -c "wss://lobby.websocket.url/?authorization=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYW1lIjoibGFjdGkiLCJlbWFpbCI6ImxhY3RyaW91c0BnbWFpbC5jb20iLCJhcHBsaWNhdGlvbiI6InZlcnktY29tcGxleC1pZC1saWtlLXV1aWQiLCJpYXQiOjE2MjEwNjUzNTQsImV4cCI6MTYyMTA2ODk1NH0.SECRET_ENCODED"

Connected (press CTRL+C to quit)
# Step 3. Send "match" message.
> {"type":"match","application":"very-complex-id-like-uuid"}

# Step 4. Receive "matched" message if matching is completed.
< {"type":"match","url":"wss://game.websocket.url/","gameId":"3d73ccc8-b755-418f-8b78-f4badfc9c4b4","playerId":"c4409ca4-58a5-41dc-a5cf-433bd58778a0"}

# Step 4-1. And then, lobby server disconnects this connection.
Disconnected (code: 1000, reason: "Connection Closed Normally")

# Step 5. Or, there are no matchable other users, disconnects this connection after about `maxWaitingMillis` milliseconds.
Disconnected (code: 1000, reason: "Connection Closed Normally")

And then, connect a game server using ${url}?x-game-id=${gameId}&x-member-id=${playerId} URL. This is a simple convention from gamebase module.

Test script

We can use cli-connect.js script to easily see how to make a connection with game server via lobby api. It uses below two parameters.

• application which is registered in APPS_OBJECT_KEY file in CONFIG_BUCKET.
• auth-api-url which is deployed auth-api server.

For example, we can run this script like this.

$ node cli-connect.js "awesome-application-id" "https://auth.api.url"
{ stage: 'dev' }
{
  application: 'very-complex-id-like-uuid',
  authUrl: 'https://auth.api.url',
  name: 'test45'
}
{
  authorization: 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYW1lIjoibGFjdGkiLCJlbWFpbCI6ImxhY3RyaW91c0BnbWFpbC5jb20iLCJhcHBsaWNhdGlvbiI6InZlcnktY29tcGxleC1pZC1saWtlLXV1aWQiLCJpYXQiOjE2MjEwNjUzNTQsImV4cCI6MTYyMTA2ODk1NH0.SECRET_ENCODED'
}
{
  lobbyUrl: 'wss://lobby.websocket.url/?authorization=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYW1lIjoibGFjdGkiLCJlbWFpbCI6ImxhY3RyaW91c0BnbWFpbC5jb20iLCJhcHBsaWNhdGlvbiI6InZlcnktY29tcGxleC1pZC1saWtlLXV1aWQiLCJpYXQiOjE2MjEwNjUzNTQsImV4cCI6MTYyMTA2ODk1NH0.SECRET_ENCODED'
}
{
  matchRequest: {
    type: 'match',
    application: 'very-complex-id-like-uuid'
  }
}
{
  matchResponse: {
    type: 'match',
    url: 'wss://game.websocket.url/',
    gameId: '8c159981-95aa-427c-b26f-62be08374af9',
    playerId: '12e62380-6a01-487a-9507-8414c6de4640'
  }
}
{
  gameId: '8c159981-95aa-427c-b26f-62be08374af9',
  playerId: '12e62380-6a01-487a-9507-8414c6de4640',
  gameUrl: 'wss://game.websocket.url/?x-game-id=8c159981-95aa-427c-b26f-62be08374af9&x-member-id=12e62380-6a01-487a-9507-8414c6de4640'
}
Connected.
{
  data: '{"type":"enter","payload":{"memberId":"12e62380-6a01-487a-9507-8414c6de4640"}}'
} Data received
{ data: '{"type":"stage","payload":{"stage":"wait","age":0}}' } Data received
{ data: '{"type":"stage","payload":{"stage":"running","age":0}}' } Data received
{ data: '{"type":"stage","payload":{"stage":"running","age":1}}' } Data received
...
{ data: '{"type":"stage","payload":{"stage":"running","age":60}}' } Data received
{ data: '{"type":"stage","payload":{"stage":"end","age":60}}' } Data received
Disconnected.

This game server is basic example from 1team-mmo-backend.

Server list

We can manage Server list using manage-apps.sh script. We can write a server list file which its name is APPS_OBJECT_KEY. For example, APPS_OBJECT_KEY is server-list, the result of cat "server-list" is like this.

{
  "very-complex-id-like-uuid": {
    "id": "very-complex-id-like-uuid",
    "url": "wss://game.websocket.url",
    "functionName": "arn:aws:lambda:AWS_REGION:AWS_ACCOUNT_ID:function:GAME_LAMBDA_FUNCTION_NAME",
    "memberCount": 2,
    "incompletedMatchingWaitMillis": 10000,
    "maxWaitingMillis": 60000
  }
}

And you can read it from S3 Bucket CONFIG_BUCKET via ./manage-apps.sh get and upload this file into S3 Bucket via ./manage-apps.sh set.

• Lobby server will disconnects after maxWaitingMillis milliseconds if there are no matchable users.
• Lobby server can make matching group less than memberCount if cannot find matchable users anymore after incompletedMatchingWaitMillis milliseconds.

License

MIT