DBMS > Drizzle vs. GeoSpock vs. Hyprcubd vs. Infobright vs. Ingres

System Properties Comparison Drizzle vs. GeoSpock vs. Hyprcubd vs. Infobright vs. Ingres

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

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

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Spatial and temporal data processing engine for extreme data scale

Serverless Time Series DBMS

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Well established RDBMS

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Website

geospock.com

hyprcubd.com (offline)

ignitetech.com/softwarelibrary/infobrightdb

www.actian.com/databases/ingres

Technical documentation

docs.actian.com/ingres

Developer

Drizzle project, originally started by Brian Aker

GeoSpock

Hyprcubd, Inc.

Ignite Technologies Inc.; formerly InfoBright Inc.

Actian Corporation

Initial release

2008

2005

1974

originally developed at University Berkely in early 1970s

Current release

7.2.4, September 2012

2.0, September 2019

11.2, May 2022

License

Commercial or Open Source

Open Source

GNU GPL

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

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, Javascript

Server operating systems

FreeBSD
Linux
OS X

hosted

Linux
Windows

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

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

temporal, categorical

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

with proprietary extensions

ANSI SQL for query only (using Presto)

SQL-like query language

yes

APIs and other access methods

JDBC

gRPC (https)

ADO.NET
JDBC
ODBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

Supported programming languages

C
C++
Java
PHP

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

Ingres Replicator

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users can be defined per table

token access

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

How GeoSpock is supercharging geospatial analytics
23 February 2021, ComputerWeekly.com

nChain Leads Investment Round in Extreme-scale Data Firm GeoSpock
2 October 2020, AlexaBlockchain

Imagining an 'Everything Connected' World With Geospock | AWS Startups Blog
20 June 2019, AWS Blog

GeoSpock launches Spatial Big Data Platform 2.0
4 September 2019, VanillaPlus

GeoSpock’s extreme-scale data mission in $5.4m funding boost
8 October 2020, Cambridge Independent

provided by Google News

Actian Launches Ingres 12.0 Database
4 June 2024, PR Newswire

Postgres pioneer Michael Stonebraker promises to upend the database once more
26 December 2023, The Register

New startup from Postgres creator puts the database at heart of software stack
12 March 2024, TechCrunch

Actian Launches Ingres as a Fully-Managed Cloud Service
24 September 2021, Integration Developers

Dr. Michael Stonebraker: A Short History of Database Systems
1 February 2019, The New Stack

provided by Google News

Share this page