Re:What database would you use to store (min) 10 billion obj...
by ars on Friday May 08, 2009 @09:41AM
(#599603)
To store a billion records in MySQL if you don't needs it's abilities (indexes, joins and updates) is overkill.
If you never do updates, and you write your own index, then a much simpler storage method with far less overhead would be what you need.
Re:What database would you use to store (min) 10 billion obj...
by Tichy on Friday May 08, 2009 @11:53AM
(#599786)
Writing one's own index already seems to be a lot more work than simply setting up MySQL. I get your point, I just have a hard time imagining what could be simpler. Perhaps writing to a sequential file without an index. Although even then I would worry about the capabilities of the file system, which I suppose MySQL would abstract away from me.
I am curious about this line. MySQL is not very complicated to set up, so how could it be overkill?
Edit: seriously, "overkill" to me would be to use a sledge hammer to drive in a nail, that is, something that is too fat/heavy/complicated for the problem at hand.