4 ms·
100%. I've dealt with many small-to-medium sized projects where the usual approach would have been some form of EAV mess. Just using a BSON column for such att
by 1propionyl 5y ago
100%. I've dealt with many small-to-medium sized projects where the usual approach would have been some form of EAV mess.
Just using a BSON column for such attributes hits the Pareto 80/20 sweet spot, _and_ I can query against them much more easily than in an EAV schema (far fewer joins).
They're great for when the schema is mostly normalized, but there's just a little bit of denormalized stuff that doesn't warrant completely architecting the schema around it.