DBMS > OpenQM vs. OrigoDB vs. Teradata vs. Vitess

System Properties Comparison OpenQM vs. OrigoDB vs. Teradata vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

QpenQM is a high-performance, self-tuning, multi-value DBMS

A fully ACID in-memory object graph database

A hybrid cloud data analytics software platform (Teradata Vantage)

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Multivalue DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

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

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

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

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

origodb.com

www.teradata.com

vitess.io

Technical documentation

origodb.com/docs

docs.teradata.com

vitess.io/docs

Developer

Rocket Software, originally Martin Phillips

Robert Friberg et al

Teradata

The Linux Foundation, PlanetScale

Initial release

1993

2009

under the name LiveDB

1984

2013

Current release

3.4-12

Teradata Vantage 1.0 MU2, January 2019

15.0.2, December 2022

License

Commercial or Open Source

Open Source

GPLv2, extended commercial license available

Open Source

commercial

Open Source

Apache Version 2.0, commercial licenses available

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

Server operating systems

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
Windows

hosted
Linux

Docker
Linux
macOS

Data scheme

yes

with some exceptions

yes

Typing

predefined data types such as float or date

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

yes

Secondary indexes

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

yes

SQL

Support of SQL

yes

SQL 2016 + extensions

yes

with proprietary extensions

APIs and other access methods

.NET Client API
HTTP API
LINQ

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
Basic
C
Java
Objective C
PHP
Python

.Net

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

UDFs, stored procedures, table functions in parallel

yes

proprietary syntax

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

yes

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Hashing

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication
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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

depending on model

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Write ahead log

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

Access rights can be defined down to the item level

Role based authorization

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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

DB-Engines blog posts

Teradata is the most popular data warehouse DBMS
2 April 2013, Paul Andlinger

show all

Recent citations in the news

Teradata Co. (NYSE:TDC) Shares Sold by Panagora Asset Management Inc.
25 May 2024, Defense World

Teradata takes plunge into lakehouse waters, but not everyone is convinced
23 May 2024, The Register

Director CHOU TIMOTHY C K Sells Shares of Teradata Corp (TDC)
22 May 2024, Yahoo Finance

Teradata AI Unlimited joins Microsoft Fabric in private preview
21 May 2024, Investing.com

Teradata (TDC) Reports Earnings Tomorrow: What To Expect
23 May 2024, The Globe and Mail

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

provided by Google News

Share this page