DBMS > Google Cloud Bigtable vs. OrigoDB vs. Snowflake vs. Splice Machine

System Properties Comparison Google Cloud Bigtable vs. OrigoDB vs. Snowflake vs. Splice Machine

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.

A fully ACID in-memory object graph database

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Key-value store
Wide column store

Document store
Object oriented DBMS

Relational DBMS

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

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Website

cloud.google.com/bigtable

origodb.com

www.snowflake.com

splicemachine.com

Technical documentation

cloud.google.com/bigtable/docs

origodb.com/docs

docs.snowflake.net/manuals/index.html

splicemachine.com/how-it-works

Developer

Google

Robert Friberg et al

Snowflake Computing Inc.

Splice Machine

Initial release

2015

2009

under the name LiveDB

2014

Current release

3.1, March 2021

License

Commercial or Open Source

commercial

Open Source

commercial

Open Source

AGPL 3.0, commercial license available

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

Server operating systems

hosted

Linux
Windows

hosted

Linux
OS X
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

User defined using .NET types and collections

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.

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

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

.NET Client API
HTTP API
LINQ

CLI Client
JDBC
ODBC

JDBC
Native Spark Datasource
ODBC

Supported programming languages

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

.Net

JavaScript (Node.js)
Python

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

yes

user defined functions

yes

Java

Triggers

yes

Domain Events

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

yes

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

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

Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Yes, via Full Spark Integration

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

depending on model

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

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

Write ahead log

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)

Role based authorization

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

Access rights for users, groups and roles 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.