aboutsummaryrefslogtreecommitdiffstats
path: root/comms/qrq
diff options
context:
space:
mode:
authornork <nork@FreeBSD.org>2010-05-30 12:41:50 +0800
committernork <nork@FreeBSD.org>2010-05-30 12:41:50 +0800
commitdb445f7e1129c7429fcb2c7142ad952d5a961cb5 (patch)
tree88b3822ddc2f8ce7edab3f2b69c9267780313002 /comms/qrq
parent8c57773704267d2d585cd6b2187db0786945b9e2 (diff)
downloadfreebsd-ports-gnome-db445f7e1129c7429fcb2c7142ad952d5a961cb5.tar.gz
freebsd-ports-gnome-db445f7e1129c7429fcb2c7142ad952d5a961cb5.tar.zst
freebsd-ports-gnome-db445f7e1129c7429fcb2c7142ad952d5a961cb5.zip
Add flare 1.0.9, is distributed, and persistent key-value storage
compatible / memcached, and has more features(as follows): * persistent storage (you can use flare as persistent memcached) * pluggable storage (currently only Tokyo Cabinet is available, though:) * data replication (synchronous or asynchronous) * data partitioning (automatically partitioned according to # of master servers (clients do not have to care about it)) * dynamic reconstruction, and partitioning (you can dynamically (I mean, without any service interruption) add slave servers and partition master servers) * node monitoring and failover (if any server is down, the server is automatically isolated from active servers and another slave server is promoted to master server) * request proxy (you can always get same result regardless of servers you connect to. so you can think flare servers as one big key-value storage) * over 256 bytes keys, and over 1M bytes values are available WWW: http://labs.gree.jp/Top/OpenSource/Flare-en.html
Diffstat (limited to 'comms/qrq')
0 files changed, 0 insertions, 0 deletions