Client

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

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

await stream.ack(event.id); const pipeline = stream.filter(e => e.amount > 100).map(e => ( ...e, fee: e.amount * 0.03 )).on('error', (err) => logger.error(err));

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

Client

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.

const client = new edgekit.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