DBMS > Badger vs. Datomic vs. Kdb+

System Properties Comparison Badger vs. Datomic vs. Kdb+

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	Badger  Xexclude from comparison	Datomic  Xexclude from comparison	Kdb+  Xexclude from comparison
Description	An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.	Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability	High performance Time Series DBMS
Primary database model	Key-value store	Relational DBMS	Time Series DBMS
Secondary database models			Relational DBMS
DB-Engines Ranking measures the popularity of database management systems Trend Chart	Score 0.10 Rank #316   Overall #46   Key-value stores	Score 1.68 Rank #135   Overall #67   Relational DBMS	Score 9.18 Rank #52   Overall #2   Time Series DBMS
Website	github.com/­dgraph-io/­badger	www.datomic.com	kx.com
Technical documentation	godoc.org/­github.com/­dgraph-io/­badger	docs.datomic.com	code.kx.com
Developer	DGraph Labs	Cognitect	Kx Systems, a division of First Derivatives plc
Initial release	2017	2012	2000 kdb was released 2000, kdb+ in 2003
Current release		1.0.6362, January 2022	3.6, May 2018
License Commercial or Open Source	Open Source Apache 2.0	commercial limited edition free	commercial free 32-bit version
Cloud-based only Only available as a cloud service	no	no	no
DBaaS offerings (sponsored links) Database as a Service Providers of DBaaS offerings, please contact us to be listed.
Implementation language	Go	Java, Clojure	q
Server operating systems	BSD Linux OS X Solaris Windows	All OS with a Java VM	Linux OS X Solaris Windows
Data scheme	schema-free	yes	yes
Typing predefined data types such as float or date	no	yes	yes
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.	no	no	yes
Secondary indexes	no	yes	yes table attribute 'grouped'
SQL Support of SQL	no	no	SQL-like query language (q)
APIs and other access methods		RESTful HTTP API	HTTP API JDBC Jupyter Kafka ODBC WebSocket
Supported programming languages	Go	Clojure Java	C C# C++ Go J Java JavaScript Lua MatLab Perl PHP Python R Scala
Server-side scripts Stored procedures	no	yes Transaction Functions	user defined functions
Triggers	no	By using transaction functions	yes with views
Partitioning methods Methods for storing different data on different nodes	none	none But extensive use of caching in the application peers	horizontal partitioning
Replication methods Methods for redundantly storing data on multiple nodes	none	none But extensive use of caching in the application peers	Source-replica replication
MapReduce Offers an API for user-defined Map/Reduce methods	no	no	no similar paradigm used for internal processing
Consistency concepts Methods to ensure consistency in a distributed system	none	Immediate Consistency	Immediate Consistency
Foreign keys Referential integrity	no	no	yes
Transaction concepts Support to ensure data integrity after non-atomic manipulations of data	no	ACID	no
Concurrency Support for concurrent manipulation of data	yes	yes	yes
Durability Support for making data persistent	yes	yes using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)	yes
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.	no	yes recommended only for testing and development	yes
User concepts Access control	no	no	rights management via user accounts
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.
More resources
	Badger	Datomic	Kdb+
DB-Engines blog posts