DBMS > Apache Drill vs. Lovefield vs. Memcached vs. mSQL vs. SQLite

System Properties Comparison Apache Drill vs. Lovefield vs. Memcached vs. mSQL vs. SQLite

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

In-memory key-value store, originally intended for caching

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Relational DBMS

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

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

drill.apache.org

google.github.io/lovefield

www.memcached.org

hughestech.com.au/products/msql

www.sqlite.org

Technical documentation

drill.apache.org/docs

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

github.com/memcached/memcached/wiki

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Google

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Hughes Technologies

Dwayne Richard Hipp

Initial release

2012

2014

2003

1994

2000

Current release

1.20.3, January 2023

2.1.12, February 2017

1.6.25, March 2024

4.4, October 2021

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

Open Source

BSD license

commercial

free licenses can be provided

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

JavaScript

Server operating systems

Linux
OS X
Windows

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

tested with Chrome, Firefox, IE, Safari

FreeBSD
Linux
OS X
Unix
Windows

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

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

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

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Proprietary protocol

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++

JavaScript

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

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

yes

using SASL (Simple Authentication and Security Layer) protocol

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.