DBMS > EJDB vs. Google BigQuery vs. Microsoft Azure SQL Database vs. mSQL vs. OrigoDB

System Properties Comparison EJDB vs. Google BigQuery vs. Microsoft Azure SQL Database vs. mSQL vs. OrigoDB

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

Database as a Service offering with high compatibility to Microsoft SQL Server

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph database

Primary database model

Document store

Relational DBMS

Document store
Object oriented DBMS

Secondary database models

Document store
Graph DBMS
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	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Website

github.com/Softmotions/ejdb

cloud.google.com/bigquery

azure.microsoft.com/en-us/products/azure-sql/database

hughestech.com.au/products/msql

origodb.com

Technical documentation

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

cloud.google.com/bigquery/docs

docs.microsoft.com/en-us/azure/azure-sql

origodb.com/docs

Developer

Softmotions

Google

Microsoft

Hughes Technologies

Robert Friberg et al

Initial release

2012

2010

1994

2009

under the name LiveDB

Current release

V12

4.4, October 2021

License

Commercial or Open Source

Open Source

GPLv2

commercial

free licenses can be provided

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

C++

Server operating systems

server-less

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

User defined using .NET types and collections

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.

yes

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

in-process shared library

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

JDBC
ODBC

.NET Client API
HTTP API
LINQ

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

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Transact SQL

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, with always 3 replicas available

none

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

none

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

depending on model

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

Write ahead log

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

Role based authorization

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.