The same civic program keeps history in HDFS, user profiles in NoSQL, and finance marts in a warehouse. What architecture idea does this illustrate?
Select an answer to reveal the explanation.
Short Explanation
History, profiles, and finance marts are different jobs — so they get different shelves. That mix is polyglot persistence, not a failure to pick one holy format.
Full Explanation
Polyglot persistence selects storage technologies by access pattern: distributed files for deep history, NoSQL for flexible profiles, warehouses for governed finance marts. One civic program can host all three under a coherent architecture. Forcing a single format, making NoSQL replace every store, or banning serving when stores multiply misunderstands the pattern. Integration and governance glue the stores together without erasing their strengths.