DBMS > AlaSQL vs. GeoMesa vs. Snowflake vs. Splunk vs. Teradata

System Properties Comparison AlaSQL vs. GeoMesa vs. Snowflake vs. Splunk vs. Teradata

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

Analytics Platform for Big Data

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Document store
Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

Technical documentation

github.com/AlaSQL/alasql

www.geomesa.org/documentation/stable/user/index.html

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

docs.teradata.com

Developer

Andrey Gershun & Mathias R. Wulff

CCRi and others

Snowflake Computing Inc.

Splunk Inc.

Teradata

Initial release

2014

2003

1984

Current release

5.0.0, May 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache License 2.0

commercial

Limited free edition and free developer edition available

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

JavaScript

Scala

Server operating systems

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

hosted

Linux
OS X
Solaris
Windows

hosted
Linux

Data scheme

schema-free

yes

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

yes

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.

yes

Secondary indexes

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

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

yes

Splunk Search Processing Language for search commands

yes

SQL 2016 + extensions

APIs and other access methods

JavaScript API

CLI Client
JDBC
ODBC

HTTP REST

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

JavaScript

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

yes

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

yes

Multi-source replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

depending on storage layer

Immediate Consistency

Eventual 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

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Users with fine-grained authorization concept, user roles and pluggable authentication

Access rights for users and roles

fine grained access rights according to SQL-standard

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.