DBMS > BigObject vs. Dolt vs. Google Cloud Datastore vs. SAP HANA

System Properties Comparison BigObject vs. Dolt vs. Google Cloud Datastore vs. SAP HANA

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

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

bigobject.io

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

cloud.google.com/datastore

www.sap.com/products/hana.html

Technical documentation

docs.bigobject.io

docs.dolthub.com

cloud.google.com/datastore/docs

help.sap.com/hana

Developer

BigObject, Inc.

DoltHub Inc

Google

SAP

Initial release

2015

2018

2008

2010

Current release

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache Version 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

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
macOS
Windows

hosted

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-like query language (GQL)

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

CLI Client
HTTP REST

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC

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
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

Lua

yes

currently in alpha release

using Google App Engine

SQLScript, R

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

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 using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

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

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

yes

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.