DBMS > EsgynDB vs. IBM Db2 vs. Qdrant vs. RDF4J vs. Snowflake

System Properties Comparison EsgynDB vs. IBM Db2 vs. Qdrant vs. RDF4J vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

Common in IBM host environments, 2 different versions for host and Windows/Linux

A high-performance vector database with neural network or semantic-based matching

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

Primary database model

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Vector DBMS

RDF store

Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	123.05
Rank	#9	Overall
	#6	Relational DBMS

Score	1.53
Rank	#145	Overall
	#7	Vector DBMS

Score	0.72
Rank	#222	Overall
	#9	RDF stores

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

www.esgyn.cn

www.ibm.com/products/db2

github.com/qdrant/qdrant
qdrant.tech

rdf4j.org

www.snowflake.com

Technical documentation

www.ibm.com/docs/en/db2

qdrant.tech/documentation

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

Developer

Esgyn

IBM

Qdrant

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Snowflake Computing Inc.

Initial release

2015

1983

host version

2021

2004

2014

Current release

12.1, October 2016

License

Commercial or Open Source

commercial

free version is available

Open Source

Apache Version 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

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

Rust

Java

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Docker
Linux
macOS
Windows

Linux
OS X
Unix
Windows

hosted

Data scheme

yes

schema-free

yes

RDF Schemas

yes

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

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

with separate tools (MQ, InfoSphere)

Collection-level replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency, tunable consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

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

Key-based authentication

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.