DBMS > Oracle NoSQL vs. TypeDB vs. VoltDB

System Properties Comparison Oracle NoSQL vs. TypeDB vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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.

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store
Key-value store
Relational DBMS

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.

Relational DBMS

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

Score	3.35
Rank	#78	Overall
	#13	Document stores
	#10	Key-value stores
	#42	Relational DBMS

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

Score	1.23
Rank	#161	Overall
	#72	Relational DBMS

Website

www.oracle.com/database/nosql/technologies/nosql

typedb.com

www.voltdb.com

Technical documentation

docs.oracle.com/en/database/other-databases/nosql-database/index.html

typedb.com/docs

docs.voltdb.com

Developer

Oracle

Vaticle

VoltDB Inc.

Initial release

2011

2016

2010

Current release

24.4, December 2024

2.28.3, June 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

GPL Version 3, commercial licenses available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java

Java, C++

Server operating systems

Linux
Solaris SPARC/x86

Linux
OS X
Windows

Linux
OS X

for development

Data scheme

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

optional

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

only a subset of SQL 99

APIs and other access methods

RESTful HTTP API

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

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C#
Go
Java
JavaScript (Node.js)
Python
Rust
Typescript (Node.js)

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Java

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Synchronous replication via raft

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

substituted by the relationship feature

FOREIGN KEY constraints are not supported

Transaction concepts

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

configurable

ACID within a storage node (=shard)

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

off heap cache

User concepts

Access control

Access rights for users and roles

yes

at REST API level; other APIs in progress

Users and roles with access to stored procedures

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