DBMS > FatDB vs. Hyprcubd vs. Ingres vs. jBASE vs. Sequoiadb

System Properties Comparison FatDB vs. Hyprcubd vs. Ingres vs. jBASE vs. Sequoiadb

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

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

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Serverless Time Series DBMS

Well established RDBMS

A robust multi-value DBMS comprising development tools and middleware

NewSQL database with distributed OLTP and SQL

Primary database model

Document store
Key-value store

Time Series DBMS

Relational DBMS

Multivalue DBMS

Document store
Relational DBMS

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

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Website

hyprcubd.com (offline)

www.actian.com/databases/ingres

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

www.sequoiadb.com

Technical documentation

docs.actian.com/ingres

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

FatCloud

Hyprcubd, Inc.

Actian Corporation

Rocket Software (formerly Zumasys)

Sequoiadb Ltd.

Initial release

2012

1974

originally developed at University Berkely in early 1970s

1991

2013

Current release

11.2, May 2022

5.7

License

Commercial or Open Source

commercial

Open Source

Server: AGPL; Client: Apache V2

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

Server operating systems

Windows

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

AIX
Linux
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

yes

optional

yes

oid, date, timestamp, binary, regex

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

yes

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language

yes

Embedded SQL for jBASE in BASIC

SQL-like query language

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

gRPC (https)

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

proprietary protocol using JSON

Supported programming languages

.Net
Basic
Jabbascript
Java

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

yes

via applications

yes

JavaScript

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Ingres Replicator

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

Can implement custom security layer via applications

token access

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

simple password-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

Temenos signs first customer in India
24 August 2009, Finextra

provided by Google News

Share this page