One digital-city program stores citizen profiles as documents, fraud links in a graph, and hot session data in a key-value cache. What persistence approach does this illustrate?
Select an answer to reveal the explanation.
Short Explanation
Different jobs, different toolboxes—that is polyglot persistence. Profiles like documents, relationships like graphs, sessions like key-value. Mixing store types on purpose beats one-size-fits-none.
Full Explanation
Polyglot persistence deliberately combines multiple data stores so each workload uses a fitting model. Document profiles, graph relationships, and key-value session caches solve distinct civic access patterns. A single universal store often forces awkward compromises across those patterns. Recognizing polyglot design is part of professional NoSQL architecture judgment.