Re:How FoundationDB works and why it works
by c0balt on Monday September 18, 2023 @02:08AM
(#37552782)
Redis has a few features outside of k/v, like a good pub-sub implementation, that make it very useful in addition to a good DX and mature libraries.
Memcache on the other habd is just solid and mature. It also has some inertia as being a solid k/v cache. For example: NextCloud supports afaik both Redis and Memcache as caching engines but doesn't have FDB support.
Re:How FoundationDB works and why it works
by rapsey on Monday September 18, 2023 @02:15AM
(#37552831)
Because memcache and redis are in-memory. Writing to fdb will be complete once it is fsync'ed to disk.
Memcache is a cache. Fdb is a an ordered kv store.
Re:How FoundationDB works and why it works
by abhishekjha on Monday September 18, 2023 @02:26AM
(#37552905)
You can configure redis to flush to disk on write operations though you lose on performance.
Re:How FoundationDB works and why it works
by leetrout on Monday September 18, 2023 @02:53AM
(#37553090)
That is not comparable to writes completing after they are flushed to disk.
Re:How FoundationDB works and why it works
by NavinF on Monday September 18, 2023 @03:18AM
(#37553268)
>appendfsync always: fsync every time new commands are appended to the AOF. Very very slow, very safe. Note that the commands are appended to the AOF after a batch of commands from multiple clients or a pipeline are executed, so it means a single write and a single fsync (before sending the replies).
https://redis.io/docs/management/persistence/
It's very slow, but if you really want to wait for fsync before replying, it can do that.
Re:How FoundationDB works and why it works
by leetrout on Monday September 18, 2023 @03:39AM
(#37553394)
I was unaware they could make that guarantee.
Thanks for the correction.
Re:How FoundationDB works and why it works
by unmole on Monday September 18, 2023 @02:30AM
(#37552928)
Redis can be configured to persist and fsync every operation.
Re:How FoundationDB works and why it works
by rapsey on Monday September 18, 2023 @03:33AM
(#37553358)
Redis is not meant as a primary database and should not be used as such. FoundationDB is meant as a reliable source of truth.
Re:How FoundationDB works and why it works
by Already__Taken on Monday September 18, 2023 @08:33AM
(#37555283)
Redis began as a caching database, but it has since evolved into a primary database. Many applications built today use Redis as a primary database.
https://redis.com/blog/redis-cache-vs-redis-primary-database...
Very much seems like an acceptable use now
Re:How FoundationDB works and why it works
by vore on Monday September 18, 2023 @07:36PM
(#37563703)
Redis can't have a working set larger than memory. It has no mechanism to page data to disk. If your data set grows too large, you're hosed unless you add more hardware.
Re:How FoundationDB works and why it works
by dboreham on Monday September 18, 2023 @03:07AM
(#37553196)
Things like Redis and Memcache are not serious data stores. Don't put any data in them that you really need back out later.
Demystified a lot about FDB for me.
> ”Summary: FDB is probably the best k/v store for regional deployment out there.”
Why should someone use Memcache or Redis then?
Is it for the data types in Redis?