News for hackers. Stuff that matters.
Re:Redis on Acid: 0.5M ops/sec, 1ms latency and ACID compliance by mayank on Sunday July 23, 2017 @04:51PM (#14834314)
You definitely could, with some pretty big caveats:

* you can tolerate some data loss in case of system crashes/power failures/etc, because redis only flushes data to disk periodically [1]

* your dataset can fit in RAM, since redis is an in-memory datastore

[1] https://redis.io/topics/persistence

Re:Redis on Acid: 0.5M ops/sec, 1ms latency and ACID compliance by kristoff_it on Sunday July 23, 2017 @05:12PM (#14834422)
Using AOF you have better durability, you can read about it in the link you provided.
Re:Redis on Acid: 0.5M ops/sec, 1ms latency and ACID compliance by mayank on Sunday July 23, 2017 @07:15PM (#14834878)
As far as I know, AOF is still not the default setting. It's important to point this out, or otherwise Redis will suffer the same fate as early MongoDB, which had a similar default persistence model which many users didn't fully understand.