Entity-Attribute-Value Refresher
Have to support a survey feature thus a system capable of managing questions-responses. The data model that readily comes to mind (or came to a coworker's mind) was using a modeling pattern that I'd forgotten the name of from 5 years ago . . the dreaded Entity-Attribute-Value design (dreaded in relational databases at least). It's just so unmaintainable and unscalable.
But in the NoSQL world, it's not only acceptable but somewhat fitting. Will have to ponder EAV in the context of this new paradigm since it's unclear how to maintain data integrity and clean models/code . .
But in the NoSQL world, it's not only acceptable but somewhat fitting. Will have to ponder EAV in the context of this new paradigm since it's unclear how to maintain data integrity and clean models/code . .