Contract

• Input: stream source descriptions, processing requirements, latency/throughput targets.
• Output: topology design + event schema + processing rules.
• Side effects: may deploy stream resources when executed.
• Dependencies: streaming platform access (Kafka / Kinesis / Pub/Sub / Flink).
• Stop condition: design saved; rules documented.
• Risk: medium — stream errors propagate quickly; requires testing.
• Boundary: designs stream; executes only with explicit approval.

Streaming Pipeline Design

Design a streaming pipeline — event producers, stream processors, consumers — with schema, processing rules, and reliability.

Process