Developers assume they can filter a civic NoSQL store on any field as freely as a normalized SQL database. What caution should the architect emphasize?
Select an answer to reveal the explanation.
Short Explanation
In NoSQL, "query anything anytime" is a myth that burns clusters. You design around the lookups you actually need. Think access patterns first, not SQL daydreams.
Full Explanation
Many NoSQL designs optimize for known primary-key or planned access paths rather than ad hoc SQL-style filtering on every attribute. Secondary indexes, when available, still carry storage and write overhead and may not match relational flexibility. Architects must model queries up front instead of assuming free arbitrary field scans. This caution prevents production surprises when civic apps filter on unplanned attributes.