DBMS > Apache Drill vs. BoltDB vs. jBASE vs. Quasardb vs. SQLite

System Properties Comparison Apache Drill vs. BoltDB vs. jBASE vs. Quasardb vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

An embedded key-value store for Go.

A robust multi-value DBMS comprising development tools and middleware

Distributed, high-performance timeseries database

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

drill.apache.org

github.com/boltdb/bolt

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

quasar.ai

www.sqlite.org

Technical documentation

drill.apache.org/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

doc.quasar.ai/master

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Rocket Software (formerly Zumasys)

quasardb

Dwayne Richard Hipp

Initial release

2012

2013

1991

2009

2000

Current release

1.20.3, January 2023

5.7

3.14.1, January 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

MIT License

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Public Domain

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++

Server operating systems

Linux
OS X
Windows

BSD
Linux
OS X
Solaris
Windows

AIX
Linux
Windows

BSD
Linux
OS X
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

optional

yes

integer and binary

yes

not rigid because of 'dynamic typing' concept.

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

with tags

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

Embedded SQL for jBASE in BASIC

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++

.Net
Basic
Jabbascript
Java

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

Depending on the underlying data source

yes

by using LevelDB

yes

In-memory capabilities

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

Depending on the underlying data source

yes

Transient mode

yes

User concepts

Access control

Depending on the underlying data source

Access rights can be defined down to the item level

Cryptographically strong user authentication and audit trail

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.