DBMS > Dolt vs. Google Cloud Spanner vs. Interbase vs. Snowflake

System Properties Comparison Dolt vs. Google Cloud Spanner vs. Interbase vs. Snowflake

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

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

Light-weight proven RDBMS

originally from Borland

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

Primary database model

Relational DBMS

Secondary database models

Document store

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	2.84
Rank	#100	Overall
	#51	Relational DBMS

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

cloud.google.com/spanner

www.embarcadero.com/products/interbase

www.snowflake.com

Technical documentation

docs.dolthub.com

cloud.google.com/spanner/docs

docs.embarcadero.com/products/interbase

docs.snowflake.net/manuals/index.html

Developer

DoltHub Inc

Google

Embarcadero

Snowflake Computing Inc.

Initial release

2018

2017

1984

2014

Current release

InterBase 2020, December 2019

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

Android
iOS
Linux
OS X
Windows

hosted

Data scheme

yes

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

Typing

predefined data types such as float or date

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.

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

Query statements complying to ANSI 2011

yes

APIs and other access methods

CLI Client
HTTP REST

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

ADO.NET
JDBC
ODBC

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

Go
Java
JavaScript (Node.js)
Python

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

Interbase procedure and trigger language

user defined functions

Triggers

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 with 3 replicas for regional instances.

Interbase Change Views

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

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

Transaction concepts

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

ACID

Strict serializable isolation

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

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)

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.