Everybody knows RAM became cheaper cheaper, while mechanical disk can't be made faster, and SSD have reliability limits.
It seems entirely logical to expect databases to work on RAM first and then commit on disk for a large performance improvement.
Everybody knows RAM became cheaper cheaper, while mechanical disk can't be made faster, and SSD have reliability limits.
It seems entirely logical to expect databases to work on RAM first and then commit on disk for a large performance improvement.
He was not really listening to what I was saying or my arguments, because a system like redis seems like a more than acceptable compromise.
It still seems a few people are reluctant to an in-memory database.
I think people who are deploying redis are willing to tolerate lower durability guarantees for the extra performance. A lot of the time redis is some kind of cache and there is a way of reconstructing the real data from more durable storage in the case of failure. Or people are willing to lose a second of data or whatever fsync interval people are using.
of course, _now_ they are like "FTW" :)
The best ideas often seem obvious in retrospect.