DBMS > EJDB vs. GBase vs. Kdb+ vs. SingleStore

System Properties Comparison EJDB vs. GBase vs. Kdb+ vs. SingleStore

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	EJDB  Xexclude from comparison	GBase  Xexclude from comparison	Kdb+  Xexclude from comparison	SingleStore former name was MemSQL  Xexclude from comparison
Description	Embeddable document-store database library with JSON representation of queries (in MongoDB style)	An analytical database for business intelligence with large customers in China.	High performance Time Series DBMS	MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type
Primary database model	Document store	Relational DBMS	Time Series DBMS	Relational DBMS
Secondary database models			Relational DBMS	Document store Spatial DBMS Time Series DBMS
DB-Engines Ranking measures the popularity of database management systems Trend Chart	Score 0.09 Rank #317   Overall #42   Document stores	Score 1.12 Rank #165   Overall #78   Relational DBMS	Score 9.12 Rank #53   Overall #2   Time Series DBMS	Score 6.66 Rank #63   Overall #36   Relational DBMS
Website	ejdb.org	www.gbase8a.com	kx.com	www.singlestore.com
Technical documentation	github.com/­Softmotions/­ejdb/­blob/­master/­README.md		code.kx.com	docs.singlestore.com
Developer	Softmotions		Kx Systems, a division of First Derivatives plc	SingleStore Inc.
Initial release	2012		2000 kdb was released 2000, kdb+ in 2003	2013
Current release		GBase 8a	3.6, May 2018	7.6, November 2021
License Commercial or Open Source	Open Source GPLv2	commercial	commercial free 32-bit version	commercial free developer edition available
Cloud-based only Only available as a cloud service	no	no	no	no
DBaaS offerings (sponsored links) Database as a Service Providers of DBaaS offerings, please contact us to be listed.
Implementation language	C		q	C++, Go
Server operating systems	server-less		Linux OS X Solaris Windows	Linux 64 bit version required
Data scheme	schema-free		yes	yes
Typing predefined data types such as float or date	yes string, integer, double, bool, date, object_id		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.			yes	no
Secondary indexes	no		yes table attribute 'grouped'	yes
SQL Support of SQL	no		SQL-like query language (q)	yes but no triggers and foreign keys
APIs and other access methods	in-process shared library		HTTP API JDBC Jupyter Kafka ODBC WebSocket	Cluster Management API as HTTP Rest and CLI HTTP API JDBC ODBC
Supported programming languages	Actionscript C C# C++ Go Java JavaScript (Node.js) Lua Objective-C Pike Python Ruby		C C# C++ Go J Java JavaScript Lua MatLab Perl PHP Python R Scala	Bash C C# Java JavaScript (Node.js) Python
Server-side scripts Stored procedures	no		user defined functions	yes
Triggers	no		yes with views	no
Partitioning methods Methods for storing different data on different nodes	none		horizontal partitioning	Sharding hash partitioning
Replication methods Methods for redundantly storing data on multiple nodes	none		Source-replica replication	Source-replica replication stores two copies of each physical data partition on two separate nodes
MapReduce Offers an API for user-defined Map/Reduce methods	no		no similar paradigm used for internal processing	no can define user-defined aggregate functions for map-reduce-style calculations
Consistency concepts Methods to ensure consistency in a distributed system			Immediate Consistency	Immediate Consistency
Foreign keys Referential integrity	no typically not needed, however similar functionality with collection joins possible		yes	no
Transaction concepts Support to ensure data integrity after non-atomic manipulations of data	no		no	ACID
Concurrency Support for concurrent manipulation of data	yes Read/Write Locking		yes	yes, multi-version concurrency control (MVCC)
Durability Support for making data persistent	yes		yes	yes All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.			yes	yes
User concepts Access control	no		rights management via user accounts	Fine grained access control via users, groups and roles
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
	EJDB	GBase	Kdb+	SingleStore former name was MemSQL
DB-Engines blog posts