DBMS > Ingres vs. Transbase vs. VoltDB vs. XTDB

System Properties Comparison Ingres vs. Transbase vs. VoltDB vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Well established RDBMS

A resource-optimized, high-performance, universally applicable RDBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Document store

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

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.actian.com/databases/ingres

www.transaction.de/en/products/transbase.html

www.voltdb.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.actian.com/ingres

www.transaction.de/en/products/transbase/features.html

docs.voltdb.com

www.xtdb.com/docs

Developer

Actian Corporation

Transaction Software GmbH

VoltDB Inc.

Juxt Ltd.

Initial release

1974

originally developed at University Berkely in early 1970s

1987

2010

2019

Current release

11.2, May 2022

Transbase 8.3, 2022

11.3, April 2022

1.19, September 2021

License

Commercial or Open Source

commercial

free development license

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Open Source

MIT License

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

Java, C++

Clojure

Server operating systems

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Linux
OS X

for development

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

yes

only a subset of SQL 99

limited SQL, making use of Apache Calcite

APIs and other access methods

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
JDBC
RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Ingres Replicator

Source-replica replication

Multi-source replication
Source-replica replication

yes, each node contains all data

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

User concepts

Access control

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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

Postgres pioneer Michael Stonebraker promises to upend the database once more
26 December 2023, The Register

New startup from Postgres creator puts the database at heart of software stack
12 March 2024, TechCrunch

Actian Launches Ingres as a Fully-Managed Cloud Service
24 September 2021, Integration Developers

PostgreSQL now top developer choice ahead of MySQL, according to massive new survey • DEVCLASS
13 June 2023, DevClass

Dr. Michael Stonebraker: A Short History of Database Systems
1 February 2019, The New Stack

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Aims for Fast Big Data Development -- ADTmag
29 January 2015, ADT Magazine

provided by Google News

Share this page