DBMS > EXASOL vs. Graph Engine vs. searchxml vs. Snowflake vs. XTDB

System Properties Comparison EXASOL vs. Graph Engine vs. searchxml vs. Snowflake vs. XTDB

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

DBMS for structured and unstructured content wrapped with an application server

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

Relational DBMS

Graph DBMS
Key-value store

Native XML DBMS
Search engine

Relational DBMS

Document store

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.exasol.com

www.graphengine.io

www.searchxml.net/category/products

www.snowflake.com

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

Technical documentation

www.exasol.com/resources

www.graphengine.io/docs/manual

www.searchxml.net/support/handouts

docs.snowflake.net/manuals/index.html

www.xtdb.com/docs

Developer

Exasol

Microsoft

informationpartners gmbh

Snowflake Computing Inc.

Juxt Ltd.

Initial release

2000

2010

2015

2014

2019

Current release

1.0

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

MIT License

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

.NET and C

C++

Clojure

Server operating systems

.NET

Windows

hosted

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

Data scheme

yes

schema-free

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

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

RESTful HTTP API

RESTful HTTP API
WebDAV
XQuery
XSLT

CLI Client
JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

Java
Lua
Python
R

C#
C++
F#
Visual Basic

C++

most other programming languages supported via APIs

JavaScript (Node.js)
Python

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

yes

on the application server

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

sychronisation to multiple collections

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

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

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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, groups and roles according to SQL-standard

Domain, group and role-based access control at the document level and for application services

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.