DBMS > Oracle vs. OrigoDB vs. Warp 10 vs. Yanza

System Properties Comparison Oracle vs. OrigoDB vs. Warp 10 vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Widely used RDBMS

A fully ACID in-memory object graph database

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

www.oracle.com/database

origodb.com

www.warp10.io

yanza.com

Technical documentation

docs.oracle.com/en/database

origodb.com/docs

www.warp10.io/content/02_Getting_started

Developer

Oracle

Robert Friberg et al

SenX

Yanza

Initial release

1980

2009

under the name LiveDB

2015

Current release

23c, September 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Apache License 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C and C++

Java

Server operating systems

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux
Windows

Linux
OS X
Windows

Windows

Data scheme

yes

Schemaless in JSON and XML columns

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

.NET Client API
HTTP API
LINQ

HTTP API
Jupyter
WebSocket

HTTP API

Supported programming languages

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net

any language that supports HTTP calls

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

yes

WarpScript

Triggers

yes

Domain Events

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

horizontal partitioning

client side managed; servers are not synchronized

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

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

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

In-memory capabilities

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

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role based authorization

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.