Finance accepts T+1 batch closes, while traffic operations needs minute-level metric refresh. How should architecture reflect both needs?
Select an answer to reveal the explanation.
Short Explanation
Payroll can wait overnight; a jammed arterial cannot. Architecture should keep a batch path for finance and a faster path for traffic instead of bullying both into one SLA. Different clocks, different lanes.
Full Explanation
Big Data architectures commonly separate batch processing from speed or serving layers that refresh near real time. Finance T+1 workloads and traffic operations minutes-level metrics exemplify why one latency class cannot serve every stakeholder. Forcing a single refresh, blocking storage until consensus, or over-engineering finance onto sub-second streams wastes cost and misses requirements. Dual paths with clear SLAs are the architectural answer.