DBMS > Badger vs. Cachelot.io vs. XTDB

System Properties Comparison Badger vs. Cachelot.io vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

In-memory caching system

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Key-value store

Document store

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	0.04
Rank	#388	Overall
	#62	Key-value stores

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

github.com/dgraph-io/badger

cachelot.io

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

godoc.org/github.com/dgraph-io/badger

www.xtdb.com/docs

Developer

DGraph Labs

Juxt Ltd.

Initial release

2017

2015

2019

Current release

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Simplified BSD License

Open Source

MIT License

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Clojure

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes, extensible-data-notation format

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

SQL

Support of SQL

limited SQL, making use of Apache Calcite

APIs and other access methods

Memcached protocol

HTTP REST
JDBC

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

Clojure
Java

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Foreign keys

Referential integrity

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

Share this page