3 ms·
if you need a ORM for key/value storage, you're doing it (very) wrong
by mariusmg 16y ago
if you need a ORM for key/value storage, you're doing it (very) wrong
- rapind 16y agoExactly. I'm not sure why this is necessary. If you want to store rich objects, just serialize them and create your indexes as necessary. Anyways, I'll definitely check it out. Maybe I'm missing something.
- wfarr 16y agoThe scale of the application affects how much you can really do just by adding indexes to tables and throwing more hardware at it. At a certain point, servers are only so fast and disks only so large and fast.
- cheald 16y agoIf it's simple "stuff it in, pull it out" stuff, sure. Having things like validations and callbacks and association sugar and the like are really nice, though, in cases beyond the very simple. I think the point is to let you focus more on writing business logic, and less on mucking about with your underlying datastore. If it works as promised, then it could very certainly result in a productivity gain.