Client

Rate limiting is built in: configure token buckets, sliding windows, or adaptive limits that respond to backpressure.

Error handling is explicit: catch failures at any stage, log them, and route bad events to a dead-letter queue without stopping the main pipeline.

await stream.on('user.created', async (event) =>  console.log(event.data.email); );

Authentication tokens are rotated silently in the background; your code never handles credentials directly.

Client

Rate limiting is built in: configure token buckets, sliding windows, or adaptive limits that respond to backpressure.

const client = new forgecore.Client( auth: 'Bearer token', retry: true, timeout: 30000 );

Rate limiting is built in: configure token buckets, sliding windows, or adaptive limits that respond to backpressure.

See also