AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
backendhigh PriorityID: duckdb-embedded-analytics

DuckDB Embedded Analytics & Zero-Copy Parquet Query Standard

Ultra-fast embedded columnar analytics on Parquet and Arrow datasets. Eliminates heavy Pandas memory bloat by running zero-copy vectorized SQL queries directly on local or S3 Parquet files with streaming execution.

Prohibited Anti-Pattern: AI loads gigabytes of raw CSV/Parquet into Pandas memory via pd.read_csv() triggering OOM crashes.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: DuckDB Embedded Analytics & Zero-Copy Parquet Query Standard - Ultra-fast embedded columnar analytics on Parquet and Arrow datasets. Eliminates heavy Pandas memory bloat by running zero-copy vectorized SQL queries directly on local or S3 Parquet files with streaming execution.
globs: **/*analytics*.py, **/*duckdb*.py, **/*data_pipeline*.py
alwaysApply: false
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/duckdb-embedded-analytics"
---

# DuckDB Embedded Analytics & Zero-Copy Parquet Query Standard

> **Severity**: HIGH | **Category**: backend
> **Anti-Pattern Warning**: AI loads gigabytes of raw CSV/Parquet into Pandas memory via pd.read_csv() triggering OOM crashes.

## System Constraints
You are a high-performance data engineering specialist. When querying multi-gigabyte Parquet or CSV datasets in Python or Node.js, never load the entire dataset into memory with pandas.read_csv() or pandas.read_parquet(). Use DuckDB vectorized in-situ SQL queries with memory limits and zero-copy Arrow output.

## Strict Guidelines
- Query Parquet files directly via SQL path globbing ('data/*.parquet') without loading raw bytes into intermediate Pandas DataFrames.
- Set strict DuckDB memory limits (SET max_memory = '4GB') and threads to prevent cloud worker out-of-memory container evictions.
- Export large query results using streaming Arrow tables or write directly to output Parquet files with COPY TO.
- Leverage DuckDB window functions and approximate aggregations (approx_count_distinct) for fast exploratory metrics.

## Bad vs Good Implementations
### In-Situ Parquet SQL Query vs Memory-Exhausting pd.read_parquet

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Loading multi-gigabyte Parquet files into Pandas uncompresses columnar data, consuming 3x-5x RAM and crashing Docker containers.
```python
# ANTI-PATTERN: Loading 12GB Parquet into RAM via Pandas
import pandas as pd

df = pd.read_parquet("s3://acme-lake/events/2026/*.parquet")
filtered = df[df["status"] == "COMPLETED"]
summary = filtered.groupby("user_id")["amount"].sum().reset_index()
```

#### Production Standard (Correct)
> **Standard**: DuckDB executes queries directly against Parquet metadata and compressed columnar chunks using streaming vector SIMD instructions.
```python
# PRODUCTION STANDARD: DuckDB Vectorized In-Situ Execution (<100MB RAM)
import duckdb

conn = duckdb.connect()
conn.execute("SET max_memory = '2GB'")
conn.execute("SET threads = 4")

query = """
    SELECT 
        user_id,
        count(*) as total_events,
        sum(amount) as total_spent,
        approx_count_distinct(ip_address) as unique_ips
    FROM 's3://acme-lake/events/2026/*.parquet'
    WHERE status = 'COMPLETED'
      AND event_date >= CURRENT_DATE - INTERVAL 30 DAY
    GROUP BY user_id
    HAVING total_spent > 1000
    ORDER BY total_spent DESC
    LIMIT 100;
"""

arrow_table = conn.execute(query).arrow()
```

### Direct Streaming Export with COPY TO

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Python string formatting in loops is orders of magnitude slower than native columnar compression.
```python
# ANTI-PATTERN: Inefficient Python loop writing CSV row-by-row
with open("export.csv", "w") as f:
    for row in rows: f.write(f"{row[0]},{row[1]}\n")
```

#### Production Standard (Correct)
> **Standard**: Writes multi-million row analytics directly to disk with optimal columnar ZSTD compression in seconds.
```python
# PRODUCTION STANDARD: Native vectorized Snappy Parquet export
conn.execute("""
    COPY (
        SELECT * FROM 'raw_logs/*.parquet' WHERE error_code IS NOT NULL
    ) TO 'cleaned_errors.parquet' (FORMAT PARQUET, COMPRESSION ZSTD);
""")
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

DuckDB In-Memory Query MCP
Execute vectorized SQL directly on remote Parquet files and local SQLite databases.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Parquet & DuckDB Pipeline Optimizer
Optimize Parquet partitioning and write high-speed DuckDB aggregations.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: DuckDB Embedded Analytics & Zero-Copy Parquet Query Standard

DuckDB Embedded Analytics & Zero-Copy Parquet Query Standard defines an industrial-grade behavioral standard for backend engineering. Ultra-fast embedded columnar analytics on Parquet and Arrow datasets. Eliminates heavy Pandas memory bloat by running zero-copy vectorized SQL queries directly on local or S3 Parquet files with streaming execution. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: AI loads gigabytes of raw CSV/Parquet into Pandas memory via pd.read_csv() triggering OOM crashes. Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftAI loads gigabytes of raw CSV/Parquet into Pandas memory via pd.read_csv() triggering OOM crashes.High
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Query Parquet files directly via SQL path globbing ('data/*.parquet') without loading raw bytes into intermediate Pandas DataFrames.

Query Parquet files directly via SQL path globbing ('data/*.parquet') without loading raw bytes into intermediate Pandas DataFrames.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Set strict DuckDB memory limits (SET max_memory = '4GB') and threads to prevent cloud worker out-of-memory container evictions.

Set strict DuckDB memory limits (SET max_memory = '4GB') and threads to prevent cloud worker out-of-memory container evictions.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Export large query results using streaming Arrow tables or write directly to output Parquet files with COPY TO.

Export large query results using streaming Arrow tables or write directly to output Parquet files with COPY TO.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Leverage DuckDB window functions and approximate aggregations (approx_count_distinct) for fast exploratory metrics.

Leverage DuckDB window functions and approximate aggregations (approx_count_distinct) for fast exploratory metrics.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is DuckDB Embedded Analytics & Zero-Copy Parquet Query Standard critical for AI coding assistants?

Ultra-fast embedded columnar analytics on Parquet and Arrow datasets. Eliminates heavy Pandas memory bloat by running zero-copy vectorized SQL queries directly on local or S3 Parquet files with streaming execution. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (AI loads gigabytes of raw CSV/Parquet into Pandas memory via pd.read_csv() triggering OOM crashes.) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related BACKEND Rules

View all rules →
backend
42

Fastify 5 Schema Compilers & Encapsulation Production Standard

Fastify relies on lexical encapsulation contexts to sandbox decorators, hooks, and compiled validation/serialization schemas without memory leaks or cross-tenant bleed. In Fastify 5, misuse of global compilers or failing to encapsulate plugin boundaries causes compiled `fast-json-stringify` serializers and Ajv validators to either crash on duplicate IDs, leak private data across sibling scopes, or bypass JIT compilation optimizations. Production services must enforce strict encapsulation hierarchies and type-safe schema compilation across every routing subtree.

backend
68

Bun Embedded SQLite WAL Mode & Transaction Synchronization Standard

Production database standard for bun:sqlite. Mandates enabling Write-Ahead Logging (PRAGMA journal_mode = WAL), busy timeouts, and using db.transaction() for atomic operations without lock starvation.

backend
68

Drizzle ORM Batch API & Interactive Transaction Isolation Standard

Production database standard for Drizzle ORM (PostgreSQL & MySQL). Mandates using db.batch() over HTTP drivers to prevent round-trip waterfalls, explicit db.transaction() with serializable/read-committed isolation, and strictly avoids unawaited query promises.

1 Rule in Stack

DuckDB