DBMS > Dolt vs. GeoSpock vs. Memcached vs. Snowflake vs. SQream DB

System Properties Comparison Dolt vs. GeoSpock vs. Memcached vs. Snowflake vs. SQream DB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Spatial and temporal data processing engine for extreme data scale

In-memory key-value store, originally intended for caching

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

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store

Time Series DBMS

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

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

geospock.com

www.memcached.org

www.snowflake.com

sqream.com

Technical documentation

docs.dolthub.com

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

docs.sqream.com

Developer

DoltHub Inc

GeoSpock

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

SQream Technologies

Initial release

2018

2003

2014

2017

Current release

2.0, September 2019

1.6.27, May 2024

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

BSD 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, Javascript

C++, CUDA, Haskell, Java, Scala

Server operating systems

Linux
macOS
Windows

hosted

FreeBSD
Linux
OS X
Unix
Windows

hosted

Linux

Data scheme

yes

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

temporal, categorical

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

CLI Client
HTTP REST

JDBC

Proprietary protocol

CLI Client
JDBC
ODBC

.Net
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
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

user defined functions

user defined functions in Python

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

none

yes

horizontal and vertical partitioning

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.

none

Repcached, a Memcached patch, provides this functionallity

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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.

User concepts

Access control

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

Access rights for users can be defined per table

yes

using SASL (Simple Authentication and Security Layer) protocol

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.