DBMS > Apache Druid vs. Derby vs. OrigoDB vs. RocksDB vs. SAP Adaptive Server

System Properties Comparison Apache Druid vs. Derby vs. OrigoDB vs. RocksDB vs. SAP Adaptive Server

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

A fully ACID in-memory object graph database

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Document store
Object oriented DBMS

Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	4.60
Rank	#70	Overall
	#38	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	35.09
Rank	#25	Overall
	#17	Relational DBMS

Website

www.sap.com/products/technology-platform/sybase-ase.html

Technical documentation

druid.apache.org/docs/latest/design

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

origodb.com/docs

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_ASE

Developer

Apache Software Foundation and contributors

Apache Software Foundation

Robert Friberg et al

Facebook, Inc.

SAP, Sybase

Initial release

2012

1997

2009

under the name LiveDB

2013

1987

Current release

29.0.1, April 2024

10.17.1.0, November 2023

9.2.1, May 2024

16.0

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache version 2

Open Source

BSD

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

C and C++

Server operating systems

Linux
OS X
Unix

All OS with a Java VM

Linux
Windows

Linux

AIX
HP-UX
Linux
Solaris
Unix
Windows

Data scheme

yes

schema-less columns are supported

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

JDBC

.NET Client API
HTTP API
LINQ

C++ API
Java API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Java

.Net

C
C++
Go
Java
Perl
Python
Ruby

C
C++
Cobol
Java
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Java and Transact-SQL

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Source-replica replication

yes

Multi-source replication
Source-replica replication

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

depending on model

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

fine grained access rights according to SQL-standard

Role based authorization

fine grained access rights according to SQL-standard

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.