DBMS > Altibase vs. Amazon Redshift vs. Axibase vs. Coveo vs. Google Cloud Datastore

System Properties Comparison Altibase vs. Amazon Redshift vs. Axibase vs. Coveo vs. Google Cloud Datastore

Editorial information provided by DB-Engines

Name

Description

An enterprise grade, high-performance RDBMS

Large scale data warehouse service for use with business intelligence tools

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

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

Primary database model

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

Score	1.07
Rank	#186	Overall
	#87	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	4.47
Rank	#76	Overall
	#12	Document stores

Website

altibase.com

aws.amazon.com/redshift

axibase.com/docs/atsd/finance

www.coveo.com

cloud.google.com/datastore

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

docs.aws.amazon.com/redshift

docs.coveo.com

cloud.google.com/datastore/docs

Developer

Altibase

Amazon (based on PostgreSQL)

Axibase Corporation

Coveo

Google

Initial release

1999

2012

2013

2012

2008

Current release

v7.3, 2023, August 2023

15585

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

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

Server operating systems

AIX
HP-UX
Linux

hosted

Linux

hosted

Data scheme

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

yes

yes, details here

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

yes

restricted

yes

SQL

Support of SQL

ANSI SQL-92

yes

does not fully support an SQL-standard

SQL-like query language

SQL-like query language (GQL)

APIs and other access methods

JDBC
ODBC
Proprietary protocol

JDBC
ODBC

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

RESTful HTTP API

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

Supported programming languages

C
C++
Java

All languages supporting JDBC/ODBC

Go
Java
PHP
Python
R
Ruby

C#
Java
JavaScript
Python

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

Server-side scripts

Stored procedures

stored procedures and stored functions

user defined functions

in Python

yes

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

Multi-source replication using Paxos

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.

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

yes

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

granular access controls, API key management, content filters

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

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.