DBMS > EJDB vs. Google BigQuery vs. NuoDB vs. PlanetScale

System Properties Comparison EJDB vs. Google BigQuery vs. NuoDB vs. PlanetScale

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

NuoDB is a webscale distributed database that supports SQL and ACID transactions

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Primary database model

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.94
Rank	#197	Overall
	#92	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Website

github.com/Softmotions/ejdb

cloud.google.com/bigquery

www.3ds.com/nuodb-distributed-sql-database

planetscale.com

Technical documentation

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

cloud.google.com/bigquery/docs

doc.nuodb.com

planetscale.com/docs

Developer

Softmotions

Google

Dassault Systèmes

originally NuoDB, Inc.

PlanetScale

Initial release

2012

2010

2013

2020

License

Commercial or Open Source

Open Source

GPLv2

commercial

limited edition free

commercial

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

Server operating systems

server-less

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

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

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

in-process shared library

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

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++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Java, SQL

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

data is dynamically stored/cached on the nodes where it is read/written

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Managed transparently by NuoDB

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

tunable commit protocol

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

MVCC

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

Temporary table

yes

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Standard SQL roles/ privileges, Administrative Users

Users with fine-grained authorization concept

no user groups or 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.