soketi

Fixed NPM release

Added NATS adapter (https://github.com/soketi/soketi/pull/317)

NATS is an alternative to Redis PubSub for intra-process communication. Starting with this version, you may use the NATS adapter instead of Redis Pub/Sub. The driver is available for testing and you may use it with your NATS server.

The expectation for NATS is to increase the performance and prepare soketi for more robust features in distributed systems, offered by NATS, such as more KV operations support, like incr or add, as this will allow using the built-in Key-Value storage for rate limiters.

Added init() handlers for adapters and closing connections after server gets closed

With the introduction of NATS, there was the need of making sure the adapters initialize before the server bootstrapping runs. This way, the adapters will now behave predictably.

As a result, the app got some polishing for the namespaces and plugins (adapters, rate limiters, queue managers), so that after the server closes, the handlers for their respective connections (like Redis connections or NATS connections) would close without suspending them. The sockets will also be evicted from memory on each server close.

We tested it thoroughly and it's not expected to break anything.

Fixes and other additions

• Fixed some race conditions throughout the app
• Added more options to the benchmark environment
• Added debugging when the app is not found
• Added SQS batching support (for cost savings)
• Added more metrics for the horizontal adapters
• Added separate custom options for pub and sub clients for the Redis adapter
• Fixed webhook sender's promise by checking in as done after the entire job finishes
• Fixed webhook sender's behavior by not sending webhook events if no webhooks are defined

Hotfixed the previous patch

• Fixed PM2 errors with the config parameter (https://github.com/soketi/soketi/pull/318)

• Added SQS driver for queues (https://github.com/soketi/soketi/pull/156)
• Added Redis Cluster support for the Redis Rate Limiter and Redis Adapter (https://github.com/soketi/soketi/pull/308)

1. Limits on an app-by-app basis

Starting with this version, you can set maximum presence channel members' size, maximum presence channel members count, and other limits at the app-level, with fallback to the server-declared defaults.

MySQL

You need to add the following fields to your table:

`max_presence_members_per_channel` tinyint(1) NULL,
`max_presence_member_size_in_kb` tinyint(1) NULL,
`max_channel_name_length` tinyint(1) NULL,
`max_event_channels_at_once` tinyint(1) NULL,
`max_event_name_length` tinyint(1) NULL,
`max_event_payload_in_kb` tinyint(1) NULL,
`max_event_batch_size` tinyint(1) NULL

Setting any of them to null or '' will ignore the setting, and use the limits associated with the server-level declared defaults

Existing apps running on <0.29.0 will still work even if you don't have these fields added after the migration to 0.29.0. You should add these fields to keep your database up-to-date or to have the choice to, later on, imply limits to your apps.

PostgreSQL

You need to add the following fields to your table:

max_presence_members_per_channel integer DEFAULT NULL,
max_presence_member_size_in_kb integer DEFAULT NULL,
max_channel_name_length integer DEFAULT NULL,
max_event_channels_at_once integer DEFAULT NULL,
max_event_name_length integer DEFAULT NULL,
max_event_payload_in_kb integer DEFAULT NULL,
max_event_batch_size integer DEFAULT NULL

Setting any of them to null or '' will ignore the setting, and use the limits associated with the server-level declared defaults

Existing apps running on <0.29.0 will still work even if you don't have these fields added after the migration to 0.29.0. You should add these fields to keep your database up-to-date or to have the choice to, later on, imply limits to your apps.

DynamoDB

Your items in DynamoDB can have the following new fields:

MaxPresenceMembersPerChannel: { N: '-1' },
MaxPresenceMemberSizeInKb: { N: '-1' },
MaxChannelNameLength: { N: '-1' },
MaxEventChannelsAtOnce: { N: '-1' },
MaxEventNameLength: { N: '-1' },
MaxEventPayloadInKb: { N: '-1' },
MaxEventBatchSize: { N: '-1' },

Not setting any of the above fields will ignore the setting, and will fallback to the limits associated with the server-level declared defaults.

Existing apps running on <0.29.0 will still work even if you don't have these fields added after the migration to 0.29.0. You should add these fields to keep your database up-to-date or to have the choice to, later on, imply limits to your apps.

2. Added MODE variable for the running mode

The app itself is full-stack, meaning it works as an HTTP API, WebSocket Server, and Queue processor, all at once. The MODE variable is now introduced to help you scale apps that use external drivers (like Redis for queue). You may want to have two fleets: one that actively interacts with the userbase HTTP/WS, and one fleet that scales independently to process queues for webhooks.

MODE=full

The default mode, and is the mode in which the apps <0.29.0 currently run. (no breaking changes expected for this feature)

MODE=server

It does not process queues. It will only serve HTTP/WS requests to your clients.

MODE=worker

You need to pair this specific mode setting with PORT to choose a different port to run on. The servers running in this mode will have an HTTP server running so that you can check for /metrics, / (health checks), and /ready (readiness checks). There are NO WebSocket endpoints running.

• Added /accept-traffic endpoint to see if new traffic can be redirected to the current instance (https://github.com/soketi/soketi/commit/537d420ff70aaa560ce9de1b4a0952ad14b27e40)

Patched package-lock.json

• Added support for ARM containers (https://github.com/soketi/soketi/pull/154)
• Added SSL_CA variable to specify the CA file path (https://github.com/soketi/soketi/pull/285)
• Added failsafe error for clients that send messages before pusher:connection_established is sent (https://github.com/soketi/soketi/pull/287)
• Patched async (https://github.com/soketi/soketi/pull/273)

• Fixed filtration signature only for non-batch webhooks (https://github.com/soketi/soketi/pull/284)

• Fixed .send() fails that looked at backpressure in a wrong way or that tried to send messages to already closed sockets (https://github.com/soketi/soketi/pull/282)
• Fixed DynamoDB's endpoint failing when credentials were set (https://github.com/soketi/soketi/pull/283, @atymic)

• Locking dependencies to avoid issues with the packages upgrading out-of-the-blue (https://github.com/soketi/soketi/pull/277)

• Webhooks can now send events in batches just like Pusher (https://github.com/soketi/soketi/pull/249, @Daynnnnn)
• Bumped & patched some dev packages (https://github.com/soketi/soketi/pull/239, https://github.com/soketi/soketi/pull/250, https://github.com/soketi/soketi/pull/266, https://github.com/soketi/soketi/pull/267, @stayallive)
• Bumped & patched some production packages (https://github.com/soketi/soketi/pull/263, @stayallive)

• Fixed PresenceMember types within the app (no effect on servers) (https://github.com/soketi/soketi/pull/248, thanks @stayallive for pointing out)
• Added /batch_events endpoint (https://github.com/soketi/soketi/pull/243, thanks to @stayallive for review 👍)
• • For /events and /batch_events, in case the payload is too big, the app will return 413 instead of 400, according to the documentation

• Fixed a bug where sending an empty POST request would crash the running server (https://github.com/soketi/soketi/pull/246)

• Fixed a bug where queued jobs in Redis would not retry and build up in-memory (https://github.com/soketi/soketi/pull/229, @stayallive)
• Added custom headers for webhooks (https://github.com/soketi/soketi/pull/226, @stayallive)
• Added support for JSON config file as alternative to environment variables (https://github.com/soketi/soketi/pull/228)