DBMS > EJDB vs. Google Cloud Bigtable vs. InfinityDB vs. Microsoft SQL Server

System Properties Comparison EJDB vs. Google Cloud Bigtable vs. InfinityDB vs. Microsoft SQL Server

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)

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

A Java embedded Key-Value Store which extends the Java Map interface

Microsofts flagship relational DBMS

Primary database model

Document store

Key-value store
Wide column store

Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	2.97
Rank	#92	Overall
	#15	Key-value stores
	#8	Wide column stores

Score	0.00
Rank	#383	Overall
	#59	Key-value stores

Score	807.76
Rank	#3	Overall
	#3	Relational DBMS

Website

github.com/Softmotions/ejdb

cloud.google.com/bigtable

boilerbay.com

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

Technical documentation

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

cloud.google.com/bigtable/docs

boilerbay.com/infinitydb/manual

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

Developer

Softmotions

Google

Boiler Bay Inc.

Microsoft

Initial release

2012

2015

2002

1989

Current release

4.0

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

GPLv2

commercial

restricted free version is available

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java

C++

Server operating systems

server-less

hosted

All OS with a Java VM

Linux
Windows

Data scheme

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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.

yes

Secondary indexes

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

yes

APIs and other access methods

in-process shared library

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

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

Supported programming languages

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

C#
C++
Go
Java
JavaScript (Node.js)
Python

Java

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

Server-side scripts

Stored procedures

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Internal replication in Colossus, and regional replication between two clusters in different zones

none

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

manual creation possible, using inversions based on multi-value capability

yes

Transaction concepts

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

Atomic single-row operations

ACID

Optimistic locking for transactions; no isolation for bulk loads

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.