DBMS > EDB Postgres vs. PlanetScale vs. Realm vs. RocksDB

System Properties Comparison EDB Postgres vs. PlanetScale vs. Realm vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

The EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

Scalable, distributed, serverless MySQL database platform built on top of Vitess

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

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

Primary database model

Relational DBMS

Document store

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	1.90
Rank	#135	Overall
	#63	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

Technical documentation

www.enterprisedb.com/docs

planetscale.com/docs

realm.io/docs

github.com/facebook/rocksdb/wiki

Developer

EnterpriseDB

PlanetScale

Realm, acquired by MongoDB in May 2019

Facebook, Inc.

Initial release

2005

2020

2014

2013

Current release

14, December 2021

8.11.4, April 2024

License

Commercial or Open Source

commercial

BSD for PostgreSQL-components

commercial

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.

Implementation language

C++

Server operating systems

Linux
Windows

Docker
Linux
macOS

Android
Backend: server-less
iOS
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

SQL

Support of SQL

yes

standard with numerous extensions

yes

with proprietary extensions

APIs and other access methods

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

ADO.NET
JDBC
MySQL protocol
ODBC

C++ API
Java API

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
PHP
Python
Tcl

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
Java

with Android only
Objective-C
React Native
Swift

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

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

yes

proprietary syntax

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

by hash, list or range

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

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 realm

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

yes

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.