DBMS > Hyprcubd vs. Ignite vs. jBASE vs. PostGIS vs. Transbase

System Properties Comparison Hyprcubd vs. Ignite vs. jBASE vs. PostGIS vs. Transbase

Editorial information provided by DB-Engines

Name

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

Description

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

A robust multi-value DBMS comprising development tools and middleware

Spatial extension of PostgreSQL

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Time Series DBMS

Key-value store
Relational DBMS

Multivalue DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

hyprcubd.com (offline)

ignite.apache.org

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

postgis.net

www.transaction.de/en/products/transbase.html

Technical documentation

apacheignite.readme.io/docs

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

postgis.net/documentation

www.transaction.de/en/products/transbase/features.html

Developer

Hyprcubd, Inc.

Apache Software Foundation

Rocket Software (formerly Zumasys)

Transaction Software GmbH

Initial release

2015

1991

2005

1987

Current release

Apache Ignite 2.6

5.7

3.4.2, February 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

GPL v2.0

commercial

free development license

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++, Java, .Net

C and C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

AIX
Linux
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

yes

optional

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

ANSI-99 for query and DML statements, subset of DDL

Embedded SQL for jBASE in BASIC

yes

APIs and other access methods

gRPC (https)

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
Basic
Jabbascript
Java

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

yes

user defined functions

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

based on PostgreSQL

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

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

yes

Concurrency

Support for concurrent manipulation of data

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

token access

Security Hooks for custom implementations

Access rights can be defined down to the item level

yes

based on PostgreSQL

fine grained access rights according to SQL-standard

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

Apache Ignite: An Overview
6 September 2023, Open Source For You

GridGain Releases Conference Schedule for Virtual Apache Ignite Summit 2023
1 June 2023, Datanami

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

Real-time in-memory OLTP and Analytics with Apache Ignite on AWS | Amazon Web Services
14 May 2016, AWS Blog

provided by Google News

Share this page