DBMS > Ingres vs. SAP HANA vs. Vitess vs. YDB

System Properties Comparison Ingres vs. SAP HANA vs. Vitess vs. YDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Well established RDBMS

In-memory, column based data store. Available as appliance or cloud service

Scalable, distributed, cloud-native DBMS, extending MySQL

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Relational DBMS

Document store
Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
Spatial DBMS

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

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Score	0.33
Rank	#287	Overall
	#43	Document stores
	#132	Relational DBMS

Website

www.actian.com/databases/ingres

www.sap.com/products/hana.html

vitess.io

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

docs.actian.com/ingres

help.sap.com/hana

vitess.io/docs

ydb.tech/en/docs

Developer

Actian Corporation

SAP

The Linux Foundation, PlanetScale

Yandex

Initial release

1974

originally developed at University Berkely in early 1970s

2010

2013

2019

Current release

11.2, May 2022

2.0 SPS07 (April 4, 2023), April 2023

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0, commercial licenses available

Open Source

Apache 2.0; commercial license available

Cloud-based only

Only available as a cloud service

also available as a cloud based 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
HP Open VMS
HP-UX
Linux
Solaris
Windows

Appliance or cloud-service

Docker
Linux
macOS

Linux

Data scheme

yes

Flexible Schema (defined schema, partial schema, 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.

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (YQL)

APIs and other access methods

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

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

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

yes

SQLScript, R

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Ingres Star to access multiple databases simultaneously

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Ingres Replicator

yes

Multi-source replication
Source-replica replication

Active-passive shard 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

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

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

yes

Users with fine-grained authorization concept

no user groups or roles

Access rights defined for Yandex Cloud users

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.