The same automatic vehicle location feed can produce a nightly MapReduce ridership summary or a continuous delay detector. What contrast should planners remember?
Select an answer to reveal the explanation.
Short Explanation
Same AVL hose, two jobs: one fills the nightly report bucket, the other watches delays as buses move. Batch MapReduce loves finished files; streaming loves the live trickle. They are not the same thing dressed differently.
Full Explanation
Batch MapReduce fits closed datasets such as nightly ridership summaries, while streaming applications process continuous feeds for timely outcomes like delay detection. Treating them as identical, assuming nightly MR is always faster for live delays, or requiring MR to delete the feed before streaming can run misstates the contrast.