DBMS > Memcached vs. Oracle vs. OrigoDB vs. TerminusDB

System Properties Comparison Memcached vs. Oracle vs. OrigoDB vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

In-memory key-value store, originally intended for caching

Widely used RDBMS

A fully ACID in-memory object graph database

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Key-value store

Relational DBMS

Document store
Object oriented DBMS

Graph 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

Document store
RDF store

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

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

www.memcached.org

www.oracle.com/database

origodb.com

terminusdb.com

Technical documentation

github.com/memcached/memcached/wiki

docs.oracle.com/en/database

origodb.com/docs

terminusdb.github.io/terminusdb/#

Developer

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

Robert Friberg et al

DataChemist Ltd.

Initial release

2003

1980

2009

under the name LiveDB

2018

Current release

1.6.27, May 2024

23c, September 2023

11.0.0, January 2023

License

Commercial or Open Source

Open Source

BSD license

commercial

restricted free version is available

Open Source

GPL V3

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 and C++

Prolog, Rust

Server operating systems

FreeBSD
Linux
OS X
Unix
Windows

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

Linux
Windows

Linux

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

yes

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

SQL-like query language (WOQL)

APIs and other access methods

Proprietary protocol

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

.NET Client API
HTTP API
LINQ

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

JavaScript
Python

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding, horizontal partitioning

horizontal partitioning

client side managed; servers are not synchronized

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication
Source-replica replication

Source-replica replication

Journaling Streams

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

Foreign keys

Referential integrity

yes

depending on model

yes

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 journaling

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

yes

using SASL (Simple Authentication and Security Layer) protocol

fine grained access rights according to SQL-standard

Role based authorization

Role-based access control

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.