DBMS > Apache Derby vs. PostgreSQL vs. ScyllaDB

System Properties Comparison Apache Derby vs. PostgreSQL vs. ScyllaDB

Please select another system to include it in the comparison.

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.

Widely used open source RDBMS

Developed as objectoriented DBMS (Postgres), gradually enhanced with 'standards' like SQL

Cassandra and DynamoDB compatible wide column store

Primary database model

Relational DBMS

with object oriented extensions, e.g.: user defined types/functions and inheritance. Handling of key/value pairs with hstore module.

Wide column store

Secondary database models

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

Key-value store

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

Score	3.04
Rank	#85	Overall
	#46	Relational DBMS

Score	674.32
Rank	#4	Overall
	#4	Relational DBMS

Score	3.70
Rank	#69	Overall
	#5	Wide column stores

Website

db.apache.org/derby

www.postgresql.org

www.scylladb.com

Technical documentation

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

www.postgresql.org/docs

docs.scylladb.com

Developer

Apache Software Foundation

PostgreSQL Global Development Group

www.postgresql.org/developer

ScyllaDB

Initial release

1997

1989

1989: Postgres, 1996: PostgreSQL

2015

Current release

10.17.1.0, November 2023

16.4, August 2024

ScyllaDB Open Source 6.2.0, October 2024

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

BSD

Open Source

Open Source (AGPL), commercial license available

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.

PostgreSQL Flex @ STACKIT offers managed PostgreSQL Instances with adjustable CPU, RAM, storage amount and speed and several extensions available, in enterprise grade to perfectly match all application requirements. All 100% GDPR-compliant.

Implementation language

Java

C++

Server operating systems

All OS with a Java VM

FreeBSD
HP-UX
Linux
NetBSD
OpenBSD
OS X
Solaris
Unix
Windows

Linux

Data scheme

yes

schema-free

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

cluster global secondary indices

SQL

Support of SQL

yes

standard with numerous extensions

SQL-like DML and DDL statements (CQL)

APIs and other access methods

JDBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

Supported programming languages

Java

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes, Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

partitioning by range, list and (since PostgreSQL 11) by hash

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

selectable replication factor

Representation of geographical distribution of servers is possible

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Atomicity and isolation are supported for single operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

in-memory tables

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per object

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.