DBMS > BigchainDB vs. Geode vs. IRONdb vs. Microsoft SQL Server

System Properties Comparison BigchainDB vs. Geode vs. IRONdb vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Microsofts flagship relational DBMS

Primary database model

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	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

www.bigchaindb.com

geode.apache.org

www.circonus.com/solutions/time-series-database/

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

Technical documentation

bigchaindb.readthedocs.io/en/latest

geode.apache.org/docs

docs.circonus.com/irondb/category/getting-started

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

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Circonus LLC.

Microsoft

Initial release

2016

2002

2017

1989

Current release

1.1, February 2017

V0.10.20, January 2018

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache Version 2; commercial licenses available as Gemfire

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.

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

Python

Java

C and C++

C++

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL-like query language (OQL)

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

CLI Client
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

HTTP API

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

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

Server-side scripts

Stored procedures

user defined functions

yes, in Lua

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

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

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

Multi-source replication

configurable replication factor, datacenter aware

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

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 rights per client and object definable

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.