Permit applications arrive as nested JSON-like records with sections that differ by permit type. Which NoSQL type is the best fit for storing these semi-structured civic records?

Permit applications arrive as nested, type-dependent JSON-like records—sections appear or vanish by permit class—so a document store that persists nested fields per application is the best NoSQL fit. Each application can carry its own shape while remaining one logical civic case file. A pure key-value blob store that never indexes nested fields can stash opaque bytes but makes section-level query and validation awkward for clerks. A rigid relational schema forcing identical columns for every permit type recreates sparse nulls and migration pain as forms evolve. A graph-only engine that cannot persist the application payload itself may link entities but fails as the system of record for the nested application content. Exam caveat: document stores still need indexing and validation strategy; flexibility is not an excuse for unqueryable blobs. Operational check: insert two permit types with different nested sections into the same collection, retrieve each by application id, and run one indexed query on a shared field such as parcel id without altering a global table DDL. In production terms for document stores for nested permits, assign an owning team, wire a dashboard that shows the pattern is healthy under peak civic load, and require a staging drill that rehearses failure and recovery before resident impact. Revisit the choice when traffic shape, retention, or integrity needs change, and keep a named rollback owner on the change record. Re-test both the happy path and the failure path for document stores for nested permits after material dependency upgrades so regressions are caught before the next public release.