DBMS > EJDB vs. Google BigQuery vs. HarperDB vs. Lovefield

System Properties Comparison EJDB vs. Google BigQuery vs. HarperDB vs. Lovefield

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Large scale data warehouse service with append-only tables

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Embeddable relational database for web apps written in pure JavaScript

Primary database model

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Website

github.com/Softmotions/ejdb

cloud.google.com/bigquery

www.harperdb.io

google.github.io/lovefield

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

cloud.google.com/bigquery/docs

docs.harperdb.io/docs

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

Developer

Softmotions

Google

HarperDB

Google

Initial release

2012

2010

2017

2014

Current release

3.1, August 2021

2.1.12, February 2017

License

Commercial or Open Source

Open Source

GPLv2

commercial

free community edition available

Open Source

Apache 2.0

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

Node.js

JavaScript

Server operating systems

server-less

hosted

Linux
OS X

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

tested with Chrome, Firefox, IE, Safari

Data scheme

schema-free

yes

dynamic schema

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

JSON data types

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

yes

SQL-like data manipulation statements

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

in-process shared library

RESTful HTTP/JSON API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

JavaScript

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Custom Functions

since release 3.1

Triggers

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

none

A table resides as a whole on one (or more) nodes in a cluster

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

the nodes on which a table resides can be defined

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

Since BigQuery is designed for querying data

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

In-memory capabilities

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

yes

using MemoryDB

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.