reading-streams

Durable stream reading supports live modes including true, false, long-poll, and SSE. You select a mode by passing the desired parameter to the stream method, which determines whether the client catches up on historical data first or maintains a continuous real-time connection.

Stream consumption methods like .json(), .text(), and .body() handle different data formats, while .subscribeJson(), .subscribeText(), and .subscribeBytes() provide continuous event listening. Choose based on whether you need one-time reads, streaming chunks, or persistent subscriptions.

Offset tracking and error handling hooks allow you to manage your position in the stream and recover from interruptions gracefully. By specifying an offset like -1, the client resumes reading from a known checkpoint, ensuring no data is lost during failures.

Yes, durable stream reading supports both Server-Sent Events (SSE) and long-polling as live modes. These options allow client applications to receive real-time updates efficiently, falling back to long-polling when continuous SSE connections are not supported or practical.

Yes, you can process byte streams using the .body(), .bodyStream(), and .subscribeBytes() methods. These APIs provide raw byte access for binary data processing, allowing TypeScript applications to handle non-text payloads directly from the durable stream.

Checkpoint-based processing is needed when your application must guarantee data delivery across interruptions or restarts. By tracking offsets, you ensure the client resumes streaming JSON data from the exact last-processed position rather than missing events or duplicating work.