DBMS > BigObject vs. GridGain vs. KeyDB vs. SiriDB vs. Snowflake

System Properties Comparison BigObject vs. GridGain vs. KeyDB vs. SiriDB vs. Snowflake

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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Open Source Time Series DBMS

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

Key-value store

Time Series DBMS

Relational DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

bigobject.io

www.gridgain.com

github.com/Snapchat/KeyDB
keydb.dev

siridb.com

www.snowflake.com

Technical documentation

docs.bigobject.io

www.gridgain.com/docs/index.html

docs.keydb.dev

docs.siridb.com

docs.snowflake.net/manuals/index.html

Developer

BigObject, Inc.

GridGain Systems, Inc.

EQ Alpha Technology Ltd.

Cesbit

Snowflake Computing Inc.

Initial release

2015

2007

2019

2017

2014

Current release

GridGain 8.5.1

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

BSD-3

Open Source

MIT License

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++

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

hosted

Data scheme

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

yes

Numeric data

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

by using the Redis Search module

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

Proprietary protocol

RESP - REdis Serialization Protoco

HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Lua

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

Lua

user defined functions

Triggers

yes (cache interceptors and events)

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)

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple password-based access control and ACL

simple rights management via user accounts

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.