DBMS > Apache Drill vs. Lovefield vs. mSQL vs. SQLite vs. SWC-DB

System Properties Comparison Apache Drill vs. Lovefield vs. mSQL vs. SQLite vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

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

Embeddable relational database for web apps written in pure JavaScript

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used embeddable, in-process RDBMS

A high performance, scalable Wide Column DBMS

Primary database model

Document store
Relational DBMS

Relational DBMS

Wide column store

Secondary database models

Time Series 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.29
Rank	#293	Overall
	#133	Relational DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

drill.apache.org

google.github.io/lovefield

hughestech.com.au/products/msql

www.sqlite.org

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

drill.apache.org/docs

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

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Google

Hughes Technologies

Dwayne Richard Hipp

Alex Kashirin

Initial release

2012

2014

1994

2000

2020

Current release

1.20.3, January 2023

2.1.12, February 2017

4.4, October 2021

3.45.3 (15 April 2024), April 2024

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

commercial

free licenses can be provided

Open Source

Public Domain

Open Source

GPL V3

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

JavaScript

C++

Server operating systems

Linux
OS X
Windows

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

tested with Chrome, Firefox, IE, Safari

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

server-less

Linux

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.

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

SQL-like query language

via JavaScript builder pattern

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

SQL-92 is not fully supported

SQL-like query language

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Proprietary protocol
Thrift

Supported programming languages

C++

JavaScript

C
C++
Delphi
Java
Perl
PHP
Tcl

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

C++

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

Foreign keys

Referential integrity

yes

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

yes

Durability

Support for making data persistent

Depending on the underlying data source

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

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

using MemoryDB

yes

User concepts

Access control

Depending on the underlying data source

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.