DBMS > NuoDB vs. Snowflake vs. VoltDB vs. XTDB

System Properties Comparison NuoDB vs. Snowflake vs. VoltDB vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

NuoDB is a webscale distributed database that supports SQL and ACID transactions

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

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

Primary database model

Relational DBMS

Document store

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

Score	0.94
Rank	#197	Overall
	#92	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

www.3ds.com/nuodb-distributed-sql-database

www.snowflake.com

www.voltdb.com

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

Technical documentation

doc.nuodb.com

docs.snowflake.net/manuals/index.html

docs.voltdb.com

www.xtdb.com/docs

Developer

Dassault Systèmes

originally NuoDB, Inc.

Snowflake Computing Inc.

VoltDB Inc.

Juxt Ltd.

Initial release

2013

2014

2010

2019

Current release

11.3, April 2022

1.19, September 2021

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C++

Java, C++

Clojure

Server operating systems

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

hosted

Linux
OS X

for development

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

Data scheme

yes

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

yes

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

only a subset of SQL 99

limited SQL, making use of Apache Calcite

APIs and other access methods

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

Java, SQL

user defined functions

Java

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

data is dynamically stored/cached on the nodes where it is read/written

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Managed transparently by NuoDB

yes

Multi-source replication
Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

tunable commit protocol

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

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

Temporary table

User concepts

Access control

Standard SQL roles/ privileges, Administrative Users

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

Users and roles with access to stored procedures

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.