DBMS > BigchainDB vs. Coveo vs. GridGain vs. Newts vs. Snowflake

System Properties Comparison BigchainDB vs. Coveo vs. GridGain vs. Newts vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

GridGain is an in-memory computing platform, built on Apache Ignite

Time Series DBMS based on Cassandra

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

Primary database model

Document store

Search engine

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	0.76
Rank	#216	Overall
	#36	Document stores

Score	2.14
Rank	#116	Overall
	#11	Search engines

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

www.bigchaindb.com

www.coveo.com

www.gridgain.com

opennms.github.io/newts

www.snowflake.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.coveo.com

www.gridgain.com/docs/index.html

github.com/OpenNMS/newts/wiki

docs.snowflake.net/manuals/index.html

Developer

Coveo

GridGain Systems, Inc.

OpenNMS Group

Snowflake Computing Inc.

Initial release

2016

2012

2007

2014

Current release

GridGain 8.5.1

License

Commercial or Open Source

Open Source

AGPL v3

commercial

commercial, open source

Open Source

Apache 2.0

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, C++, .Net, Python, REST, SQL

Java

Server operating systems

Linux

hosted

Linux
OS X
Solaris
Windows
z/OS

Linux
OS X
Windows

hosted

Data scheme

schema-free

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

schema-free

yes

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

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

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

CLI Client
RESTful HTTP API

RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

HTTP REST
Java API

CLI Client
JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C#
Java
JavaScript
Python

C#
C++
Java
PHP
Python
Ruby
Scala

Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

yes

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

based on Cassandra

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

yes (replicated cache)

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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

granular access controls, API key management, content filters

Role-based access control
Security Hooks for custom implementations

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

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.