The code is easy to read, and the data model is as flexible as you want it to be, since it's schemaless.
Reasoning about what the code does is simple once you shift your paradigm to document from relational.
Do your research. "document-based" DBs already "ruled the world" right until relational databases were invented, which quickly obsoleted them.
The only advantage of disk-backed hash table is ease of scalability, this is why they're useful for hm.... top 0.005% of web sites, who handle thousands of updates per second.
How terse the code is? How easy the code is to read? How likely the code is to be correct? How flexible the data model is to new requirements? How simply you can reason about what the code does?