DBMS > BigchainDB vs. GeoSpock vs. Snowflake vs. Teradata vs. Tibero

System Properties Comparison BigchainDB vs. GeoSpock vs. Snowflake vs. Teradata vs. Tibero

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Spatial and temporal data processing engine for extreme data scale

Cloud-based data warehousing service for structured and semi-structured data

A hybrid cloud data analytics software platform (Teradata Vantage)

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Document store

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Website

www.bigchaindb.com

geospock.com

www.snowflake.com

www.teradata.com

us.tmaxsoft.com/products/tibero

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.snowflake.net/manuals/index.html

docs.teradata.com

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

GeoSpock

Snowflake Computing Inc.

Teradata

TmaxSoft

Initial release

2016

2014

1984

2003

Current release

2.0, September 2019

Teradata Vantage 1.0 MU2, January 2019

6, April 2015

License

Commercial or Open Source

Open Source

AGPL v3

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

Python

Java, Javascript

C and Assembler

Server operating systems

Linux

hosted

hosted
Linux

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

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

temporal, categorical

yes

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

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL 2016 + extensions

yes

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC

CLI Client
JDBC
ODBC

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

JavaScript (Node.js)
Python

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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

yes

UDFs, stored procedures, table functions in parallel

Persistent Stored Procedure (PSM)

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

yes

Sharding

Hashing

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Multi-source replication
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

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

planned for next version

User concepts

Access control

yes

Access rights for users can be defined per table

Users with fine-grained authorization concept, user roles and pluggable authentication

fine grained access rights according to SQL-standard

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.