It's just that Redis is mostly an in-memory database and if the process is terminated and restarted (for all sorts of reasons) the data can be restored from disk.
So what IceFireDB might be good for is data which would not fit easily into the memory of one node.
I often see projects like this posted on HN, and it's very unclear to me what the actual use case is. Does anyone even end up actually using these things? I guess the developers hope it takes off, and they gain notoriety as 'the guy who made X'?
It's just that Redis is mostly an in-memory database and if the process is terminated and restarted (for all sorts of reasons) the data can be restored from disk.
So what IceFireDB might be good for is data which would not fit easily into the memory of one node.
Again, it's really not clear to me.