DBMS > Dolt vs. Google Cloud Datastore vs. SAP Advantage Database Server vs. Snowflake

System Properties Comparison Dolt vs. Google Cloud Datastore vs. SAP Advantage Database Server vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Low-cost RDBMS with access to ISAM and FoxPro data structures

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

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store

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

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

cloud.google.com/datastore

www.sap.com/products/advantage-database-server.html

www.snowflake.com

Technical documentation

docs.dolthub.com

cloud.google.com/datastore/docs

docs.snowflake.net/manuals/index.html

Developer

DoltHub Inc

Google

Sybase, SAP

Snowflake Computing Inc.

Initial release

2018

2008

1993

2014

License

Commercial or Open Source

Open Source

Apache Version 2.0

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

Server operating systems

Linux
macOS
Windows

hosted

Linux
Windows

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

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (GQL)

yes

APIs and other access methods

CLI Client
HTTP REST

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

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
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

Delphi
Perl
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

using Google App Engine

yes

user defined functions

Triggers

yes

Callbacks using the Google Apps Engine

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes

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

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

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

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

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

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.

caching of (temporary) tables can be configured

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)

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.