How Trigger.dev is using ClickHouse to scale observability for long-running AI workflows
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.
Take a backup or restore a backup using commands - ClickHouse DocumentationClickhouse
Formats for input and output data - ClickHouse DocumentationClickhouse
DataStore accessors - ClickHouse DocumentationClickhouse
Embedded in ClickHouse - ClickHouse DocumentationClickhouse
Performance guide - ClickHouse DocumentationClickhouse
DataStore Query building - ClickHouse DocumentationClickhouse
Trigger automation - MintlifyMintlify
How we grew Mintlify by doing things that don't scaleMintlify
10 best AI observability tools for monitoring and evaluating agents in 2026Mintlify
Top 3 Use Cases for Speech-to-Text in Gaming - Deepgram Blog ⚡️Deepgram
No Code Transcription: Simplifying Workflows with Deepgram and Make.comDeepgram
Local Kubernetes Development Using Minikube and Redis EnterpriseRedis
Six Things to Consider When Using Redis on HerokuRedis
How a marketing agency increased client conversions 35% with Zapier CanvasZapier
How to implement AI training for employeesZapier
Customer.io Automatically Standardizes Form Submissions for ReportingZapier
How automation helped us get better customer reviewsZapier
Pancakes Are Delicious and Data Centers Are for Free StuffThenewstack
Transform and Future-Proof Your Architecture with MACHThenewstack
Selecting the Right Database for Your MicroservicesThenewstack
