Dragonflydb – A modern replacement for Redis and Memcached

Re:Dragonflydb – A modern replacement for Redis and Memcached by nextaccountic on Monday May 30, 2022 @06:37PM (#31564383)

Have you thought about also offering dragonflydb as a library, like sqlite? This would avoid context switching when running everything on the same machine.

[ Parent | on HN ]

Re:Dragonflydb – A modern replacement for Redis and Memcached by romange on Monday May 30, 2022 @06:45PM (#31564435)

it could be done technically. not sure how widespread that usecase would be.

dragonfly is a linking of a library and a main file dfly_main.cc so without this file you will have the lib.

Redis is "Remote Dictionary Server". You gonna loose the remote part :)

[ Parent | on HN ]

Re:Dragonflydb – A modern replacement for Redis and Memcached by secondcoming on Tuesday May 31, 2022 @05:44AM (#31567624)

Being able to use redis as an in-process L1 cache is something I’ve wanted to do. I don’t want the overhead of domain sockets.

[ Parent | on HN ]

Re:Dragonflydb – A modern replacement for Redis and Memcached by manigandham on Tuesday May 31, 2022 @11:58AM (#31571115)

This is what in-memory data grids can do, look at Apache Ignite for example: https://ignite.apache.org/

[ Parent | on HN ]

Re:Dragonflydb – A modern replacement for Redis and Memcached by obert on Monday May 30, 2022 @06:49PM (#31564465)

for development and demos it would help a lot, son one just runs the project at hand, instead of managing multiple procs

[ Parent | on HN ]