topling/toplingdb: ToplingDB is a cloud native LSM Key-Value Store with searchable compression algo and distributed compaction · GitHub

ToplingDB is developed and maintained by Topling Inc. See ToplingDB Branch Name Convention.

ToplingDB requires C++17, gcc 8.3 or newer is recommended, clang also works.

ToplingDB is forked form RocksDB, much faster than RocksDB (see the db_bench comparisons), you can download ToplingDB Enterprise or compile it by yourself:

sudo yum -y install git libaio-devel gcc-c++ gflags-devel zlib-devel bzip2-devel libcurl-devel liburing-devel snappy-devel jemalloc-devel
#sudo apt-get update -y && sudo apt-get install -y libjemalloc-dev libaio-dev libgflags-dev zlib1g-dev libbz2-dev libcurl4-gnutls-dev liburing-dev libsnappy-dev libbz2-dev liblz4-dev libzstd-dev
git clone https://github.com/topling/toplingdb
cd toplingdb
make -j`nproc` db_bench DEBUG_LEVEL=0
sudo make install PREFIX=/some/path # default is /usr/local

After download+uncompress or compile, you can run bundled db_bench.sh(need port 2011), then use ToplingDB in C++, or in Java, Rust.

During compiling, precompiled ToplingZipTable(90 days trial) will be auto downloaded, if download failed, you can pass WITH_TOPLING_ROCKS=0 to make to disalbe it(or contact us). CSPPMemTable is also distributed this way.

ToplingDB's submodule rockside is the entry point of ToplingDB, see SidePlugin wiki.

ToplingDB has much more key features than RocksDB:

1. SidePlugin enables users to write a json(or yaml) to define DB configs
2. Embedded Http Server enables users to view almost all DB info on web, this is a component of SidePlugin
3. Embedded Http Server enables users to online change db/cf options and all db meta objects(such as MemTabFactory, TableFactory, WriteBufferManager ...) without restart the running process
4. Many improvements and refactories on RocksDB, aimed for performance and extendibility
5. memtable as wal log index, omit Flush MemTable to L0, reduce write amp, further improves for large MemTable
6. Topling transaction lock management, 5x faster than rocksdb
7. MultiGet with concurrent IO by fiber/coroutine + io_uring, much faster than RocksDB's async MultiGet
8. Topling de-virtualization, de-virtualize hotspot (virtual) functions, and key prefix caches, bechmarks
9. Topling zero copy for point search(Get/MultiGet) and Iterator
10. Topling memtable as log index, omit memtable flush to L0
11. Builtin SidePlugins for existing RocksDB components(Cache, Comparator, TableFactory, MemTableFactory...)
12. Builtin Prometheus metrics support, this is based on Embedded Http Server
13. Many bugfixes for RocksDB, a small part of such fixes was Pull Requested to upstream RocksDB

1. MyTopling(MySQL on ToplingDB), MyTopling on aliyun
2. Todis(Redis on ToplingDB)

With SidePlugin mechanics, plugins/components can be physically separated from core toplingdb

1. Can be compiled to a separated dynamic lib and loaded at runtime
2. User code need not any changes, just change json/yaml files
3. Topling's non-open-source enterprise plugins/components are delivered in this way

toplingdb
 \__ sideplugin
      \__ rockside                 (submodule , sideplugin core and framework)
      \__ topling-zip              (auto clone, zip and core lib)
      \__ cspp-memtab              (auto clone, sideplugin component)
      \__ cspp-wbwi                (auto clone, sideplugin component)
      \__ topling-sst              (auto clone, sideplugin component)
      \__ topling-rocks            (auto clone, sideplugin component)
      \__ topling-zip_table_reader (auto clone, sideplugin component)
      \__ topling-dcompact         (auto clone, sideplugin component)
           \_ tools/dcompact       (dcompact-worker binary app)

To simplify the compiling, repos are auto cloned in ToplingDB's Makefile, community users will auto clone public repo successfully but fail to auto clone private repo, thus ToplingDB is built without private components, this is so called community version.

For performance and simplicity, ToplingDB disabled some RocksDB features by default:

To enable these features, add -D${MACRO_NAME} to var EXTRA_CXXFLAGS, such as build ToplingDB for java with dynamic ColumnFamily:

make -j`nproc` EXTRA_CXXFLAGS='-DROCKSDB_DYNAMIC_CREATE_CF' rocksdbjava

RocksDB is developed and maintained by Facebook Database Engineering Team. It is built on earlier work on LevelDB by Sanjay Ghemawat (sanjay@google.com) and Jeff Dean (jeff@google.com)

This code is a library that forms the core building block for a fast key-value server, especially suited for storing data on flash drives. It has a Log-Structured-Merge-Database (LSM) design with flexible tradeoffs between Write-Amplification-Factor (WAF), Read-Amplification-Factor (RAF) and Space-Amplification-Factor (SAF). It has multi-threaded compactions, making it especially suitable for storing multiple terabytes of data in a single database.

Start with example usage here: https://github.com/facebook/rocksdb/tree/main/examples

See the github wiki for more explanation.

The public interface is in include/. Callers should not include or rely on the details of any other header files in this package. Those internal APIs may be changed without warning.

Questions and discussions are welcome on the RocksDB Developers Public Facebook group and email list on Google Groups.

RocksDB is dual-licensed under both the GPLv2 (found in the COPYING file in the root directory) and Apache 2.0 License (found in the LICENSE.Apache file in the root directory). You may select, at your option, one of the above-listed licenses.