DBMS > Google Cloud Bigtable vs. GridGain vs. Linter vs. Snowflake

System Properties Comparison Google Cloud Bigtable vs. GridGain vs. Linter vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

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

RDBMS for high security requirements

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

Primary database model

Key-value store
Wide column store

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

cloud.google.com/bigtable

www.gridgain.com

linter.ru

www.snowflake.com

Technical documentation

cloud.google.com/bigtable/docs

www.gridgain.com/docs/index.html

docs.snowflake.net/manuals/index.html

Developer

Google

GridGain Systems, Inc.

relex.ru

Snowflake Computing Inc.

Initial release

2015

2007

1990

2014

Current release

GridGain 8.5.1

License

Commercial or Open Source

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

C and C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

hosted

Data scheme

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

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

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

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

CLI Client
JDBC
ODBC

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
Python

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

yes

proprietary syntax with the possibility to convert from PL/SQL

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

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

yes (replicated cache)

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

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.