DBMS > EsgynDB vs. Graph Engine vs. OrigoDB vs. TimesTen

System Properties Comparison EsgynDB vs. Graph Engine vs. OrigoDB vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A fully ACID in-memory object graph database

An in-memory SQL relational database that delivers microsecond response and high throughput for OLTP applications. TimesTen can be deployed as a standalone database or as a cache to a backend Oracle database.

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Document store
Object oriented DBMS

Relational DBMS

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

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	0.56
Rank	#241	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	1.26
Rank	#164	Overall
	#75	Relational DBMS

Website

www.esgyn.cn

www.graphengine.io

origodb.com

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

Technical documentation

www.graphengine.io/docs/manual

origodb.com/docs

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

Developer

Esgyn

Microsoft

Robert Friberg et al

Oracle

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

Initial release

2015

2010

2009

under the name LiveDB

1998

Current release

Release 22.1

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

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

C++, Java

.NET and C

Server operating systems

Linux

.NET

Linux
Windows

IBM AIX Power PC 64-bit
Linux arm64
Linux x86-64
Solaris SPARC 64
Solaris SPARC/x86
Solaris x86-64

Data scheme

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP API

.NET Client API
HTTP API
LINQ

ODBC
ODP.NET
Oracle Call Interface (OCI)
Pro*C/C++ programming interfaces
SQL and PL/SQL via JDBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
F#
Visual Basic

.Net

C
C++
Java
Node.js
PL/SQL
Python

Server-side scripts

Stored procedures

Java Stored Procedures

yes

PL/SQL

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

depending on model

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

Write ahead log

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

User concepts

Access control

fine grained access rights according to SQL-standard

Role based authorization

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.

Related products and services

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

More resources

Recent citations in the news

Trinity
30 October 2010, microsoft.com

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

The graph analytics landscape 2019
27 February 2019, Data Science Central

provided by Google News

Oracle starts peddling Exalytics in-memory appliance
12 March 2012, The Register

SAP S&D Benchmark - The Intel Xeon E7-8800 v3 Review: The POWER8 Killer?
8 May 2015, AnandTech

provided by Google News

Share this page