A high performance NoSQL Database Server powered by Go
Go to file
re 2ff8098b91 upd 2023-02-15 10:41:45 +03:00
.github Add a stale check (#386) 2020-05-10 18:33:04 +08:00
cmd upd 2023-02-15 10:41:45 +03:00
config Add vet check and fix some vet errors (#374) 2020-04-24 13:07:38 +08:00
doc upd 2023-02-15 10:41:45 +03:00
etc use vendor and do clean up. (#241) 2016-05-01 23:33:02 +08:00
ledis upd 2023-02-15 10:41:45 +03:00
rpl upd 2023-02-15 10:41:45 +03:00
server upd 2023-02-15 10:41:45 +03:00
store upd 2023-02-15 10:41:45 +03:00
tools Use latest (1.20+) LevelDB (#326) 2017-11-27 08:51:18 +08:00
vendor Use go mod instead of dep to manage the project 2020-04-23 17:00:20 +08:00
.gitignore Fix badge (#381) 2020-04-26 20:11:32 +08:00
.travis.yml Add coverage from codecov (#376) 2020-04-24 13:23:58 +08:00
CONTRIBUTING.md upd 2023-02-15 10:41:45 +03:00
Dockerfile upd 2023-02-15 10:41:45 +03:00
LICENSE Initial commit 2014-04-29 17:43:09 -07:00
Makefile Fix some lint error (#385) 2020-05-10 18:17:39 +08:00
README.md upd 2023-02-15 10:41:45 +03:00
dev.sh upd 2023-02-15 10:41:45 +03:00
entrypoint.sh Add Dockerfile (#327) 2017-11-28 08:50:33 +08:00
go.mod upd 2023-02-15 10:41:45 +03:00
go.sum Use go mod instead of dep to manage the project 2020-04-23 17:00:20 +08:00

README.md

LedisDB

Build Status codecov goreportcard

Ledisdb is a high-performance NoSQL database library and server written in Go. It's similar to Redis but store data in disk. It supports many data structures including kv, list, hash, zset, set.

LedisDB now supports multiple different databases as backends.

Features

  • Rich data structure: KV, List, Hash, ZSet, Set.
  • Data storage is not limited by RAM.
  • Various backends supported: LevelDB, goleveldb, RocksDB, RAM.
  • Supports Lua scripting.
  • Supports expiration and TTL.
  • Can be managed via redis-cli.
  • Easy to embed in your own Go application.
  • HTTP API support, JSON/BSON/msgpack output.
  • Replication to guarantee data safety.
  • Supplies tools to load, dump, and repair database.
  • Supports cluster, use xcodis.
  • Authentication (though, not via http).
  • Repair integrated: You can use ledis repair to repair broken databases and ledis repair-ttl to repair a very serious bug for key expiration and TTL if you upgraded from v0.4.

Build from source

Create a workspace and checkout ledisdb source

git clone git@github.com:ledisdb/ledisdb.git
cd ledisdb

#set build and run environment 
source dev.sh

make
make test

Then you will find all the binary build on ./bin directory.

LevelDB support

  • 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

RocksDB support

  • 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.

Choose store database

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 -config=/etc/ledis.conf -db_name=leveldb

Flag command set will overwrite config setting.

Lua support

Lua is supported using gopher-lua, a Lua VM, completely written in Go.

Configuration

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.

Server Example

//set run environment if not
source dev.sh

./bin/ledis -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"}

Package Example

import (
    lediscfg "git.internal/re/ledisdb/config"
    "git.internal/re/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)

Replication Example

Set slaveof in config or dynamiclly

ledis cli -p 6381 

ledis 127.0.0.1:6381> slaveof 127.0.0.1 6380
OK

Cluster support

LedisDB uses a proxy named xcodis to support cluster.

CONTRIBUTING

See [CONTRIBUTING.md] .

Benchmark

See benchmark for more.

Todo

See Issues todo

Client

See Clients to find or contribute LedisDB client.

Caveat

  • Changing the backend database at runtime is very dangerous. Data validation is not guaranteed if this is done.

Requirement

  • Go version >= 1.11

Donate

If you like the project and want to buy me a cola, you can through:

PayPal 微信
[

Feedback