App Managers

The app manager is the source of truth for application credentials, limits, and webhook configurations. Every WebSocket connection and API request is validated against the app manager.

Drivers

Set the driver:

APP_MANAGER_DRIVER=memory

{ "app_manager": { "driver": "memory" } }

Memory Driver

The default driver. Apps are defined inline in config.json or bootstrapped via environment variables. Data is not persisted - apps are lost on restart.

{
  "app_manager": {
    "driver": "memory",
    "array": {
      "apps": [
        {
          "id": "my-app-id",
          "key": "my-app-key",
          "secret": "my-app-secret",
          "enabled": true,
          "enable_client_messages": true,
          "max_connections": 100000,
          "max_client_events_per_second": 1000
        }
      ]
    }
  }
}

You can also bootstrap a default app entirely from environment variables:

SOCKUDO_DEFAULT_APP_ID=my-app-id
SOCKUDO_DEFAULT_APP_KEY=my-app-key
SOCKUDO_DEFAULT_APP_SECRET=my-app-secret
SOCKUDO_DEFAULT_APP_ENABLED=true

See Environment Variables for all SOCKUDO_DEFAULT_APP_* options.

MySQL Driver

Stores apps in a MySQL table with automatic schema migrations. Includes built-in query caching.

{
  "app_manager": {
    "driver": "mysql"
  },
  "database": {
    "mysql": {
      "host": "localhost",
      "port": 3306,
      "username": "sockudo",
      "password": "secret",
      "database": "sockudo",
      "table_name": "applications"
    }
  }
}

Connection Pooling

MySQL connections are pooled automatically:

You can also set global pool limits:

DATABASE_POOLING_ENABLED=true
DATABASE_POOL_MIN=2
DATABASE_POOL_MAX=10

Query Caching

App lookups are cached in-memory to avoid repeated database queries:

Table Schema

Sockudo auto-creates the table and migrates new columns automatically. The table includes:

• id, key, secret - Core credentials
• max_connections, max_client_events_per_second - Limits
• enable_client_messages, enabled - Flags
• webhooks - JSON column for webhook definitions
• allowed_origins - JSON column for origin restrictions
• All optional per-app limit fields

PostgreSQL Driver

Same features as MySQL, adapted for PostgreSQL. Uses JSONB columns and PostgreSQL-native syntax.

{
  "app_manager": {
    "driver": "postgres"
  },
  "database": {
    "postgres": {
      "host": "localhost",
      "port": 5432,
      "username": "sockudo",
      "password": "secret",
      "database": "sockudo"
    }
  }
}

APP_MANAGER_DRIVER=postgres
DATABASE_POSTGRES_HOST=localhost
DATABASE_POSTGRES_PORT=5432
DATABASE_POSTGRES_USERNAME=sockudo
DATABASE_POSTGRES_PASSWORD=secret
DATABASE_POSTGRES_DATABASE=sockudo

Connection pooling and query caching work identically to MySQL.

DynamoDB Driver

Stores apps in a single DynamoDB table with the id field as the partition key.

{
  "app_manager": {
    "driver": "dynamodb"
  },
  "database": {
    "dynamodb": {
      "region": "us-east-1",
      "table_name": "sockudo-applications"
    }
  }
}

For local development with DynamoDB Local:

DATABASE_DYNAMODB_ENDPOINT_URL=http://localhost:8000

Authentication

DynamoDB uses standard AWS credential resolution:

1. Environment variables: AWS_ACCESS_KEY_ID + AWS_SECRET_ACCESS_KEY
2. AWS profile: aws_profile_name in config
3. IAM role (ECS task role, EC2 instance profile)

AWS_ACCESS_KEY_ID=AKIA...
AWS_SECRET_ACCESS_KEY=secret...

ScyllaDB Driver

High-performance driver using ScyllaDB (or Apache Cassandra). Automatically creates the keyspace, table, and secondary indexes.

{
  "app_manager": {
    "driver": "scylladb",
    "scylladb": {
      "nodes": ["10.0.0.1:9042", "10.0.0.2:9042"],
      "keyspace": "sockudo",
      "table_name": "applications",
      "username": "cassandra",
      "password": "cassandra",
      "replication_class": "NetworkTopologyStrategy",
      "replication_factor": 3
    }
  }
}

A secondary index on the key column is created automatically for fast key-based lookups.

App Manager Caching

All database-backed drivers (MySQL, PostgreSQL, DynamoDB, ScyllaDB) are automatically wrapped in a caching layer. This is separate from the cache driver and is configured under app_manager.cache:

{
  "app_manager": {
    "cache": {
      "enabled": true,
      "ttl": 300
    }
  }
}

The cache is:

• Read-through: on cache miss, fetches from the database and stores in cache.
• Write-through: on app update/delete, invalidates cache immediately.
• Keyed by both app ID and app key for fast lookups in either direction.

App Configuration Fields

Each app supports these fields:

Choosing a Driver

• Development: Use memory with inline apps or env vars.
• Single-node production: mysql or postgres with connection pooling.
• Multi-node production: Any database driver works since all nodes read from the same source.
• AWS-native: dynamodb with IAM roles.
• High-throughput: scylladb for lowest latency at scale.