DBMS > AlaSQL vs. AnzoGraph DB vs. Snowflake vs. XTDB

System Properties Comparison AlaSQL vs. AnzoGraph DB vs. Snowflake vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

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

Graph DBMS
RDF store

Relational DBMS

Document store

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.29
Rank	#303	Overall
	#25	Graph DBMS
	#14	RDF stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

alasql.org

cambridgesemantics.com/anzograph

www.snowflake.com

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

Technical documentation

github.com/AlaSQL/alasql

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

docs.snowflake.net/manuals/index.html

www.xtdb.com/docs

Developer

Andrey Gershun & Mathias R. Wulff

Cambridge Semantics

Snowflake Computing Inc.

Juxt Ltd.

Initial release

2014

2018

2014

2019

Current release

2.3, January 2021

1.19, September 2021

License

Commercial or Open Source

Open Source

MIT-License

commercial

free trial version available

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

Clojure

Server operating systems

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

Linux

hosted

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

Data scheme

schema-free

Schema-free and OWL/RDFS-schema support

yes

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

schema-free

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

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

SPARQL and SPARQL* as primary query language. Cypher preview.

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

JavaScript API

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

CLI Client
JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

JavaScript

C++
Java
Python

JavaScript (Node.js)
Python

Clojure
Java

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication in MPP-Cluster

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency in MPP-Cluster

Immediate Consistency

Foreign keys

Referential integrity

yes

not needed in graphs

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 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.