DBMS > Apache Phoenix vs. EJDB vs. Google BigQuery vs. LokiJS

System Properties Comparison Apache Phoenix vs. EJDB vs. Google BigQuery vs. LokiJS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

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

Large scale data warehouse service with append-only tables

In-memory JavaScript DBMS

Primary database model

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.43
Rank	#264	Overall
	#42	Document stores

Website

phoenix.apache.org

github.com/Softmotions/ejdb

cloud.google.com/bigquery

github.com/techfort/LokiJS

Technical documentation

phoenix.apache.org

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

cloud.google.com/bigquery/docs

techfort.github.io/LokiJS

Developer

Apache Software Foundation

Softmotions

Google

Initial release

2014

2012

2010

2014

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPLv2

commercial

Open Source

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

Java

JavaScript

Server operating systems

Linux
Unix
Windows

server-less

hosted

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

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

via views

SQL

Support of SQL

yes

APIs and other access methods

JDBC

in-process shared library

RESTful HTTP/JSON API

JavaScript API

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

atomic operations within a single collection possible

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

In-memory capabilities

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

yes

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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

Google Cloud Identity & Access Management (IAM)

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.