DBMS > BigchainDB vs. Google Cloud Datastore vs. Snowflake vs. SWC-DB vs. Valentina Server

System Properties Comparison BigchainDB vs. Google Cloud Datastore vs. Snowflake vs. SWC-DB vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

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

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

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

A high performance, scalable Wide Column DBMS

Object-relational database and reports server

Primary database model

Secondary database models

Time Series DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

www.bigchaindb.com

cloud.google.com/datastore

www.snowflake.com

github.com/kashirin-alex/swc-db
www.swcdb.org

www.valentina-db.net

Technical documentation

bigchaindb.readthedocs.io/en/latest

cloud.google.com/datastore/docs

docs.snowflake.net/manuals/index.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Google

Snowflake Computing Inc.

Alex Kashirin

Paradigma Software

Initial release

2016

2008

2014

2020

1999

Current release

0.5, April 2021

5.7.5

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

GPL 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

C++

Server operating systems

Linux

hosted

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

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

schema-free

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

SQL-like query language

yes

APIs and other access methods

CLI Client
RESTful HTTP API

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

CLI Client
JDBC
ODBC

Proprietary protocol
Thrift

ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

JavaScript (Node.js)
Python

C++

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

yes

Triggers

Callbacks using the Google Apps Engine

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using Paxos

yes

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

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

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 for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

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.