DBMS > AlaSQL vs. Rockset vs. SiteWhere vs. Snowflake vs. XTDB

System Properties Comparison AlaSQL vs. Rockset vs. SiteWhere vs. Snowflake vs. XTDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

A scalable, reliable search and analytics service in the cloud, built on RocksDB

M2M integration platform for persisting/querying time series data

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store
Relational DBMS

Secondary database models

Relational DBMS
Search engine

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.82
Rank	#212	Overall
	#36	Document stores

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

alasql.org

rockset.com

github.com/sitewhere/sitewhere

www.snowflake.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

github.com/AlaSQL/alasql

docs.rockset.com

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

www.xtdb.com/docs

Developer

Andrey Gershun & Mathias R. Wulff

Rockset

SiteWhere

Snowflake Computing Inc.

Juxt Ltd.

Initial release

2014

2019

2010

2014

2019

Current release

1.19, September 2021

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

Common Public Attribution License Version 1.0

commercial

Open Source

MIT License

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

C++

Java

Clojure

Server operating systems

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

hosted

Linux
OS X
Windows

hosted

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

predefined scheme

yes

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

schema-free

Typing

predefined data types such as float or date

dynamic typing

yes

yes, extensible-data-notation format

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.

ingestion from XML files supported

yes

Secondary indexes

all fields are automatically indexed

yes

SQL

Support of SQL

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

Read-only SQL queries, including JOINs

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

JavaScript API

HTTP REST

CLI Client
JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

JavaScript

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Clojure
Java

Server-side scripts

Stored procedures

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

based on HBase

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

selectable replication factor

based on HBase

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users and organizations can be defined via Rockset console

Users with fine-grained authorization concept

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.