DBMS > Kyligence Enterprise vs. Oracle Berkeley DB vs. Quasardb vs. Snowflake

System Properties Comparison Kyligence Enterprise vs. Oracle Berkeley DB vs. Quasardb vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed analytics engine for big data, built on top of Apache Kylin

Widely used in-process key-value store

Distributed, high-performance timeseries database

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

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Time Series DBMS

Relational DBMS

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

Score	0.46
Rank	#266	Overall
	#124	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

kyligence.io/kyligence-enterprise

www.oracle.com/database/technologies/related/berkeleydb.html

quasar.ai

www.snowflake.com

Technical documentation

docs.oracle.com/cd/E17076_05/html/index.html

doc.quasar.ai/master

docs.snowflake.net/manuals/index.html

Developer

Kyligence, Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

quasardb

Snowflake Computing Inc.

Initial release

2016

1994

2009

2014

Current release

18.1.40, May 2020

3.14.1, January 2024

License

Commercial or Open Source

commercial

Open Source

commercial license available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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++ (depending on the Berkeley DB edition)

C++

Server operating systems

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

BSD
Linux
OS X
Windows

hosted

Data scheme

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

integer and binary

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

with tags

SQL

Support of SQL

ANSI SQL for queries (using Apache Calcite)

yes

SQL interfaced based on SQLite is available

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

only for the SQL API

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Source-replica replication with selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with 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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

Cryptographically strong user authentication and audit trail

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.