DBMS > Apache Drill vs. HEAVY.AI vs. Lovefield vs. SQLite vs. TinkerGraph

System Properties Comparison Apache Drill vs. HEAVY.AI vs. Lovefield vs. SQLite vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Embeddable relational database for web apps written in pure JavaScript

Widely used embeddable, in-process RDBMS

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Document store
Relational DBMS

Relational DBMS

Graph DBMS

Secondary database models

Spatial 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	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

drill.apache.org

github.com/heavyai/heavydb
www.heavy.ai

google.github.io/lovefield

www.sqlite.org

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

drill.apache.org/docs

docs.heavy.ai

github.com/google/lovefield/blob/master/docs/spec_index.md

www.sqlite.org/docs.html

Developer

Apache Software Foundation

HEAVY.AI, Inc.

Google

Dwayne Richard Hipp

Initial release

2012

2016

2014

2000

2009

Current release

1.20.3, January 2023

5.10, January 2022

2.1.12, February 2017

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

Open Source

Public Domain

Open Source

Apache 2.0

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

JavaScript

Java

Server operating systems

Linux
OS X
Windows

Linux

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

server-less

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

SQL-like query language

via JavaScript builder pattern

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
Thrift
Vega

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

TinkerPop 3

Supported programming languages

C++

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript

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

Groovy
Java

Server-side scripts

Stored procedures

user defined functions

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

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

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

optional

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

using MemoryDB

yes

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

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.