Ledisdb is a high-performance NoSQL database, similar to Redis, written in Go. It supports many data structures including kv, list, hash, zset, set.
LedisDB now supports multiple different databases as backends.
ledis-upgrade-ttl before using LedisDB version 0.4, I fixed a very serious bug for key expiration and TTL.Create a workspace and checkout ledisdb source
mkdir $WORKSPACE
cd $WORKSPACE
git clone git@github.com:siddontang/ledisdb.git src/github.com/siddontang/ledisdb
cd src/github.com/siddontang/ledisdb
#set build and run environment
source dev.sh
make
make test
Install leveldb and snappy.
LedisDB supplies a simple script to install leveldb and snappy:
sudo sh tools/build_leveldb.sh
It will install leveldb at /usr/local/leveldb and snappy at /usr/local/snappy by default.
LedisDB uses the modified LevelDB for better performance. Details.
You can easily use other LevelDB versions (like Hyper LevelDB or Basho LevelDB) instead, as long as the header files are in include/leveldb, not include/hyperleveldb or any other location.
Set LEVELDB_DIR and SNAPPY_DIR to the actual install path in dev.sh.
make clean && make Install rocksdb(5.1+)(make shared_lib) and snappy first.
LedisDB has not yet supplied a simple script to install.
Set ROCKSDB_DIR and SNAPPY_DIR to the actual install path in dev.sh.
make clean && make If the RocksDB API changes, LedisDB may not build successfully. LedisDB currently supports RocksDB version 5.1 or later.
LedisDB now supports goleveldb, leveldb, rocksdb, and RAM. It will use goleveldb by default.
Choosing a store database to use is very simple.
Set in server config file
db_name = "leveldb"
Set in command flag
ledis-server -config=/etc/ledis.conf -db_name=leveldb
Flag command set will overwrite config setting.
Lua is supported using gopher-lua, a Lua VM, completely written in Go.
LedisDB uses toml as the configuration format. The basic configuration ./etc/ledis.conf in LedisDB source may help you.
If you don't use a configuration, LedisDB will use the default for you.
//set run environment if not
source dev.sh
./bin/ledis-server -config=/etc/ledis.conf
//another shell
./bin/ledis-cli -p 6380
ledis 127.0.0.1:6380> set a 1
OK
ledis 127.0.0.1:6380> get a
"1"
//use curl
curl http://127.0.0.1:11181/SET/hello/world
→ {"SET":[true,"OK"]}
curl http://127.0.0.1:11181/0/GET/hello?type=json
→ {"GET":"world"}
import (
lediscfg "github.com/siddontang/ledisdb/config"
"github.com/siddontang/ledisdb/ledis"
)
# Use Ledis's default config
cfg := lediscfg.NewConfigDefault()
l, _ := ledis.Open(cfg)
db, _ := l.Select(0)
db.Set(key, value)
db.Get(key)
Set slaveof in config or dynamiclly
ledis-cli -p 6381
ledis 127.0.0.1:6381> slaveof 127.0.0.1 6380
OK
LedisDB uses a proxy named xcodis to support cluster.
See benchmark for more.
See Issues todo
See Clients to find or contribute LedisDB client.
If you like the project and want to buy me a cola, you can through:
| PayPal | 微信 |
|---|---|
![]() |
[![]() |
$ claude mcp add ledisdb \
-- python -m otcore.mcp_server <graph>