A city lake holds the same mobility and permitting facts, but council packets need polished PDF summaries while dispatch consoles need sub-second lookups. Which architectural idea best explains serving both consumers from one platform?
Select an answer to reveal the explanation.
Short Explanation
Think of the lake as a kitchen pantry: chefs and catering trays both pull ingredients, but plating differs. Same facts can power slow, pretty council packets and snappy dispatcher lookups through different serving paths.
Full Explanation
Big Data architectures commonly separate storage and processing from serving so one curated platform can support heterogeneous consumers. Executive PDF generation tolerates batch latency and rich formatting, while operational consoles demand low-latency keyed access. Designing multiple serving characteristics—reports, APIs, caches—from shared analytical layers avoids duplicating raw lakes while still meeting each SLA.