DBMS > Graph Engine vs. Oracle Berkeley DB vs. Postgres-XL vs. TempoIQ

System Properties Comparison Graph Engine vs. Oracle Berkeley DB vs. Postgres-XL vs. TempoIQ

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

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

Widely used in-process key-value store

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Graph DBMS
Key-value store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

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

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Score	0.43
Rank	#260	Overall
	#119	Relational DBMS

Website

www.graphengine.io

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

www.postgres-xl.org

tempoiq.com (offline)

Technical documentation

www.graphengine.io/docs/manual

docs.oracle.com/cd/E17076_05/html/index.html

www.postgres-xl.org/documentation

Developer

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

TempoIQ

Initial release

2010

1994

2014

since 2012, originally named StormDB

2012

Current release

18.1.40, May 2020

10 R1, October 2018

License

Commercial or Open Source

Open Source

MIT License

Open Source

commercial license available

Open Source

Mozilla public license

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

.NET and C

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

.NET

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
macOS

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

only with the Berkeley DB XML edition

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

distributed, parallel query execution

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API

Supported programming languages

C#
C++
F#
Visual Basic

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

only for the SQL API

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

yes

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

simple authentication-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.

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

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

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

What is NoSQL (Not Only SQL database)?
28 February 2022, TechTarget

Margo I. Seltzer
18 August 2020, Berkman Klein Center

Oracle acquires Sleepycat for code
17 August 2016, East Bay Times

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular
5 March 2019, ADT Magazine

provided by Google News

Share this page