DBMS > Databricks vs. EJDB vs. Infobright vs. Newts vs. Tkrzw

System Properties Comparison Databricks vs. EJDB vs. Infobright vs. Newts vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Time Series DBMS based on Cassandra

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Document store
Relational DBMS

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

Score	81.08
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

www.databricks.com

github.com/Softmotions/ejdb

ignitetech.com/softwarelibrary/infobrightdb

opennms.github.io/newts

dbmx.net/tkrzw

Technical documentation

docs.databricks.com

github.com/Softmotions/ejdb/blob/master/README.md

github.com/OpenNMS/newts/wiki

Developer

Databricks

Softmotions

Ignite Technologies Inc.; formerly InfoBright Inc.

OpenNMS Group

Mikio Hirabayashi

Initial release

2013

2012

2005

2014

2020

Current release

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

GPLv2

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

Server operating systems

hosted

server-less

Linux
Windows

Linux
OS X
Windows

Linux
macOS

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

Secondary indexes

yes

Knowledge Grid Technology used instead

SQL

Support of SQL

with Databricks SQL

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

in-process shared library

ADO.NET
JDBC
ODBC

HTTP REST
Java API

Supported programming languages

Python
R
Scala

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions and aggregates

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

selectable replication factor

based on Cassandra

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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

DB-Engines blog posts

PostgreSQL is the DBMS of the Year 2023
2 January 2024, Matthias Gelbmann, Paul Andlinger

show all

Recent citations in the news

Databricks Agrees to Acquire Tabular, the Company Founded by the Original Creators of Apache Iceberg USA - English
4 June 2024, PR Newswire

Databricks buys Tabular to win the Iceberg war – Blocks and Files
5 June 2024, Blocks and Files

Databricks to buy data management firm Tabular for over $1 bln
4 June 2024, Reuters

Fenwick Represents Databricks in its Pending Acquisition of…
4 June 2024, Fenwick & West LLP

Databricks' $1B Tabular buy raises questions around table format wars
5 June 2024, The Register

provided by Google News

Share this page