DBMS > BigchainDB vs. EJDB vs. HBase vs. Microsoft SQL Server

System Properties Comparison BigchainDB vs. EJDB vs. HBase vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

Microsofts flagship relational DBMS

Primary database model

Document store

Wide column 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.79
Rank	#212	Overall
	#36	Document stores

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

www.bigchaindb.com

github.com/Softmotions/ejdb

hbase.apache.org

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

Technical documentation

bigchaindb.readthedocs.io/en/latest

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

hbase.apache.org/book.html

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

Developer

Softmotions

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Microsoft

Initial release

2016

2012

2008

1989

Current release

2.3.4, January 2021

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

GPLv2

Open Source

Apache version 2

commercial

restricted free version is available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Python

Java

C++

Server operating systems

Linux

server-less

Linux
Unix
Windows

using Cygwin

Linux
Windows

Data scheme

schema-free

schema-free, schema definition possible

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

options to bring your own types, AVRO

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

yes

SQL

Support of SQL

yes

APIs and other access methods

CLI Client
RESTful HTTP API

in-process shared library

Java API
RESTful HTTP API
Thrift

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

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

Server-side scripts

Stored procedures

yes

Coprocessors in Java

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Multi-source replication
Source-replica replication

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 or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

Single row ACID (across millions of columns)

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

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

yes

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.