DBMS > Microsoft Azure Table Storage vs. Oracle Berkeley DB vs. TypeDB

System Properties Comparison Microsoft Azure Table Storage vs. Oracle Berkeley DB vs. TypeDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A Wide Column Store for rapid development using massive semi-structured datasets

Widely used in-process key-value store

TypeDB provides developers with an expressive, customizable type system to manage their data using an award-winning query language, TypeQL, while building on a high-performance, distributed architecture.

Primary database model

Wide column store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Graph DBMS

The type-theoretic data model of TypeDB subsumes the graph database model.
Object oriented DBMS

The data model of TypeDB comprises object-oriented features such as class inheritance and interfaces.
Relational DBMS

The type-theoretic data model of TypeDB subsumes the relational database model.

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

Score	2.66
Rank	#97	Overall
	#7	Wide column stores

Score	1.74
Rank	#129	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	0.64
Rank	#229	Overall
	#20	Graph DBMS
	#8	Object oriented DBMS
	#106	Relational DBMS

Website

azure.microsoft.com/en-us/services/storage/tables

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

typedb.com

Technical documentation

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

typedb.com/docs

Developer

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Vaticle

Initial release

2012

1994

2016

Current release

18.1.40, May 2020

2.28.3, June 2024

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

GPL Version 3, commercial licenses available

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, Java, C++ (depending on the Berkeley DB edition)

Java

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X
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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

APIs and other access methods

RESTful HTTP API

gRPC protocol
TypeDB Console (shell)
TypeDB Studio (IDE)

Supported programming languages

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

.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

All JVM based languages
C
C++
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Source-replica replication

Synchronous replication via raft

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

substituted by the relationship feature

Transaction concepts

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

optimistic locking

ACID

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

User concepts

Access control

Access rights based on private key authentication or shared access signatures

yes

at REST API level; other APIs in progress

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

Share this page