DBMS > Derby vs. EsgynDB vs. Kdb vs. Microsoft Access vs. Snowflake

System Properties Comparison Derby vs. EsgynDB vs. Kdb vs. Microsoft Access vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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

High performance Time Series DBMS

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

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

Primary database model

Relational DBMS

Time Series DBMS
Vector DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	4.60
Rank	#70	Overall
	#38	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	7.71
Rank	#49	Overall
	#2	Time Series DBMS
	#1	Vector DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

db.apache.org/derby

www.esgyn.cn

kx.com

www.microsoft.com/en-us/microsoft-365/access

www.snowflake.com

Technical documentation

db.apache.org/derby/manuals/index.html

code.kx.com

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Esgyn

Kx Systems, a division of First Derivatives plc

Microsoft

Snowflake Computing Inc.

Initial release

1997

2015

2000

kdb was released 2000, kdb+ in 2003

1992

2014

Current release

10.17.1.0, November 2023

3.6, May 2018

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache version 2

commercial

free 32-bit version

commercial

Bundled with Microsoft Office

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

Java

C++, Java

C++

Server operating systems

All OS with a Java VM

Linux

Linux
OS X
Solaris
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

yes

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

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

table attribute 'grouped'

yes

SQL

Support of SQL

yes

SQL-like query language (q)

yes

but not compliant to any SQL standard

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

Java

All languages supporting JDBC/ODBC/ADO.Net

C
C#
C++
Go
J
Java
JavaScript
Lua
MatLab
Perl
PHP
Python
R
Scala

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

with views

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication between multi datacenters

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

similar paradigm used for internal processing

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

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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

rights management via user accounts

a simple user-level security was built in till version Access 2003

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

More information provided by the system vendor

Specific characteristics

Integrated columnar database & programming system for streaming, real time and historical...
» more

Competitive advantages

provides seamless scalability; runs on industry standard server platforms; is top-ranked...
» more

Typical application scenarios

tick database streaming sensor data massive intelligence applications oil and gas...
» more

Key customers

Goldman Sachs Morgan Stanley Merrill Lynch J.P. Morgan Deutsche Bank IEX Securities...
» more

Market metrics

kdb+ performance and reliability proven by our customers in critical infrastructure...
» more

Licensing and pricing models

upon request
» more

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.