DBMS > Oracle Berkeley DB vs. OrientDB vs. SQLite vs. YTsaurus

System Properties Comparison Oracle Berkeley DB vs. OrientDB vs. SQLite vs. YTsaurus

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

Multi-model DBMS (Document, Graph, Key/Value)

Widely used embeddable, in-process RDBMS

YTsaurus is an open source platform for distributed storage and processing.

Primary database model

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store
Graph DBMS
Key-value store

Relational DBMS

Document store
Key-value store

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

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Score	3.02
Rank	#88	Overall
	#16	Document stores
	#6	Graph DBMS
	#12	Key-value stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.15
Rank	#323	Overall
	#44	Document stores
	#47	Key-value stores

Website

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

orientdb.org

www.sqlite.org

ytsaurus.tech

Technical documentation

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

www.orientdb.com/docs/last/index.html

www.sqlite.org/docs.html

ytsaurus.tech/docs/en

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

OrientDB LTD; CallidusCloud; SAP

Dwayne Richard Hipp

Yandex

Initial release

1994

2010

2000

2023

Current release

18.1.40, May 2020

3.2.29, March 2024

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

commercial license available

Open Source

Apache version 2

Open Source

Public Domain

Open Source

Apache License, Version 2.0

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

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

Java

C++

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

All OS with a Java JDK (>= JDK 6)

server-less

Ubuntu

Data scheme

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

SQL-like query language, no joins

yes

SQL-92 is not fully supported

YQL, an SQL-based language, is supported

APIs and other access methods

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C++
Go
Java
JavaScript
Python

Server-side scripts

Stored procedures

Java, Javascript

Triggers

yes

only for the SQL API

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

yes

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Access rights for users and roles; record level security configurable

Access Control Lists

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.