DBMS > Oracle Berkeley DB vs. PlanetScale vs. SAP HANA vs. SAP SQL Anywhere

System Properties Comparison Oracle Berkeley DB vs. PlanetScale vs. SAP HANA vs. SAP SQL Anywhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used in-process key-value store

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

In-memory, column based data store. Available as appliance or cloud service

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

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

planetscale.com

www.sap.com/products/hana.html

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

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

planetscale.com/docs

help.sap.com/hana

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

PlanetScale

SAP

formerly Sybase

Initial release

1994

2020

2010

1992

Current release

18.1.40, May 2020

2.0 SPS07 (April 4, 2023), April 2023

17, July 2015

License

Commercial or Open Source

Open Source

commercial license available

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Docker
Linux
macOS

Appliance or cloud-service

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
ODBC

ADO.NET
HTTP API
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

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax

SQLScript, R

yes, in C/C++, Java, .Net or Perl

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

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

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

yes

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.