DBMS > AlaSQL vs. GeoSpock vs. Percona Server for MongoDB vs. Snowflake vs. STSdb

System Properties Comparison AlaSQL vs. GeoSpock vs. Percona Server for MongoDB vs. Snowflake vs. STSdb

Editorial information provided by DB-Engines

Name

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

Description

JavaScript DBMS library

Spatial and temporal data processing engine for extreme data scale

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Relational DBMS

Secondary database models

Time Series DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

alasql.org

geospock.com

www.percona.com/mongodb/software/percona-server-for-mongodb

www.snowflake.com

github.com/STSSoft/STSdb4

Technical documentation

github.com/AlaSQL/alasql

docs.percona.com/percona-distribution-for-mongodb

docs.snowflake.net/manuals/index.html

Developer

Andrey Gershun & Mathias R. Wulff

GeoSpock

Percona

Snowflake Computing Inc.

STS Soft SC

Initial release

2014

2015

2014

2011

Current release

2.0, September 2019

3.4.10-2.10, November 2017

4.0.8, September 2015

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

GPL Version 2

commercial

Open Source

GPLv2, commercial license 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

JavaScript

Java, Javascript

C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

hosted

Linux

hosted

Windows

Data scheme

schema-free

yes

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

temporal, categorical

yes

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

JavaScript API

JDBC

proprietary protocol using JSON

CLI Client
JDBC
ODBC

.NET Client API

Supported programming languages

JavaScript

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

JavaScript (Node.js)
Python

C#
Java

Server-side scripts

Stored procedures

JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

via In-Memory Engine

User concepts

Access control

Access rights for users can be defined per table

Access rights for users and roles

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.