6 ms·
True there are, and I'd be lying if I said I had tried everything. But in general even key-value stores are designed to store sorted/structured data. Not reall
by UnoriginalGuy 13y ago
True there are, and I'd be lying if I said I had tried everything.
But in general even key-value stores are designed to store sorted/structured data. Not really massive BLOBs with a little meta data sprinkled in to explain it.
You just run into serious performance issues when you try and store/access >2 GB of "junk" data via some clever database management engine, which is really more accustomed to storing tiny little columns of explain-able data you can write clever queries to.
We've wound up in a situation now where we just use databases to store the meta-data and have left the actual data in files, which from a programming point of view makes things harder (since you're hooking into two methods of data access as opposed to one).
- icebraining 13y agoWell, PostgreSQL supports the Large Objects, which are designed to store big amounts of data (outside the normal tables) and reference them using special IDs. It may work for your use case.
- reefab 13y agoI've used CouchDB's attachment feature for that purpose: http://onabai.wordpress.com/2012/05/08/working-with-attachments/ http://onabai.wordpress.com/2012/05/08/working-with-attachme...