Schedule icon
Query icon
Parallel icon
Request icon
Commands icon
If icon
Log icon

In-Memory DuckDB Customer Sentiment and Health Pipeline

Orchestrate in-memory DuckDB batch extraction, parallel HTTP checks, and conditional alert logging with Kestra.

Categories
Data

Orchestrates in-memory SQL analytics with DuckDB, parallel HTTP status verification, and conditional telemetry logging without external database dependencies.

How it works

  1. A Schedule trigger runs the pipeline automatically on an hourly cron schedule.
  2. DuckDB extracts unprocessed customer reviews directly in memory via SQL.
  3. A Parallel flowable task concurrently queries an API status endpoint and processes log messages.
  4. An If task evaluates HTTP response codes and routes success telemetry accordingly.

What you get

  • Fast in-memory analytics without provisioning external database servers.
  • Concurrent verification of dependent APIs to eliminate pipeline bottlenecks.
  • Automated logging safeguards alerting on execution status.

Who it's for

  • Analytics Engineers looking for zero-setup relational extraction patterns.
  • Platform Teams designing concurrent health diagnostics.

Why orchestrate this with Kestra

  • Declarative YAML workflows with built-in retries and state management.
  • Built-in UI topology and execution tracking for every branch.

Prerequisites

  • Standard Kestra instance with the DuckDB plugin enabled.

Secrets

  • No secrets required.

Quick start

  1. Import this blueprint into your Kestra instance.
  2. Click Execute to verify all tasks complete in green.
  3. Enable the hourly schedule trigger.

How to extend

  • Replace the mock records with real Parquet or S3 queries in DuckDB.
  • Connect a Slack or PagerDuty task to the If evaluation branch.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.