DBMS > BigObject vs. GridGain vs. HBase vs. Snowflake

System Properties Comparison BigObject vs. GridGain vs. HBase vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

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

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

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store
Relational DBMS

Wide column store

Relational DBMS

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

Score	0.13
Rank	#342	Overall
	#150	Relational DBMS

Score	1.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

Score	31.25
Rank	#26	Overall
	#2	Wide column stores

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

docs.bigobject.io

www.gridgain.com/docs/index.html

hbase.apache.org/book.html

docs.snowflake.net/manuals/index.html

Developer

BigObject, Inc.

GridGain Systems, Inc.

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Snowflake Computing Inc.

Initial release

2015

2007

2008

2014

Current release

GridGain 8.5.1

2.3.4, January 2021

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

Apache version 2

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

Java, C++, .Net

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux
OS X
Solaris
Windows

Linux
Unix
Windows

using Cygwin

hosted

Data scheme

yes

schema-free, schema definition possible

yes

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

Typing

predefined data types such as float or date

yes

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

SQL-like DML and DDL statements

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

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

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

Java API
RESTful HTTP API
Thrift

CLI Client
JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Groovy
Java
PHP
Python
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Lua

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

yes

Coprocessors in Java

user defined functions

Triggers

yes (cache interceptors and events)

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes (replicated cache)

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

Single row ACID (across millions of columns)

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

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

Security Hooks for custom implementations

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

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.