DBMS > AntDB vs. Firebird vs. Hyprcubd vs. Ingres vs. Redis

System Properties Comparison AntDB vs. Firebird vs. Hyprcubd vs. Ingres vs. Redis

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

A scalable, multi-tenant, MPP-architectured RDBMS for OLTP and OLAP operations, highly compatible with Oracle

Firebird is an open source RDBMS forked from Borland's InterBase

Serverless Time Series DBMS

Well established RDBMS

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

Primary database model

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Secondary database models

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

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

Score	0.09
Rank	#342	Overall
	#149	Relational DBMS

Score	19.46
Rank	#30	Overall
	#18	Relational DBMS

Score	3.63
Rank	#79	Overall
	#43	Relational DBMS

Score	149.43
Rank	#6	Overall
	#1	Key-value stores

Website

www.asiainfo.com/en_us/product_aisware_antdb_detail.html

www.firebirdsql.org

hyprcubd.com (offline)

www.actian.com/databases/ingres

redis.com
redis.io

Technical documentation

www.firebirdsql.org/en/reference-manuals

docs.actian.com/ingres

docs.redis.com/latest/index.html
redis.io/docs

Developer

AsiaInfo Technologies Limited

Firebird Foundation

Hyprcubd, Inc.

Actian Corporation

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2000

As fork of Borland's InterBase

1974

originally developed at University Berkely in early 1970s

2009

Current release

5.0.1, August 2024

12.0, July 2024

7.2.5, May 2024

License

Commercial or Open Source

commercial

Open Source

Initial Developer's Public License

commercial

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

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

C and C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

with RediSearch module

SQL

Support of SQL

SQL2016 compliant

yes

SQL-like query language

yes

with RediSQL module

APIs and other access methods

JDBC
MySQL protocol compliant
ODBC

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

gRPC (https)

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

PSQL

yes

Lua; Redis Functions coming in Redis 7 (slides and Github)

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Ingres Replicator

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

yes

MVCC

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept

token access

fine grained access rights according to SQL-standard

Access Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based authentication

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.