3 ms·
Nice. But I have a difficult time seeing how storing "malleable" data like that, opaque to the storage engine, is going to be performant for querying. Must be
by heresy 17y ago
Nice. But I have a difficult time seeing how storing "malleable" data like that, opaque to the storage engine, is going to be performant for querying.
Must be nice to have requirements that never change once you've decided on a data representation...
- paulgb 17y agoThe database is still aware of the fields, so MongoDB can build indices on certain fields if you wish. Admittedly I haven't deployed Mongo in an environment that really tested its performance, but we've been serving about 20k pageviews per day with no issues. Granted, this was a fairly basic application. As for changing requirements, mongo handled those well too. It's certainly not a silver bullet, but when I just need a basic object store the query performance trade-off is worth it.