How Trigger.dev is using ClickHouse to scale observability for long-running AI workflows

T1Covered by 1 source · first reported by Databricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale at 09 Jul, 13:07 UTC

Trigger.dev migrated from Postgres to ClickHouse to scale observability for its serverless AI workflow platform, delivering ~200 ms P95 query performance and a dramatically smaller telemetry storage footprint.

cloud

Sources

• T1How Trigger.dev is using ClickHouse to scale observability for long-running AI workflowsDatabricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale09 Jul, 13:07