3 ms·
> well configured and maintained Well there's the rub -- table stakes for traditional database software (the "boring technology") is not losing your data. Redi
by hardwaresofton 5y ago
> well configured and maintained
Well there's the rub -- table stakes for traditional database software (the "boring technology") is not losing your data. Redis has AOF which can be tuned and this SO post[0] is a good intro to how they work and the different settings involved. Pieces of software like Postgres have settings that get you to dont-lose-my-data on day 1.
Also people generally rant and rave about the performance of Redis when AOF-write-on-every-write (aka WAL) is not turned on. It also kind of annoys me how AOF is caleld AOF when there is a very good well known term for this already -- WAL.
[0]: https://stackoverflow.com/questions/40939756/difference-between-redis-aof-and-tarantool-wal-log https://stackoverflow.com/questions/40939756/difference-betw...
- tomnipotent 5y agoThe redis AOF is a post-write log, so it's not a WAL.
- hardwaresofton 5y agoAh thanks for the correction, it's not a Write Ahead Log at all, and they made the right choice in not overloading it to mean Write After or anything silly like that. That irk was over nothing. Given that being true then there is no way to run Redis without the spectre of data loss, period -- just a question of how much you are OK with possibly losing (which to be fair is probably fairly small with most healthy systems).