DBMS > Hyprcubd vs. Ingres vs. Kingbase vs. SiteWhere vs. SQLite

System Properties Comparison Hyprcubd vs. Ingres vs. Kingbase vs. SiteWhere vs. SQLite

Editorial information provided by DB-Engines

Name

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

Description

Serverless Time Series DBMS

Well established RDBMS

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

M2M integration platform for persisting/querying time series data

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

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	0.50
Rank	#257	Overall
	#119	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

hyprcubd.com (offline)

www.actian.com/databases/ingres

www.kingbase.com.cn

github.com/sitewhere/sitewhere

www.sqlite.org

Technical documentation

docs.actian.com/ingres

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

Developer

Hyprcubd, Inc.

Actian Corporation

BeiJing KINGBASE Information technologies inc.

SiteWhere

Dwayne Richard Hipp

Initial release

1974

originally developed at University Berkely in early 1970s

1999

2010

2000

Current release

11.2, May 2022

V8.0, August 2021

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Common Public Attribution License Version 1.0

Open Source

Public Domain

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 Java

Java

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux
Windows

Linux
OS X
Windows

server-less

Data scheme

yes

predefined scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like query language

yes

Standard with numerous extensions

yes

SQL-92 is not fully supported

APIs and other access methods

gRPC (https)

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Ingres Star to access multiple databases simultaneously

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Ingres Replicator

yes

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

via file-system locks

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

token access

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.