# Batch-vs-Stream

Record: `arch:batch-vs-stream`
Kind: approach
Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md)
Severity: contextual
Scope: data processing, latency, architecture
Canonical: https://banes-lab.com/ontology#arch-batch-vs-stream

## Repair

- Refactored by: Choose Batch or Stream by Latency Need
- Detected by: batch cadence mismatched to freshness requirements
- Violated by: low-latency needs served by periodic batch jobs
- Measured by: data-freshness lag vs requirement
- Enforced by: data architecture review

## requires

- [Latency Requirement Clarity](https://banes-lab.com/records/lex/latency-requirement-clarity.md)

## reinforces

- [Fitness for Purpose](https://banes-lab.com/records/lex/fitness-for-purpose.md)

## enables

- [Latency-Appropriate Processing Model](https://banes-lab.com/records/lex/latency-appropriate-processing-model.md)

## conflicts-with

- [One-Size-Fits-All Processing](https://banes-lab.com/records/lex/one-size-fits-all-processing.md)

## tensions-with

- [Operational Duplication](https://banes-lab.com/records/lex/operational-duplication.md)

## tensions

- [Batch-vs-Stream Operational Duplication](https://banes-lab.com/records/tension/batch-vs-stream-operational-duplication.md)