DBMS > Geode vs. OpenTSDB vs. Oracle vs. TimesTen

System Properties Comparison Geode vs. OpenTSDB vs. Oracle vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Scalable Time Series DBMS based on HBase

Widely used RDBMS

In-Memory RDBMS compatible to Oracle

Primary database model

Key-value store

Time Series DBMS

Relational 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	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	1.68
Rank	#142	Overall
	#12	Time Series DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

geode.apache.org

opentsdb.net

www.oracle.com/database

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

Technical documentation

geode.apache.org/docs

opentsdb.net/docs/build/html/index.html

docs.oracle.com/en/database

docs.oracle.com/database/timesten-18.1

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

currently maintained by Yahoo and other contributors

Oracle

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2002

2011

1980

1998

Current release

1.1, February 2017

23c, September 2023

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

LGPL

commercial

restricted free version is available

commercial

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

C and C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
Windows

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

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

with proprietary extensions

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HTTP API
Telnet API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

Erlang
Go
Java
Python
R
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

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

user defined functions

PL/SQL

also stored procedures in Java possible

PL/SQL

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on HBase

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication factor

based on HBase

Multi-source replication
Source-replica replication

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

Eventual Consistency

Immediate Consistency

based on HBase

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

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

Access rights per client and object definable

fine grained access rights according to SQL-standard

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.