DBMS > Databricks vs. HarperDB vs. PostgreSQL

System Properties Comparison Databricks vs. HarperDB vs. PostgreSQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

HarperDB takes the "stack" out of "tech stack" by combining an ultra-fast document-style data store, in-memory cache, real-time message broker, and your application components into a single distributed technology.

Widely used open source RDBMS

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

Primary database model

Document store
Relational DBMS

Document store

Relational DBMS

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

Secondary database models

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

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

Score	96.01
Rank	#13	Overall
	#2	Document stores
	#9	Relational DBMS

Score	0.49
Rank	#245	Overall
	#38	Document stores

Score	663.42
Rank	#4	Overall
	#4	Relational DBMS

Website

www.databricks.com

www.harperdb.io

www.postgresql.org

Technical documentation

docs.databricks.com

docs.harperdb.io/docs

www.postgresql.org/docs

Developer

Databricks

HarperDB

PostgreSQL Global Development Group

www.postgresql.org/developer

Initial release

2013

2017

1989

1989: Postgres, 1996: PostgreSQL

Current release

3.1, August 2021

16.4, August 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

BSD

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.

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

Node.js

Server operating systems

hosted

Linux
OS X

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

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data types

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

SQL

Support of SQL

with Databricks SQL

SQL-like data manipulation statements

yes

standard with numerous extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

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

Supported programming languages

Python
R
Scala

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

user defined functions and aggregates

Custom Functions

since release 3.1

user defined functions

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

A table resides as a whole on one (or more) nodes in a cluster

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

the nodes on which a table resides can be defined

Source-replica replication

other methods possible by using 3rd party extensions

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

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

Access rights for users and roles

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.