One city Kafka topic must refresh a low-latency NoSQL hot store and also land long-term copies in HDFS. Which architecture idea applies?
Select an answer to reveal the explanation.
Short Explanation
One announcement, two listeners—hot NoSQL for now, HDFS for the archive. Fan-out from a single topic beats making producers shout twice. Same event, different homes.
Full Explanation
Kafka fan-out lets independent consumer groups read one topic for different sinks—such as a NoSQL serving layer and an HDFS or lake archive loader. That avoids dual producers and decouples latency-sensitive stores from batch landers. Polling HDFS from NoSQL, forcing producers to emit twin streams, or keeping data only in broker memory loses the shared-bus benefit. Fan-out is a standard civic ingestion architecture pattern.