DBMS > DuckDB vs. EsgynDB vs. Snowflake vs. VoltDB

System Properties Comparison DuckDB vs. EsgynDB vs. Snowflake vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, in-process, column-oriented SQL OLAP RDBMS

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Primary database model

Relational DBMS

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

Score	4.63
Rank	#69	Overall
	#37	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

Technical documentation

duckdb.org/docs

docs.snowflake.net/manuals/index.html

docs.voltdb.com

Developer

Esgyn

Snowflake Computing Inc.

VoltDB Inc.

Initial release

2018

2015

2014

2010

Current release

1.0.0, June 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

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

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

C++, Java

Java, C++

Server operating systems

server-less

Linux

hosted

Linux
OS X

for development

Data scheme

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

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

Arrow Database Connectivity (ADBC)
CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C#

3rd party driver
C++
Crystal

3rd party driver
Go

3rd party driver
Java
Lisp

3rd party driver
Python
R
Ruby

3rd party driver
Rust
Swift
Zig

3rd party driver

All languages supporting JDBC/ODBC/ADO.Net

JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

Java

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication between multi datacenters

yes

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

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

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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.