DBMS > EJDB vs. Google Cloud Datastore vs. IBM Db2 warehouse vs. Microsoft SQL Server vs. Teradata

System Properties Comparison EJDB vs. Google Cloud Datastore vs. IBM Db2 warehouse vs. Microsoft SQL Server vs. Teradata

Editorial information provided by DB-Engines

Name

Description

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

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

Cloud-based data warehousing service

Microsofts flagship relational DBMS

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

github.com/Softmotions/ejdb

cloud.google.com/datastore

www.ibm.com/products/db2/warehouse

www.microsoft.com/en-us/sql-server

www.teradata.com

Technical documentation

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

cloud.google.com/datastore/docs

learn.microsoft.com/en-US/sql/sql-server

docs.teradata.com

Developer

Softmotions

Google

IBM

Microsoft

Teradata

Initial release

2012

2008

2014

1989

1984

Current release

SQL Server 2022, November 2022

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

GPLv2

commercial

restricted free version is available

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

Linux
Windows

hosted
Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes, details here

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.

Import/export of XML data possible

yes

Secondary indexes

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

SQL-like query language (GQL)

yes

SQL 2016 + extensions

APIs and other access methods

in-process shared library

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

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

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

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

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

using Google App Engine

PL/SQL, SQL PL

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

UDFs, stored procedures, table functions in parallel

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

yes

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

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

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

yes

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

User concepts

Access control

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.