DBMS > Amazon Redshift vs. Google Cloud Datastore vs. HugeGraph vs. Infobright

System Properties Comparison Amazon Redshift vs. Google Cloud Datastore vs. HugeGraph vs. Infobright

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 fast-speed and highly-scalable Graph DBMS

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

Primary database model

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.17
Rank	#335	Overall
	#31	Graph DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Website

aws.amazon.com/redshift

cloud.google.com/datastore

github.com/hugegraph
hugegraph.apache.org

ignitetech.com/softwarelibrary/infobrightdb

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/datastore/docs

hugegraph.apache.org/docs

Developer

Amazon (based on PostgreSQL)

Google

Baidu

Ignite Technologies Inc.; formerly InfoBright Inc.

Initial release

2012

2008

2018

2005

Current release

0.9

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

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

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

Java

Server operating systems

hosted

Linux
macOS
Unix

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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.

Secondary indexes

restricted

yes

also supports composite index and range index

Knowledge Grid Technology used instead

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

Java API
RESTful HTTP API
TinkerPop Gremlin

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

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

Groovy
Java
Python

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

Server-side scripts

Stored procedures

user defined functions

in Python

using Google App Engine

asynchronous Gremlin script jobs

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on used storage backend, e.g. Cassandra and HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes

depending on used storage backend, e.g. Cassandra and HBase

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

via hugegraph-spark

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.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

yes

edges in graph

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, roles and permissions

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.