DBMS > Dolt vs. GigaSpaces vs. Google BigQuery vs. GridDB

System Properties Comparison Dolt vs. GigaSpaces vs. Google BigQuery vs. GridDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Large scale data warehouse service with append-only tables

Scalable in-memory time series database optimized for IoT and Big Data

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Time Series DBMS

Secondary database models

Document store

Graph DBMS
Search engine

Key-value store
Relational DBMS

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

Score	0.93
Rank	#194	Overall
	#90	Relational DBMS

Score	0.91
Rank	#197	Overall
	#33	Document stores
	#7	Object oriented DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

www.gigaspaces.com

cloud.google.com/bigquery

griddb.net

Technical documentation

docs.dolthub.com

docs.gigaspaces.com/latest/landing.html

cloud.google.com/bigquery/docs

docs.griddb.net

Developer

DoltHub Inc

Gigaspaces Technologies

Google

Toshiba Corporation

Initial release

2018

2000

2010

2013

Current release

15.5, September 2020

5.1, August 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2; Commercial licenses available

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also 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, C++, .Net

C++

Server operating systems

Linux
macOS
Windows

Linux
macOS
Solaris
Windows

hosted

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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.

XML can be used for describing objects metadata

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-99 for query and DML statements

yes

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

CLI Client
HTTP REST

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C++
Java
Python
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

user defined functions

in JavaScript

Triggers

yes

yes, event driven architecture

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID at container level

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

Only one user is configurable, and must be specified in the config file at startup

Role-based access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights for users can be defined per database

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.