Queries need result bounds

A timeout20 can limit waiting while leaving a large result problem intact. Limit query results explicitly and choose a bounded consumption path.

Book basis: B433.

Failure it prevents

One query exhausts memory despite a concurrency limit of one.

Our Effect 4.0.0 reading

Stream.take bounds consumption of a real stream. It cannot undo a driver’s full allocation. Apply limits or cursor pagination in the query adapter27.

Source: packages/effect/src/Stream.ts.

How to check

Use a dataset larger than the intended result budget. Check rows fetched and memory before consumption completes. This check is our proposal. The books do not prescribe it.

Continue with Steady state recycles resources9, Bulkheads isolate scarce capacity10.

Connect this to the existing rat-stack guidance23.

Use the durability skill for the full review. Return to the durability index34.

Sources

  1. Nygard, Michael T. Release It!: Design and Deploy Production-Ready Software. Pragmatic Bookshelf, 2007.. Pragmatic Bookshelf. §4.4 Unbounded Result Sets; Chapter 5 Stability Patterns: §5.1 Timeouts, §5.2 Circuit Breaker, §5.3 Bulkheads, §5.4 Steady State, §5.5 Fail Fast, §5.6 Handshaking, §5.7 Test Harness, §5.8 Decoupling Middleware. Accessed 2026-10-23.
  2. Effect contributors. Effect 4.0.0. Stream.ts. Effect-TS. Pinned source for our Effect mapping, not a claim from the book. Accessed 2026-10-23.

Last changed 2026-10-23 in 58dc623. Source on GitHub. Change log.

Linked from

  1. Agent guide. An Effect stack so pure (aspirational) Kit Langton will blush.

    Queries need result bounds — Limit result cardinality before the driver materializes an oversized response.

  2. Change log. What changed in the files served here, newest first.

    Queries need result bounds — new page: docs(lore): land the durability wiki pages and bibliography

  3. Durability starts with a recovery record. A reading order for storage, replay, worker ownership, overload, and recovery tests.

    Queries need result bounds: Limit result cardinality before the driver materializes an oversized response.¶

  4. Full agent guide. An Effect stack so pure (aspirational) Kit Langton will blush.
  5. Rat Stack lore | rat-stack. Short, source-grounded notes on the ideas and decisions behind rat-stack.

    Queries need result bounds — Limit result cardinality before the driver materializes an oversized response.

  6. Source change history (log.md). The generated change log as Markdown.

    Queries need result bounds — new page: docs(lore): land the durability wiki pages and bibliography

  7. Steady state recycles resources. Every accumulation needs a deliberate recycling policy.

    Continue with Queries need result bounds, Dead letters need a return path.¶