Live Video Ingestion Pipeline Deployment Framework

Role: Principal Streaming Infrastructure Engineer with deep expertise in live video packaging, real-time transcoding engines, and zero-downtime deployment pipelines.

Context

• Target Platform: {{streaming_platform_name}}
• Peak Target Concurrency: {{target_concurrency}}
• Transcoding & Packaging Engine: {{transcoding_engine}}
• Target Cloud Environment: {{cloud_provider}}
• Latency SLA Threshold: {{max_tolerable_latency}}
• Rollback Window Allowance: {{rollback_window_minutes}}

Task

Design an end-to-end continuous deployment and automated verification framework for the live video ingestion microservices supporting {{streaming_platform_name}}, ensuring seamless blue/green cluster transitions, synthetic pipeline verification, and automated rollback execution under strict latency budgets.

Method

1. Define pre-deployment pipeline gates that validate container images against baseline {{transcoding_engine}} runtime benchmarks.
2. Model the blue/green infrastructure provisioning workflow within {{cloud_provider}} to host parallel stream ingestion workers.
3. Implement synthetic video feed ingestion to evaluate real-time stream packet loss and packaging latency against {{max_tolerable_latency}}.
4. Configure dynamic traffic shifting policies to route a 5% live canary split while monitoring encoder drop-frame metrics.
5. Design automated health probe telemetry capturing chunk generation times, RTMP/SRT handshake latency, and buffer-health indicators for {{target_concurrency}} load profiles.
6. Specify automated rollback triggers tied to error-budget burn rates that complete full traffic reversion within {{rollback_window_minutes}}.
7. Detail post-deployment teardown routines for retired staging instances once downstream client stability is confirmed.

Constraints

• MUST require synthetic media validation before opening any public ingest ports.
• MUST NOT exceed {{max_tolerable_latency}} during canary traffic diversion.
• All deployment stages must produce machine-readable metrics for CDN origin shielding.
• Security validation must verify stream key authentication mechanisms during step 3.
• Framework stages must remain vendor-neutral while leveraging native {{cloud_provider}} networking constructs.

Output format

1. Executive Architecture Overview (max 150 words)
2. Pipeline Stage Matrix (Stage name, Trigger, Tooling, Gate Criteria, Max Execution Time)
3. Automated Verification & Synthetic Smoke Test Specification
4. Canary Traffic Shifting & Rollback Protocol (step-by-step table)
5. Observability & Telemetry KPI Checklist (at least 6 streaming-specific metrics)

Self-review

• Did I incorporate {{transcoding_engine}} and {{cloud_provider}} specifics into the pipeline stages?
• Are rollback triggers explicitly bounded by {{rollback_window_minutes}}?
• Is the latency check clearly validated against {{max_tolerable_latency}}?