DBMS > Apache Impala vs. Google Cloud Datastore vs. HEAVY.AI vs. Lovefield vs. SQLite

System Properties Comparison Apache Impala vs. Google Cloud Datastore vs. HEAVY.AI vs. Lovefield vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store

Spatial DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

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

Website

impala.apache.org

cloud.google.com/datastore

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

google.github.io/lovefield

www.sqlite.org

Technical documentation

impala.apache.org/impala-docs.html

cloud.google.com/datastore/docs

docs.heavy.ai

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

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

HEAVY.AI, Inc.

Google

Dwayne Richard Hipp

Initial release

2013

2008

2016

2014

2000

Current release

4.1.0, June 2022

5.10, January 2022

2.1.12, February 2017

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C++ and CUDA

JavaScript

Server operating systems

Linux

hosted

Linux

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

tested with Chrome, Firefox, IE, Safari

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

yes

SQL-like query language

via JavaScript builder pattern

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC
Thrift
Vega

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

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

selectable replication factor

Multi-source replication using Paxos

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

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.

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, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.