DBMS > Amazon Redshift vs. Google Cloud Datastore vs. Informix vs. Ultipa

System Properties Comparison Amazon Redshift vs. Google Cloud Datastore vs. Informix vs. Ultipa

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A secure embeddable database from IBM, positioned besides IBM Db2 as a relatively low-cost product optimized for OLTP and Internet of Things data

High performance Graph DBMS supporting HTAP high availability cluster deployment

Primary database model

Relational DBMS

Document store

Relational DBMS

Since Version 12.10 support for JSON/BSON datatypes compatible with MongoDB

Graph DBMS

Secondary database models

Document store
Spatial DBMS
Time Series DBMS

with Informix TimeSeries Extension

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	16.32
Rank	#35	Overall
	#21	Relational DBMS

Score	0.11
Rank	#338	Overall
	#32	Graph DBMS

Website

aws.amazon.com/redshift

cloud.google.com/datastore

www.ibm.com/products/informix

www.ultipa.com

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/datastore/docs

informix.hcldoc.com
www.ibm.com/support/knowledgecenter/SSGU8G/welcomeIfxServers.html

www.ultipa.com/document

Developer

Amazon (based on PostgreSQL)

Google

IBM, HCL Technologies

Effective May 1st, 2017, HCL took on development, technical support, and product management teams, and works jointly with IBM on product strategy, marketing, and sales.

Ultipa

Initial release

2012

2008

1984

2019

Current release

14.10.FC5, November 2020

License

Commercial or Open Source

commercial

free developer edition available

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, C++ and Java

Server operating systems

hosted

AIX
HP-UX
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

Since Version 12.10 support for JSON/BSON datatypes

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (GQL)

yes

APIs and other access methods

JDBC
ODBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
JSON API

MongoDB compatible
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

C++
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

using Google App Engine

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

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

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users with fine-grained authentication, authorization, and auditing controls

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.