3 ms·
I don't think single- vs. multi-threaded is not relevant in this context. Any database, regardless its architectural design choices, will probably have a hard t
by itamarhaber 12y ago
I don't think single- vs. multi-threaded is not relevant in this context. Any database, regardless its architectural design choices, will probably have a hard time if you try process this much information.
As for when to use SQL and when not to, well, that really depends on the problems that you're trying to solve, your preferences and a whole myriad of other considerations. I fully agree there are tasks that can be handled well by more than one solution, while others are best tackled with specialized tools.
- andrewvc 12y agoIt is very relevant because with a multithreaded DB you can survey your pkeys while only minimally interfering with the day to day operations of the database. I understand that it's a judgement call, I'm merely asserting that most people make the wrong judgement because they want to play with new tech.
- thezilch 12y agoYou can do the same with Redis. Regardless of the fact you can simply hang a Redis slave and work on that; Redis has a *SCAN commands that can incrementally iterate over your entire keyspace or keys of any Redis collection (hashes, sets, etc).