StructuredFor DevelopersSystem Design & Architecture

Data Pipeline Architecture.

When building a new data pipeline or diagnosing why an existing one is unreliable or too slow.

ChatGPT Β· Claude Β· GeminiΒ·IntermediateΒ·~900 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
data-pipeline-architecture-4.md Β· 900 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: System Design & Architecture
- Use case: Data Pipeline Architecture
- Source task:
  - Design a data pipeline for {{describe_the_use_case_analytics_ml_training_reporting_etl}}. Data sources: {{list_sources}}. Data volume: {{volume_frequency}}. Target: {{data_warehouse_data_lake_ml_feature_store_reporting_db}}. Recommend:
  - 1. pipeline architecture (Lambda / Kappa / Streaming-first)
  - 2. technology stack for ingestion, processing, and storage
  - 3. data quality checks at each stage
  - 4. failure handling and retry strategy
  - 5. monitoring and alerting approach for pipeline health

# Goal
Architecture recommendation with stack, stage-by-stage data quality checks, failure handling, and pipeline monitoring design.

# Constraints
- Produce a complete, usable first draft in one response.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
Architecture recommendation with stack, stage-by-stage data quality checks, failure handling, and pipeline monitoring design.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Roledata engineer and architect
{{use_case}}Your specific valuedata pipeline architecture
{{describe_the_use_case_analytics_ml_training_reporting_etl}}Describe the use case analytics ml training reporting etlML training
{{list_sources}}List sourcesPostgreSQL, S3 logs, Stripe API
{{volume_frequency}}Volume frequencyVOLUME
{{data_warehouse_data_lake_ml_feature_store_reporting_db}}Data warehouse data lake ml feature store reporting dbDATA WAREHOUSE

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When building a new data pipeline or diagnosing why an existing one is unreliable or too slow.

PRO TIP

Design for late-arriving data from day one β€” real-world data pipelines always receive out-of-order events, and retrofit solutions are expensive.

Related prompts

Structured

Blog Post Drafting Engine

Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal

Structured

Email Newsletter Writer

Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.

Structured

YouTube Video Script Writer

Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.

Structured

LinkedIn Article Builder

Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’