The architecture board maps ingestion, processing, storage, and serving layers before choosing Hadoop, MapReduce, NoSQL, Spark, or Kafka components. Why is that sequencing sound?
Select an answer to reveal the explanation.
Short Explanation
Draw the rooms before you buy the furniture. Layers and patterns tell you what Hadoop, Spark, or Kafka are for—not the other way around.
Full Explanation
Reference architecture clarifies responsibilities—ingestion, distributed storage, batch or stream processing, serving—before binding specific technologies. That framing lets teams place Hadoop/HDFS, MapReduce, NoSQL, Spark, or Kafka where each fits, instead of forcing every problem into a favorite product. Tool selection without an architectural frame often creates gaps in buffering, governance, or serving SLAs.