Recipes

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.

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

const batch = stream.pipe(filter((e) => e.type === 'payment'), batch(100), debounce(5000));

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.

Recipes

Each event flows through a series of transformation stages, with built-in support for filtering, mapping, and conditional routing.

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

The TypeScript types are fully inferred; no manual type assertions needed even with complex nested schemas.