DBMS > Apache Impala vs. Lovefield vs. SQLite vs. Tigris

System Properties Comparison Apache Impala vs. Lovefield vs. SQLite vs. Tigris

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Embeddable relational database for web apps written in pure JavaScript

Widely used embeddable, in-process RDBMS

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Relational DBMS

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Document store

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Website

impala.apache.org

google.github.io/lovefield

www.sqlite.org

www.tigrisdata.com

Technical documentation

impala.apache.org/impala-docs.html

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

www.sqlite.org/docs.html

www.tigrisdata.com/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

Dwayne Richard Hipp

Tigris Data, Inc.

Initial release

2013

2014

2000

2022

Current release

4.1.0, June 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 2.0

Open Source

Public Domain

Open Source

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

JavaScript

Server operating systems

Linux

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

tested with Chrome, Firefox, IE, Safari

server-less

Linux
macOS
Windows

Data scheme

yes

dynamic column types

yes

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-like DML and DDL statements

SQL-like query language

via JavaScript builder pattern

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

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

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

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

selectable replication factor

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

yes

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

yes

yes, using FoundationDB

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Access rights for users and roles

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.